> 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/gong-gao/open-api-qing-qiu-binlxian-zhi-geng-xin-gong-gao.md).

# Open API 請求頻率限制更新公告

我們將對 Omnichat Open API 的請求頻率限制執行方式進行調整。請詳閱以下變更內容，並評估對您目前整合設定的影響。

### **更新內容**

自 **2026 年 7 月 29 日起**，超過請求頻率限制的 API 呼叫將收到 **429 Too Many Requests** 錯誤回應。回應中將同時附上 Retry-After 標題，建議於 1 秒後重試。

### **頻率限制說明**

* 每個 Omnichat Team 帳號的預設請求頻率限制維持為**每秒 40 次**。頻率限制以 Team 為單位計算。
* 若您的 Team 下設有多個 API Token，所有 Token 的請求次數將合併計算。
* 此限制不區分 API 類型，所有 API 請求皆納入計算，包含透過 Insider 進階模組及 Racoon AI 整合所發出的請求。當達到上限時，該 Team 下的所有 Token 將同時受到限制。

### **建議您採取的行動**

**請在 7 月 29 日前檢視您的 API 使用狀況，確認是否在頻率限制範圍內。**同時建議在您的整合設定中加入 Retry 機制，以妥善處理 429 錯誤回應。

若您目前的整合已在頻率限制範圍內運作，且已具備重試機制，則無需進行任何變更。

### **需要協助？**

如對本次更新有任何疑問，或需要協助檢視您的整合設定，歡迎聯繫我們的支援團隊。您也可以參考 Omnichat Open API 文件以取得完整 API 資訊。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omnichat.ai/gong-gao/open-api-qing-qiu-binlxian-zhi-geng-xin-gong-gao.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.