> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/technical-library/zh-tw/ai-whitepaper/apis.md).

# API

## API

Zoom 提供多種 API 端點，以滿足客戶和開發者的多元需求。這些 API 讓組織能夠將 Zoom 強大的通訊功能無縫整合到現有工作流程中，延伸功能，並打造符合特定商業需求的客製化解決方案。

目前，Zoom 的許多 AI 功能——例如會議摘要、會議逐字稿和電話逐字稿——都與個別的 Zoom 產品密切相關。因此，與這些功能相關的 API 會透過各自的產品專屬 API 端點來存取。除了可在 AI 聊天面板中封存對話的功能之外，Zoom 目前不提供 AI 功能的 API 存取。

如需有關 Zoom AI API 的詳細資訊以及入門指引，請造訪 [Zoom 開發者中心](https://developers.zoom.us/docs/api/).

## MCP

請參閱 Zoom 的開發者中心，以取得更多關於 [在 Zoom 開始使用 MCP](https://developers.zoom.us/docs/mcp/). 


---

# 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://library.zoom.com/technical-library/zh-tw/ai-whitepaper/apis.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.