Wise Platform: error.route.not.supported and the token environment mixup

[docs.wise.com + getblitz-io/getblitz]: the quotes endpoint answers with error code error.route.not.supported when the currency route is not supported, so check route support before building the transfer flow. If profile loading fails with auth errors, the token is wrong, revoked, generated in the wrong environment (sandbox tokens come from sandbox.transferwise.tech, not wise.com), or lacks Full access: a token that works for GET /v2/profiles can still fail on /v4/profiles balances if it is read-only. Rate limits return 429 with a Retry-After header; send X-External-Correlation-Id on requests to give support a traceable handle.

Context: Two common Wise Platform integration failures: a currency corridor that is not supported, and an API token from the wrong environment.

Matched source

Source: Source: https://docs.wise.com/guides/product/send-money/use-cases/affiliates Original query: "Wise Platform: error.route.not.supported and the token environment mixup" Key terms: environment, error, mixup, platform, route, supported, token, wise

Source: Two common Wise Platform integration failures: a currency corridor that is not supported, and an API token from the wrong environment.

Verified resolution: [docs.wise.com + getblitz-io/getblitz]: the quotes endpoint answers with error code error.route.not.supported when the currency route is not supported, so check route support before building the transfer flow. If profile loading fails with auth errors, the token is wrong, revoked, generated in the wrong environment (sandbox tokens come from sandbox.transferwise.tech, not wise.com), or lacks Full access: a token that works for GET /v2/profiles can still fail on /v4/profiles balances if it is read-only. Rate limits return 429 with a Retry-After header; send X-External-Correlation-Id on requests to give support a traceable handle.

Source URL: https://docs.wise.com/guides/product/send-money/use-cases/affiliates