API endpoints
Balances API
Balance and journal endpoints expose ledger-backed projections for an account or wallet. Use them for product balances and reconciliation rather than calculating state only from WebSocket events.
Operations
| Method | Path | Scope | Description |
|---|---|---|---|
GET | /api/v1/ledger/accounts/{accountId}/balances | wallets:read | Account balances by chain and asset |
GET | /api/v1/wallets/{walletId}/balances | wallets:read | Wallet balances |
GET | /api/v1/wallets/{walletId}/ledger-entries | wallets:read | Wallet journal entries |
Account balance fields
| Field | Meaning |
|---|---|
postedBalance | Settled accounting balance in atomic units |
reservedBalance | Amount currently reserved by pending operations |
availableBalance | Amount available after reservations |
*Display | Human-readable representation using asset decimals |
decimals | Decimal precision when known |
displaySource | asset_config or atomic |
Keep atomic values as strings. Do not parse them through floating-point types.
Filters
Account balances accept cursor, limit, chain, and asset. Wallet balances accept cursor, limit, and asset.
Wallet journal entries can be filtered by transactionId, status, direction, entryType, asset, createdFrom, and createdTo, in addition to cursor pagination.
Reconciliation rule
Use events as a trigger to refresh state, then read balances, transactions, and journal entries through REST. Persist the returned identifiers and timestamps so each movement can be traced end to end.