UNSUPPORTED_TOKEN
Unsupported token: A provider does not recognise or will not route the source or destination token.
| HTTP status | Retry |
|---|---|
400 |
no |
Where it comes from: Provider errors from Jupiter, Relay, deBridge and 0x. Usually appears per provider in QuoteResponse.errors.
Causes#
- The token address / mint does not exist on that chain, or is not tradable on the provider.
- A symbol that is not on LayerHop's built-in token list was passed; unknown symbols are forwarded as if they were addresses.
- The token is restricted by the provider (for example a sanctioned asset).
How to fix#
- Pass the token's address / mint instead of a symbol when it is not on the token list.
- Check that the address belongs to the chain you named (USDC on Base is not USDC on Arbitrum).
Example response#
JSON
{
"error": {
"code": "UNSUPPORTED_TOKEN",
"message": "jupiter: Token not tradable",
"requestId": "0d5e1f6a-3b2c-4d1e-8f9a-7b6c5d4e3f21",
"docsUrl": "https://docs.layerhop.com/errors/UNSUPPORTED_TOKEN"
}
}See Error handling & retries for a retry strategy, and the error catalog for every code.