Skip to main content

Accounts

This page covers portfolio balances and transfer history from the Accounts tag in Trader API (standard REST) (see OpenAPI specs). Use your Trader API bearer token (Authentication, Standard API). Use the endpoints below to read balances and transfer history programmatically.

Balances​

How this differs from low-latency positions​

The low-latency Balances endpoint is built for active trading: what you hold per instrument, sizes, and what is still available after open orders.

GET /api/v2/accounts/balances on standard REST is a broader portfolio snapshot. It still reflects trading-related balances, but it also rolls in other Figure Markets products—margin and loans, Democratized Prime offers, and related totals—so you can see funding, lending, and trading together. Use positions on trade.figuremarkets.* when you need low-latency, order-book–centric sizing; use portfolio balances when you need the full cross-product view or a historical snapshot via atTime.

Committed vs uncommitted (short)​

Figure Markets separates assets that are committed to the exchange settlement layer on Provenance (eligible to trade, post margin, and similar) from uncommitted balances that remain in your wallet and are not yet locked for exchange use. Portfolio balances expose that split where the product applies, including uncommitted wallet amounts you have not yet committed. Only committed balances generally count toward what you can deploy for trading on the exchange.

Get portfolio balances: GET /api/v1/accounts/balances

Optional query atTime (ISO 8601) returns balances at a specific time. Response includes assets, loans, offers, cryptoBackedLoans, and totals.

Transfer history​

Historical transfers for the authenticated account with optional filters.

Get transfer history: GET /api/v1/accounts/history

Optional query params: actions (e.g. DEPOSIT, WITHDRAW, MARGIN, SEND, RECEIVE), assets, page, size. Response is paginated. V2 includes SEND, RECEIVE, SEND_COLLATERAL, RECEIVE_COLLATERAL. For the full action enum and response schema, see the Accounts spec.