Rate limits & errors
How the API throttles requests and what each status code means.
Rate limits
These endpoints are unauthenticated, so usage is controlled by a per-IP rate limit rather than a per-account quota. Exceeding it returns 429 Too Many Requests; back off and retry rather than retrying immediately in a loop.
Odds move constantly, so poll the odds endpoints rather than requesting them in tight loops — and prefer the batch endpoints where they exist. “Market Odds” accepts up to ten market IDs in one call, which replaces ten separate requests.
Status codes
| Code | Meaning | What to do |
|---|---|---|
| 200 | Success | The response body carries the data. |
| 400 | Bad request | A required parameter is missing or malformed. |
| 404 | Not found | The ID in the path does not exist. |
| 429 | Too many requests | You have exceeded the rate limit — back off and retry. |
| 500 | Server error | Retry with backoff; contact support if it persists. |
Error shape
Errors return a JSON body with a message field describing what went wrong. Read the HTTP status first and the message second — the status is what your retry logic should branch on.