Rate Limits

Rate limits protect the API from abuse and ensure fair usage across all customers. Understanding and properly handling rate limits is essential for building reliable integrations.

Rate Limit Tiers

Rate limits vary by plan tier and endpoint type.

* Subject to fair use policy and infrastructure capacity

Endpoint-Specific Limits

Response Headers

Every API response includes headers to help you track your rate limit status.

X-RateLimit-Limit: 300
X-RateLimit-Remaining: 245
X-RateLimit-Reset: 1705312800
X-RateLimit-Window: 60

Handling 429 Errors

When you exceed the rate limit, the API returns a 429 Too Many Requests response.

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

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Rate limit exceeded. Please retry after 30 seconds.",
    "retry_after": 30
  }
}

Implementing Retry Logic

async function apiRequestWithRetry(url, options, maxRetries = 3) {
  for (let attempt = 0; attempt <= maxRetries; attempt++) {
    const response = await fetch(url, options);
    
    if (response.status === 429) {
      const retryAfter = response.headers.get('Retry-After') || 
        Math.pow(2, attempt) * 1000;
      
      console.log(`Rate limited. Retrying in ${retryAfter}ms`);
      await new Promise(r => setTimeout(r, retryAfter));
      continue;
    }
    
    return response;
  }
  
  throw new Error('Max retries exceeded');
}

Best Practices

Requesting Higher Limits

If your use case requires higher rate limits, contact our team to discuss custom plans.