Skip to main content
Rate limits help ensure fair usage and system stability. Limits are applied per API key based on your subscription plan.

Rate Limit Tiers

  • Starter/Standard: 500 requests/hour
  • Professional/Premium: 5,000 requests/hour
  • Enterprise: 50,000 requests/hour

Rate Limit Headers

Every API response includes rate limit information in the headers:
  • X-RateLimit-Limit: Your hourly limit
  • X-RateLimit-Remaining: Requests remaining in the current window
  • X-RateLimit-Reset: Unix timestamp when the limit resets

Rate Limit Errors

When you exceed your rate limit, you’ll receive a 429 Too Many Requests response:
The retryAfter field indicates how many seconds to wait before retrying.

Per-Key Rate Limits

You can set custom rate limits for individual API keys when creating them:
This allows you to have different rate limits for different use cases.

Best Practices

  1. Monitor your usage - Check the X-RateLimit-Remaining header
  2. Implement exponential backoff - When you hit rate limits, wait before retrying
  3. Use webhooks - Instead of polling, use webhooks for real-time updates
  4. Cache responses - Cache data that doesn’t change frequently
  5. Batch requests - Combine multiple operations when possible

Handling Rate Limits

Exponential Backoff

Rate Limit Monitoring