Skip to main content
Use GET /partner/wallets/chains as the source of truth for route availability in the environment you are calling. Route availability changes without notice, so do not hardcode it in production systems. Each returned route has a network (the route family) and a chain object whose slug names the exact network. Production currently exposes these families and networks: Staging exposes a reduced route set that can be empty at times. Read the live list rather than assuming a test network exists, and use the sandbox simulation endpoints to create stablecoin deposit activity when no route is available.

​
Required Headers

GET /partner/wallets/chains and GET /partner/wallets/fiat/banks are public. Other wallet routes require X-Api-Key.

​
Common Failures

​
Route Selection

Pass the route family as chain and, whenever the family has more than one network, the exact network as slug when calling GET /partner/wallets/crypto/address:
In production slug is required for evm. Route families can share asset symbols, so the chain and slug are part of the deposit instruction and must be stored with the address. For example, USDT on Tron and USDT on an EVM chain are different deposit routes. Showing the wrong route can cause funds to be sent to an address that does not match the user’s intended network. Refresh route metadata periodically and before showing deposit instructions in your application.