Skip to main content

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 window
  • X-RateLimit-Remaining: Number of requests remaining in the current window
  • X-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 a 429 Too Many Requests response:

Best Practices

  1. Monitor Rate Limit Headers: Check X-RateLimit-Remaining to track your usage
  2. Implement Exponential Backoff: Retry failed requests with increasing delays
  3. Cache Responses: Cache frequently accessed data to reduce API calls
  4. Batch Operations: Use bulk endpoints when available to reduce request count

Example: Exponential Backoff

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
Both limits must be satisfied. If either limit is exceeded, you’ll receive a 429 response.

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:
  1. Contact support at support@qualifi.hr
  2. Provide details about your expected usage patterns
  3. Include your organization ID and use case description
Higher rate limits may be available for enterprise customers or specific use cases.

Next Steps

Error Handling

Learn how to handle API errors gracefully

Best Practices

Review best practices for API usage