[Frontend] Consolidate four different NEXT_PUBLIC_API_URL fallbacks (mix of /v1 and root)

[ogazboiz]

Join the discussion on Telegram

Why this matters

Four places in the frontend define API_BASE_URL independently, with two different fallback shapes — some with /v1 and some without. This is the source of subtle bugs (e.g. issue #455 with the settings page calling ${baseWithV1}/health and getting /v1/health which doesn't exist).

Verified locations:

• frontend/src/app/streams/[id]/page.tsx:46 → ... || \"http://localhost:3001/v1\"
• frontend/src/app/settings/page.tsx:19 (named INDEXER_URL) → ... || \"http://localhost:3001/v1\"
• frontend/src/app/activity/page.tsx:13-15 → ... || \"http://localhost:3001\" (no /v1)
• frontend/src/components/TransactionTracker.tsx:59 → ... || \"http://localhost:3001/v1\"
• frontend/src/lib/api/_shared.ts:1 (canonical) → \"http://localhost:3001\" (no /v1) via getApiBaseUrl()

Some of these then concatenate /v1/streams/... directly, breaking depending on whether the env var ends in /v1.

Acceptance criteria

• Make every fetch use the shared helper in frontend/src/lib/api/_shared.ts (extend if needed) so there's exactly one place that knows the base URL shape
• All hardcoded fallback strings get removed from the four files above
• Behaviour identical whether NEXT_PUBLIC_API_URL is set with or without trailing /v1

Files to touch

• frontend/src/app/streams/[id]/page.tsx
• frontend/src/app/settings/page.tsx
• frontend/src/app/activity/page.tsx
• frontend/src/components/TransactionTracker.tsx
• frontend/src/lib/api/_shared.ts

Out of scope

• Reworking the SSE event subscribe URL

[GiftedGiftB]

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

I can get this work done in less than 30 minutes.

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

[Silver36-ship-it]

@Silver36-ship-it has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this professionally, please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Silver36-ship-it to this issue.

[Banx17]

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

Please assign this issue to me, thanks.

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

[oluwaseyi1996-netizen]

@oluwaseyi1996-netizen has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

please i will love to work on this issue thank you

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

[code-0-stella]

@code-0-stella has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, I have reviewed the issue and understand what needs to be done.

I would appreciate being assigned to it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @code-0-stella to this issue.

[Glam26]

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

I'd like to work on this issue.

I'm a returning contributor and have worked on frontend refactors and API consistency improvements in previous contributions. This issue addresses an important source of subtle bugs by centralizing API URL construction, making it a good candidate for a focused cleanup.

My plan is to:

• Audit the current API base URL usage in:

  • frontend/src/app/streams/[id]/page.tsx
  • frontend/src/app/settings/page.tsx
  • frontend/src/app/activity/page.tsx
  • frontend/src/components/TransactionTracker.tsx

• Extend frontend/src/lib/api/_shared.ts (if necessary) so it becomes the single source of truth for API URL generation.

• Ensure the helper correctly handles:

  • NEXT_PUBLIC_API_URL with no /v1
  • NEXT_PUBLIC_API_URL ending with /v1
  • trailing slash variations

• Remove all hardcoded localhost fallback URLs from the affected files.

• Verify existing request paths continue to work without producing duplicate or missing /v1 segments.

• Add/update tests for the shared helper covering the supported URL configurations.

• Run the project's lint, tests, and build to confirm there are no regressions.

I'll keep the change scoped to URL normalization and avoid touching the SSE subscription implementation, as requested.

If the issue is still available, I'd be happy to take it. Thank you!

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

[OsagieCynthia]

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

Hi, i am a fullstack engineer, i will love to close this issue ser
please assign

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @OsagieCynthia has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #622)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.