[Frontend] Fix broken 'Indexer Last Ledger' fetch on settings page

[ogazboiz]

Join the discussion on Telegram

Why this matters

The settings page shows an "Indexer Last Ledger" row that is permanently broken. In frontend/src/app/settings/page.tsx:

const INDEXER_URL = process.env.NEXT_PUBLIC_API_URL || "http://localhost:3001/v1";
// ...
const response = await fetch(`${INDEXER_URL}/health`);
const data = await response.json();
if (data.ledger) setLastLedger(data.ledger.toString());

Two problems:

1. The health route is mounted at /health (root), not under /v1 (see backend/src/app.ts — app.use('/health', healthRoutes) and backend/src/routes/v1/index.ts). So ${API_URL}/v1/health (or /v1/v1/health depending on the env value) 404s.
2. The health response (backend/src/routes/health.routes.ts) returns { status, db, indexerLag, uptime } — there is no ledger field. The actual last ledger lives in GET /v1/admin/metrics (indexer.lastLedger), which requires admin auth.

So the row always renders "Unknown"/"Unavailable"/"Error". Either expose the ledger somewhere reachable or remove the row.

Acceptance criteria

• Pick one approach and implement it: (a) add a public, unauthenticated lastLedger field to the /health response and point the fetch at the correct /health path; or (b) add a small public indexer-status endpoint; or (c) remove the "Indexer Last Ledger" row if no public source is desired.
• Fix the URL so it resolves regardless of whether NEXT_PUBLIC_API_URL ends in /v1.
• Handle loading/error states so it never sticks on "Loading...".

Files to touch

• frontend/src/app/settings/page.tsx
• backend/src/routes/health.routes.ts (if exposing the field)

Out of scope

• Reworking the full admin metrics endpoint.

[zoffunjunior381-jpg]

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

Hi Maintainer Can I work on this issue

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

[drips-wave]

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

🧑‍💻 @zoffunjunior381-jpg: 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 🌊

[drips-wave]

This issue has been completed by @zoffunjunior381-jpg as part of the Stellar Wave Program's 5th Wave 🥳

😎 @zoffunjunior381-jpg: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.