Rate Limits

We enforce rate limits to prevent abuse and ensure that the APIs (called from SDKs for feedback fetching and submission) is used fairly by all users.

Rate Limit Enforcement

The rate limits are applied on a combination of user's IP address and API key generated for the environment (test or production). The following table shows the rate limits for different API endpoints for each environment:

Rate Limit Headers

When you make requests to the API, you'll receive rate limit information in the response headers:

• X-RateLimit-Limit: The maximum number of requests allowed per time window
• X-RateLimit-Remaining: The number of requests remaining in the current time window
• X-RateLimit-Reset: The time at which the current rate limit window resets (Unix timestamp in seconds)

Handling Rate Limits

When you exceed the rate limit, you'll receive a 429 Too Many Requests response. You should:

1. Wait for the rate limit window to reset
2. Implement exponential backoff in your application
3. Consider caching responses to reduce API calls

Best Practices

• Monitor your rate limit usage through the response headers
• Implement proper error handling for 429 responses
• Use caching to minimize API calls
• Reach out to us if your usecase requires customized rate limits