Rate Limit Overview
The Gather API implements rate limiting to ensure fair usage and system stability. Rate limits are applied per API key.Default Limits
- Per Hour: 1000 requests per hour per API key
- Burst: 100 requests per minute
- Scope: Limits are applied per API key independently
Rate limits are subject to change. Contact support if you need higher limits
for your use case.
Rate Limit Headers
All API responses include rate limit information in the response headers:X-RateLimit-Limit: Maximum number of requests allowed in the current windowX-RateLimit-Remaining: Number of requests remaining in the current windowX-RateLimit-Reset: Unix timestamp (seconds) when the rate limit window resets
Example Response Headers
Handling Rate Limits
429 Too Many Requests
When you exceed the rate limit, you’ll receive a429 Too Many Requests response:
Best Practices
- Monitor Rate Limit Headers: Check
X-RateLimit-Remainingto track your usage - Implement Exponential Backoff: Retry failed requests with increasing delays
- Cache Responses: Cache frequently accessed data to reduce API calls
- Batch Operations: Use bulk endpoints when available to reduce request count
Example: Exponential Backoff
- JavaScript
- Python
Rate Limit Windows
Rate limits are calculated using sliding windows:- Hourly Window: 1000 requests per hour, calculated on a rolling 60-minute window
- Burst Window: 100 requests per minute, calculated on a rolling 60-second window
Monitoring Your Usage
Check rate limit headers in every response to monitor your usage:Requesting Higher Limits
If you need higher rate limits for your use case:- Contact support at [email protected]
- Provide details about your expected usage patterns
- Include your organization ID and use case description
Higher rate limits may be available for enterprise customers or specific use
cases.

