Skip to content

Migrate default endpoints to unified api.{env}.nado.xyz API - #453

Merged
cedricinkfnd merged 1 commit into
mainfrom
housekeeping/update-endpoints
Aug 28, 2026
Merged

Migrate default endpoints to unified api.{env}.nado.xyz API#453
cedricinkfnd merged 1 commit into
mainfrom
housekeeping/update-endpoints

Conversation

@cedricinkfnd

Copy link
Copy Markdown
Contributor

Backend launched a unified API host (api.{env}.nado.xyz/{service}) for all public services. This migrates the SDK's default endpoints off the per-service hosts (gateway.test.nado.xyz, archive.prod.nado.xyz, etc.). Old endpoints still work; this just moves our defaults forward.

Heads up:

  • Breaking for custom-endpoint users: MobileClient request paths changed from ${url}/mobile/execute${url}/execute (service/version now live in the base URL, e.g. .../mobile/v1). If you pass a custom mobile URL, it must now include /mobile/v1. Same applies to the local default (...:8004/v1/mobile).
  • New optional opts: IndexerClientOpts.rewardsUrl and rewardsEndpoint on createNadoClient custom-endpoint opts. Both fall back to ${indexerEndpoint}/rewards/v1 (the old topology), so existing custom-endpoint setups keep working.
  • All unified routes were verified live against testnet (gateway/archive/rewards/trigger/mobile + WS paths).

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

Tip: disable this comment in your organization's Code Review settings.

// Server base URL, without a version segment (ex. `https://api.prod.nado.xyz/archive`)
url: string;
// Rewards service base URL, including the version segment (ex. `https://api.prod.nado.xyz/rewards/v1`).
// Defaults to `${url}/rewards/v1`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should make this required?

@cedricinkfnd cedricinkfnd Aug 28, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably not worth it, I kept it for smoothing/derisking migration in case anyone uses a custom endpoint for this - after a while we could just have this work exactly like other services.

Only reason it looks a bit different, compared to other services, is that rewards was kinda hybrid as an "extension" of archive before unified.

@cedricinkfnd
cedricinkfnd merged commit 3f583e4 into main Aug 28, 2026
3 checks passed
@cedricinkfnd
cedricinkfnd deleted the housekeeping/update-endpoints branch August 28, 2026 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants