Throttling

Rate Limits

To ensure the stability and availability of our API service, we implement rate limiting on all API endpoints. This helps prevent abuse and ensures fair usage across all users.

Default Limits

By default, our API implements the following rate limits:

• Authenticated requests: 60 requests per minute
• Unauthenticated requests: 10 requests per minute

These limits are applied per IP address and API key.

Response Headers

When you make a request to our API, we include rate limit information in the response headers:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 59
X-RateLimit-Reset: 1620345678

• X-RateLimit-Limit: The maximum number of requests allowed per minute
• X-RateLimit-Remaining: The number of requests remaining in the current window
• X-RateLimit-Reset: The time at which the current rate limit window resets (Unix timestamp)

Rate Limit Exceeded

If you exceed the rate limit, you will receive a 429 Too Many Requests response with the following body:

{
  "error": "Too Many Requests",
  "message": "API rate limit exceeded",
  "retry_after": 30
}

The retry_after value indicates the number of seconds you should wait before making another request.

Best Practices

To avoid hitting rate limits:

1. Implement caching on your end for frequently accessed data
2. Use bulk operations where possible instead of making many individual requests
3. Implement exponential backoff when encountering rate limit errors
4. Consider implementing a queue system for non-time-sensitive operations

If you require higher rate limits for your application, please contact our support team.