Core concepts
Assets & networks
Assets and network capabilities are dynamic. Always query capability endpoints instead of hardcoding token/chain assumptions.
Supported assets
Assets and network capabilities are dynamic. Always query capability endpoints instead of hardcoding token/chain assumptions.
curl $XPEND_BASE/v1/assets \
-H "Authorization: Bearer $XPEND_SECRET_KEY"Capability checks before write actions
- Use merchant checkout quote-chain options before exposing checkout token selectors.
- Use destination availability before rendering payout forms.
- Cache capability responses briefly (~60s), they change but not constantly.
Asset key conventions
Asset identifiers are modeled as token and chain combinations in multiple endpoints (for example payout creation and balance lookup). Keep them normalized in your persistence layer.
Network policy is environment-scoped
Network policy can differ by environment and merchant configuration. Query capability endpoints at startup and cache briefly. Do not hardcode network lists in your codebase, they will drift.
- Store assets as
{ token, chain }tuples, never as a single concatenated string. - Match the casing returned by /v1/assets exactly when sending values back.