Skip to main content

HTTP Status Codes

Error Response Format

All errors follow a consistent JSON format:

Common Error Types

Authentication Errors

INVALID_API_KEY

INVALID_SIGNATURE

Trading Errors

INSUFFICIENT_BALANCE

ORDER_NOT_FOUND

Smart Routing & Execution Errors

Smart order endpoints return errors with a top-level success: false payload instead of the nested error object used by legacy endpoints.

CREDENTIAL_ERROR

ROUTING_ERROR

EXECUTION_ERROR

Rate Limiting Errors

RATE_LIMIT_EXCEEDED

Error Handling Best Practices

1. Implement Retry Logic

2. Handle Specific Error Types

Support and Debugging

When reporting errors:
  1. Include the requestId from the error response
  2. Provide the full error response (sanitize sensitive data)
  3. Include request details (endpoint, parameters, timestamp)
  4. Describe the expected behavior
Contact support:
Always validate input parameters before making API calls to avoid unnecessary errors and rate limit consumption.