Rate Limiting

Understand rate limits and how to handle them.

Overview #

The API enforces rate limits to ensure fair usage and service stability. Each API key is limited to 100 requests per minute.

Rate Limit Response #

When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header:

429 Too Many Requests

HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: application/json

{
  "status": 429,
  "title": "Too Many Requests",
  "detail": "Rate limit exceeded. Try again later."
}

Best Practices #

To stay within rate limits:

• Cache responses when possible — avoid redundant requests for the same data
• Use pagination — fetch only the data you need with page and pageSize parameters
• Implement exponential backoff — when you receive a 429, wait before retrying
• Batch your operations — group related reads together rather than making many small requests