> For the complete documentation index, see [llms.txt](https://docs.omnichat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnichat.ai/en/announcements/upcoming-changes-to-open-api-rate-limits.md).

# Upcoming Changes to Open API Rate Limits

Effective August 26, 2026

We are updating how rate limits are enforced on the Omnichat Open API. Please review the changes below and assess any impact on your current integration.

### **What is changing**

Starting **August 26, 2026,** requests that exceed the rate limit will return a 429 Too Many Requests error. A Retry-After header will be included in the response, indicating a 1-second wait before your next retry.

### **How the rate limit works**

* The default rate limit remains **40 requests per second** per Omnichat Team account. 
* The limit is calculated at the Team level. If your Team has multiple API tokens, **requests across all tokens are counted together.** 
* The limit applies to all API types without exception, including calls made through the Insider advanced module and Racoon AI integrations. **When the limit is reached, all tokens under your Team will be affected simultaneously.**

### **What you need to do**

Review your API usage ahead of August 26 to ensure you are within the rate limit. We also recommend implementing a Retry mechanism in your integration to handle 429 responses gracefully.

If your integration is already operating within the limit and has retry logic in place, no further action is required.

### **Need help?**

If you have questions about this update or need assistance reviewing your integration, please contact our support team. You can also refer to our Open API Documentation for full API details.