> 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/ai/ai-whitepaper/apis.md).

# API

Zoom AI 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.zoom.com/technical-library/zh/ai/ai-whitepaper/apis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.