API errors and troubleshooting
Understand validation errors, authentication, limits, and retries.
400 and 422: check the request
Read the error message. Verify currency identifiers, amount limits, the selected network, recipient address, and any destination memo. A corrected request can be submitted again.
401 and 404: check ownership
Sign in or send a valid local API key. An order belonging to another user or browser is returned as not found; possession of an exchange ID does not grant access.
403: check request origin
Browser writes must originate from this site. Server-to-server integrations can send requests directly with a bearer key; do not disable origin validation to embed privileged account operations.
429: slow down
The installation applies request limits. Wait before retrying instead of repeatedly submitting the same request.
502 and 503: provider configuration
When live mode is enabled, check the server provider credentials and connectivity. A provider error does not turn a live exchange into a demo exchange. Inspect an existing order before retrying creation.