API Rate Limits

Understanding rate limits and usage guidelines for optimal API integration and performance.

Throttling

Our API implements intelligent throttling to ensure fair usage and optimal performance for all users:

• Request Rate Limiting: Limits based on requests per minute and per hour
• Burst Protection: Temporary allowances for short bursts of traffic
• Gradual Backoff: Automatic retry mechanisms with exponential backoff
• Fair Usage: Dynamic limits based on subscription tier and usage patterns

Error Handling

When rate limits are exceeded, the API returns specific error codes and headers:

HTTP/1.1 429 Too Many Requests
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1640995200
Retry-After: 60

{
  "error": "rate_limit_exceeded",
  "message": "API rate limit exceeded",
  "retry_after": 60
}

Best Practices

Follow these guidelines to optimize your API usage and avoid rate limiting:

• Implement Caching: Cache responses to reduce redundant API calls
• Batch Requests: Use bulk endpoints when available for multiple lookups
• Monitor Headers: Check rate limit headers in responses to track usage
• Implement Retry Logic: Use exponential backoff for failed requests
• Optimize Timing: Spread requests evenly rather than bursting
• Upgrade Plans: Consider higher tiers for increased limits

Rate Limit Tiers