Quick Reference - Key rate limits at a glance:
| Operation Type | Limit |
|---|---|
| Core | 10,000 requests/minute |
| Standard | 20,000 requests/minute |
CometChat REST API Rate Limits
The rate limits below are for general applications. Rate limits can be adjusted on a per-need basis, depending on your use case and plan. The rate limits are cumulative. For example: if the rate limit for core operations is 10,000 requests per minute, then you can login a user, add a user to a group, remove a user from a group, etc. for a combined total of 10,000 requests per minute.
| Operation Type | Rate Limit | Examples |
|---|---|---|
| Core Operations | 10,000 requests per minute | User login, create/delete user, create/join group (cumulative) |
| Standard Operations | 20,000 requests per minute | All other operations (cumulative) |
What Happens When the Rate Limit is Reached?
The request isn’t processed and a response is sent containing a429 response code. Along with the response code, there will be a couple of headers sent which specify the time in seconds that you must wait before you can try the request again.
Is There an Endpoint That Returns Rate Limits?
No, CometChat does not provide a dedicated rate-limit endpoint. However, the following response headers are included with every API response, which you can use to confirm the app’s current rate limit and monitor the number of requests remaining in the current minute:Best Practices
Best Practices
- Monitor
X-Rate-Limit-Remainingheaders to proactively manage your request volume - Implement exponential backoff when you receive a
429response - Use the
Retry-Afterheader value to determine when to retry - Batch operations where possible to reduce the total number of API calls
- Cache responses locally to avoid redundant requests
Troubleshooting
Troubleshooting
- Receiving 429 errors frequently: Review your request patterns and consider batching or caching
- Rate limit seems too low: Contact CometChat support to discuss adjustments based on your plan and use case
- Inconsistent rate limit headers: Ensure you’re reading headers from the correct response object in your HTTP client