HTTP errors
Common transport and authentication errors across the API.
| HTTP status | Meaning | Next action |
|---|---|---|
| 401 | Invalid or missing credentials | Check both authentication headers and account activation. |
| 403 | Source IP not allowed | Check your backend's outbound IP against the account allowlist. |
| 404 | Resource not found | Check the resource identifier and authenticated account. |
| 409 | Deposit idempotency conflict | Reconcile the original operation; do not reuse a key with different data. |
| 422 | Invalid request | Check the endpoint's fields, types and required parameters. |
| 429 | Rate limited | Honor Retry-After and reduce request frequency. |
| 503 | Unavailable capability or service | Inspect the code. FEATURE_NOT_AVAILABLE requires account access, not repeated retries. |
HTTP status is not trade status
A 202 response accepts work for processing. A network error does not prove it failed. Use the deposit or withdrawal lookup and signed events to determine the actual outcome.