Get an account
Authorizations
OAuth 2.0 client_credentials grant. Send client_id:client_secret
as HTTP Basic, or as form fields. Tokens are HS256 JWTs valid for
one hour (configurable). Decode them at jwt.io.
Path Parameters
Response
ok
Discriminator naming the shape of this resource (e.g. account, transaction).
account "account"
"accounts_receivable:acme"
asset, liability, revenue, expense, equity "liability"
"USDC"
"Acme payable"
6 for USDC, 8 for BTC, 18 for ETH; null for unknown.
6
fiat, crypto, stablecoin, null "stablecoin"
True if currency isn't in our metadata registry. The ledger still works.
false
allowed, none "allowed"
Numeric string. Always nonneg.
"0"
restricted is set by the platform on accounts created via
POST /v1/reserves. Customers can also pass it explicitly
to model reserves they build by hand.
standard, restricted Opaque, customer-defined identifier of the counterparty a
reserve account is held against. Set automatically by
POST /v1/reserves; ignored on non-reserve accounts.
"acme"
Customer-set grouping for funds segregation reporting.
The platform does not interpret this beyond grouping
accounts in GET /v1/reports/fund_segregation. Inherited
from the account's template when omitted on create.
client_held, operator, neutral Opaque custody-system identifier (e.g. fireblocks,
anchorage). Paired with custody_external_id: both
set or both null.
"fireblocks"
Provider-specific identifier (vault id, account id, etc.).
Paired with custody_provider.
"vault_42"
"2026-05-14T10:23:45.123456Z"