[Wave 150pts] Fix: `GET /wallets/balances` returns 404 — update path to `/users/wallet/balances` in `lib/api/wallet.ts`

[portableDD]

Summary

The wallet balance API call is hitting the wrong URL and returning 404 on every request. This is the highest-priority frontend bug identified in the API audit because it causes WithdrawalForm.tsx to display an error banner on every load for every authenticated user.

Root Cause

lib/api/wallet.ts calls /wallets/balances but the correct backend path is /users/wallet/balances. Live probe confirmed:

• GET /v1/wallets/balances → 404 Not Found ("Cannot GET /v1/wallets/balances")
• GET /v1/users/wallet/balances → 401 Unauthorized (route exists and is protected)

Impact

• WithdrawalForm.tsx calls getBalances() on mount. Because getBalances() always throws (404), the component lands on its error state and shows "Unable to load currencies or balances. Please try again." for every authenticated user — the form is unusable.
• components/dashboard/account-overview.tsx has a TODO comment to wire up getBalances() once this path is fixed. Once this issue is resolved, that wiring can proceed (tracked in a separate issue).

What Needs to Be Done

File: lib/api/wallet.ts

Change:

const data = await apiClient<any>("/wallets/balances", {

To:

const data = await apiClient<any>("/users/wallet/balances", {

Also check whether useProxy should be true (routed via /api/proxy) or false (direct call). All other authenticated calls in lib/api/users.ts use useProxy: false — verify with the backend team which pattern applies here and update accordingly.

Acceptance Criteria

• lib/api/wallet.ts calls /users/wallet/balances
• getBalances() no longer throws a 404 when called with a valid token
• WithdrawalForm.tsx no longer shows the error banner on load for authenticated users
• useProxy value is confirmed and documented in a code comment

Constraints

• Do not change WithdrawalForm.tsx logic in this PR — the path fix in lib/api/wallet.ts is the only required change
• Complexity: Low — 150 points

[Luchistack]

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

Hello! I’d love to take on this issue. I’ve reviewed the requirements and have a clear path forward for the implementation. I estimate I can have a PR ready within about 3 hours of being assigned. Could you please assign this to me?

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

[drips-wave]

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

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