API Error Codes

For the general error-response envelope, authentication requirements, and rate-limit conventions, see API conventions.
How an error is returned
Gateway failures use an HTTP status code and an error payload. Matching-engine rejections are normally returned with HTTP400; the payload contains the applicable RejectReason code.
OrderRejected. Batch operations can return HTTP 202 Accepted while the final result is pending; use the relevant order or execution endpoint to retrieve the outcome.
Gateway API errors
Matching-engine rejection codes
The codes below are returned asRejectReason values. A code can apply to more than one endpoint; the operation group shows where it is expected to occur, not an exclusive mapping.
Place order
Amend or cancel-replace order
Cancel order
Shared and generic codes
Integration guidance
- Use the HTTP status to determine whether to retry, re-authenticate, or correct the request.
- For HTTP
400order rejections, branch on the returnedRejectReasonrather than parsing the human-readable message. - Do not retry validation, risk, precision, or order-state rejections unchanged. Correct the request first.
- Back off and retry only transient errors such as
429,503, or500; respect any rate-limit headers and use exponential backoff with jitter. - For
202 Acceptedbatch results, wait for the final status through the appropriate order or execution query rather than treating acceptance as execution.