Rate Limits
OddsForge API uses rate limiting to ensure fair usage and prevent abuse.
Limits
| Tier | Limit | Scope | Endpoints |
|---|---|---|---|
| Global | 200 req/min | Per IP | All /api/* endpoints |
| Strict | 10 req/min | Per IP | POST /api/pool/trade, /deposit, /withdraw, /resolve, /cancel |
| API Key — Read | 120 req/min | Per API Key | All GET endpoints with API key |
| API Key — Write | 30 req/min | Per API Key | All POST endpoints with API key |
Rate Limit Headers
Every response includes these headers when using API key authentication:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the window |
X-RateLimit-Remaining | Remaining requests in the current window |
X-RateLimit-Reset | UNIX timestamp when the window resets |
Exceeding Limits
If you exceed the rate limit, you'll receive a 429 Too Many Requests response:
Response
429 Too Many Requests
{
"success": false,
"error": "Rate limit exceeded. Maximum 120 read requests per minute.",
"retry_after": 23
}
💡
Best Practice: Use the Batch Prices endpoint to fetch multiple markets in one request instead of making individual calls.
OddsForge