Status codes
Standard HTTP status codes with a human-readable error message when requests fail.
Rate limits
Know your limits when accessing the Anchorage API to avoid 429 errors.
Idempotency
Required on certain endpoints to avoid duplicative operations.
Pagination
Paginate through pages of API results.
Status codes
| Code | Meaning |
|---|---|
200 OK | The request was successful. |
400 Bad Request | The request was improperly formed, often due to invalid syntax, insufficient funds, or a missing required parameter. |
401 Unauthorized | The request was missing a valid API key. |
403 Forbidden | The API key does not have permission to perform the requested action. |
404 Not Found | The requested resource does not exist. |
409 Conflict | The requested action cannot proceed because the resource is not in the required state. |
429 Too Many Requests | Too many requests were sent in a given amount of time. |
5xx | Something went wrong on Anchorage Digital’s side. |
Rate limits
Keys provisioned by an organization share one common rate limit. API requests are limited to20 requests/second per organization, allowing bursts of up to 100 requests within a single second.
Idempotency
Certain endpoints support idempotent requests so retries do not perform the same operation twice. For example, if a transfer request does not respond because of a network issue, retry with the same idempotent ID to ensure only one transfer is created. For supported endpoints, include a uniqueidempotentId in the POST request body.
Pagination
Cursor pagination is used for endpoints that return multiple records. Responses include anext cursor in the page attribute when more results are available.
| Parameter | Description |
|---|---|
afterId | Request a page after, or older than, this pagination ID. |
endDate | Request records older than this date in YYYY-MM-DD format. Used for /trading/trades and /trading/settlements. |
limit | Maximum number of results requested. Defaults vary by resource. |