Add pagination metadata and sorting options to GET /api/transactions

[Codex723]

ISSUE #16

---

Category: Stellar API Routes
Difficulty: good-first-issue
Labels: backend, api, good-first-issue

Files involved

• src/app/api/transactions/route.ts

Background

Currently only limit/offset are supported. Add a sort param (createdAt asc/desc, amount) and return hasMore in the response.

This issue is part of the RemitX contributor backlog, generated from a full codebase audit of the project. RemitX is a Stellar-based remittance platform (Next.js 16, Prisma/Postgres, the Stellar SDK, and a Soroban escrow contract) currently at the "foundation build" stage: auth and the data model are real, while the Stellar integration, escrow contract internals, and several frontend pages are intentionally scaffolded with TODO(contributor) markers. See FOUNDATION.md in the repo root for the full project map and current status of every subsystem before starting.

Suggested approach

1. Review the current implementation in src/app/api/transactions/route.ts and confirm the stub/gap described below.
2. Currently only limit/offset are supported. Add a sort param (createdAt asc/desc, amount) and return hasMore in the response.
3. Manually verify the change against the acceptance criteria below before opening a PR.
4. Update any relevant comments/docs (e.g. remove the TODO(contributor) marker this issue resolves, if applicable).

Acceptance criteria

• sort query param works for at least 2 fields
• Response includes hasMore boolean
• Backward compatible with existing callers

Notes for contributors

• Keep the change scoped to this issue — if you notice other stubs or bugs nearby, open a separate issue rather than bundling fixes into this PR.
• Match the existing code style in the surrounding file. This codebase uses TypeScript strict mode, Zod for input validation, and the shared successResponse/errorResponse helpers in src/lib/api-response.ts for every API route.
• If this issue depends on another issue in this area being done first, check the related issues below before starting — some subsystems (e.g. the escrow contract's release() authorization) need a design decision made before implementation can proceed.
• Please reference this issue number in your PR description, and check off acceptance criteria as you satisfy them.

Related issues in this area

• Wire POST /api/stellar/send to real rate + XDR build (end-to-end) #12 Wire POST /api/stellar/send to real rate + XDR build (end-to-end)
• Wire POST /api/stellar/submit to update Escrow record when applicable #13 Wire POST /api/stellar/submit to update Escrow record when applicable
• Add rate-limiting to /api/stellar/rate #14 Add rate-limiting to /api/stellar/rate
• Add request idempotency key support to POST /api/stellar/send #15 Add request idempotency key support to POST /api/stellar/send
• Add a GET /api/stellar/account route to fetch current user's Stellar balance #17 Add a GET /api/stellar/account route to fetch current user's Stellar balance