Scope of this section. Base URLs, authentication, versioning, rate limits,
reference-id format and the shared error-envelope shape are documented once in
the API reference overview and are not repeated
here.
New to accounts? Start with the Accounts guide. It covers
what an account is, the difference between
FIAT and ONRAMP, how to open one,
and the lifecycle. This page is the reference entry point.At a glance
The accounts endpoints run a higher rate limit than the platform default of
60 requests per minute. Both are per API key, and both answer with
429 ERRCORE_1006 carrying X-RateLimit-Limit and X-RateLimit-Remaining —
read the header rather than assuming either number.The endpoints
Response shape
Success bodies are unwrapped — a200 body is the account object itself, with
no data key to unwrap. Only errors use the five-key envelope.
Get account — 200
fundingInstructions are populated depends on the currency.
Fields that do not apply are omitted entirely, not returned as null.
Response by currency
A field matrix across all seven currency/category combinations, with a full
body for each.
Accounts errors
Every code the accounts endpoints raise, what causes it, and whether to retry.
Identifiers
Path ids are reference ids, not UUIDs — customers arecus_…, accounts are
acct_…, wallets are wlt_…. A wrongly-shaped acct_… or wlt_… id is a 400
(ERRREF_1000); a well-formed but unknown one is a 404 (ERRREF_1001). Different
fixes, so they are deliberately different codes. Customer ids are the exception:
any cus_… id that isn’t blank but doesn’t resolve — malformed, unknown, deleted
or another partner’s — is 404 ERRREF_1001, field userId. A blank userId is
400 ERRACC_1000 (User id is required, field userId).