Skip to main content

Rate Limits and Errors

Rate Limits​

Public APIs are protected by server-side rate limiting.

Recommended client behavior:

  1. retry only when appropriate
  2. add exponential backoff with jitter
  3. avoid concurrent burst retries

HTTP Status Codes​

CodeMeaning
200success
400invalid request
401unauthorized
404resource not found
409conflict
429rate limited
500server error
502upstream/provider error

Typical Error Payload​

{
  "error": "Failed to fetch market data",
  "message": "Unknown error"
}

Some endpoints return only error when no additional details are needed.

Integration Guidance​

  • treat all numeric fields as strings unless documented otherwise
  • validate nullable fields (null can be expected when markets are thin or new)
  • design clients to tolerate additive fields in responses