[Backend] Mount pool, notifications, and events routers under /api/v1

[ogazboiz]

Join the contributor Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

/api/v1 is the documented versioned namespace but only mounts simulation, score, loans, indexer, admin, auth, remittances. The pool, notifications, and events routers are only available under the legacy /api prefix. Frontend code that adopts /api/v1 consistently currently gets 404s for these surfaces, which makes the version promise meaningless.

Acceptance criteria

• Mount poolRoutes at /api/v1/pool in app.ts.
• Mount notificationsRoutes at /api/v1/notifications in app.ts.
• Mount eventRoutes at /api/v1/events in app.ts.
• Add an integration test that hits one endpoint from each newly mounted router under /api/v1 and expects 200/2xx with valid auth headers.
• Keep the legacy /api/* mounts unchanged for backwards compatibility.

Files to touch

• backend/src/app.ts
• backend/src/__tests__/loanEndpoints.test.ts (or a new apiV1Mounts.test.ts)

Out of scope

• Removing legacy /api/* mounts.
• Updating frontend to use /api/v1 (separate follow-up).

[artylobos]

Submitted PR #919 for this issue: #919

Scope:

• mounts the existing pool, notifications, and events routers under /api/v1
• keeps the legacy /api/* mounts in place
• adds integration coverage for /api/v1/pool/stats, /api/v1/notifications, and /api/v1/events/status with valid auth/API-key headers

Validation:

• GitHub CI is green: supply-chain-audit, backend, frontend, contracts, and CodeQL
• local focused Jest: 3 passed
• local backend full Jest: 213 passed, 18 skipped
• local backend build/typecheck/lint completed; lint exits 0 with existing repository warnings
• local frontend Prettier and tsc --noEmit checks passed
• git diff --check passed

No secrets, wallet keys, deployment values, or private/system context included.

[AbelOsaretin]

@AbelOsaretin has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AbelOsaretin to this issue.

[soomtochukwu]

@soomtochukwu has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Heyyy :) 👋🏿
Let me take this off your plate ASAP

ℹ️ Repo Maintainers: To accept this application, review their application or assign @soomtochukwu to this issue.

[drips-wave]

Congratulations, @AbelOsaretin! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @AbelOsaretin: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊