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
Common money movement errors
These are the failures developers hit most often when moving assets, and how to resolve each.
A request that returns
201 can still fail at execution—after quorum approval or at broadcast—if there are insufficient funds for the network fee or a blockchain-level failure occurs. Track terminal status via Track movement status.
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.
Retries and backoff
Retry429 and 5xx responses with exponential backoff—for example, 1s, 2s, 4s, then 8s. When retrying a POST, reuse the same idempotentId so a request that succeeded but didn’t return its response doesn’t execute twice. Don’t retry other 4xx responses: they indicate a request that needs to be corrected, not repeated.
Pagination
Cursor pagination is used for endpoints that return multiple records. Responses include anext cursor in the page attribute when more results are available.