Pockets
Create and list currency pockets under a parent or subaccount wallet.
A pocket is an optional sub-ledger per currency (EUR, BTC, ETH, and others). You can also operate at wallet level.
Wallet buy and sell accept either a pair such as BTC/EUR or pocket UUIDs in the request body; swaps and withdrawals take pocket UUIDs. See Buy, sell, and swap.
Every call for an end user must include X-SUBACCOUNT-ID after you create the subaccount. See Account model.
List pockets and balances
GET /v1/wallet/pocketReturns each pocket with its balance, for fiat and crypto pockets alike. Use it to check a balance before a proforma.
Create a pocket
POST /v1/wallet/pocketRequired body fields: currency (asset symbol from GET /v2/currency/assets) and name. HTTP 406 means the pocket limit for that asset is exceeded.
Exact request fields are in the REST reference. Amounts are decimal strings. Use . not ,.
Typical partner sequence
POST /v1/account/subaccount → store userId.
EUR (or the fiat in your contract) plus the crypto assets you will buy or receive. To receive crypto from another platform, see Crypto deposits.
Fiat funding, buy and sell, then withdrawals.