Get your configuration
What your api client is enabled for: every assetId it may use, and who pays the network fee on each.
There is no request body — no userId, no assetId. The answer is the same for every user you hold.
Read this instead of hardcoding the asset table
Your api client may be enabled for only some of the assets in the Asset IDs table, and a call for one you are not enabled for is a 403. This endpoint is the list that will not 403 — resolved against the running service, so an asset that is limited on your environment is absent here too rather than failing later with 400 Unknown assetId.
It is also the list /create, /extend and /addresses filter their address maps to: a chain appears there while you have at least one enabled asset on it.
Call it at startup and cache it. It changes only when your operator changes your account, so poll it on the order of minutes if you poll it at all.
Who pays the fee
feePayer says who covers the network fee on a transfer of that asset:
USER— the fee comes out of the sending wallet. For a native asset it is taken from theamount; for a token it is paid in the chain’s native coin, which the wallet must therefore hold.PLATFORM— you cover it, so your user can move the token without holding any of the chain’s native coin.
The top-level feePayer is PLATFORM when at least one of your assets is, and USER when none are.
Where trades fill
liquidity says where your buy and sell orders are filled: type is internal when they fill on your own desk, and provider when they fill through the liquidity provider set on your account, named in provider.
feePayer describes your arrangement, not a guarantee for the next transfer. A PLATFORM asset can still fall back to USER on an individual send. /fee is the only quote — call it before a transfer and show your user what it returns.
Authentication
A 15-minute token from /auth. Required on every endpoint except /auth.
Headers
Correlation id. Generated if omitted, echoed on every response, and written to the audit log. /send is the exception — there it is required, and it doubles as the idempotency key.
Response
Echo of the inbound X-Request-Id, or a generated one.