SDK Rate Limits
Learn about the rate limits for the Encatch Web and Mobile SDKs
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. These limits apply when using our Web SDK and Mobile SDKs.
Rate Limit Enforcement
Rate limits are applied per project, per contact/user ID, and per IP address. The following table shows the limits for each environment type:
Production projects
| Limit scope | Requests per minute |
|---|---|
| Per project | 40,000 |
| Per contact / user ID | 100 |
| Per IP address | 300 |
Sandbox projects
Sandbox projects are designed to let you test during implementation and throughout ongoing project development. They are not intended for production use. Their limits are set to avoid exhausting our systems while still supporting development workflows.
| Limit scope | Requests per minute |
|---|---|
| Per project | 50 |
| Per contact / user ID | 10 |
| Per IP address | 10 |
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 windowX-RateLimit-Remaining: The number of requests remaining in the current time windowX-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:
- Wait for the rate limit window to reset
- Implement exponential backoff in your application
- Consider caching responses to reduce API calls