Skip to main content
An account is where a customer receives money. Open one in a supported currency and Endl returns the bank coordinates to give a payer — and, for an on-ramp account, what those funds convert into on arrival.
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.
The one convention worth repeating. A successful response is the bare object. There is no envelope around it — only errors are enveloped.
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 — a 200 body is the account object itself, with no data key to unwrap. Only errors use the five-key envelope.
Get account — 200
Which keys inside 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 are cus_…, accounts are acct_…, wallets are wlt_…. A wrongly-shaped 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.