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

# APIs

## APIs

Zoom offers a wide range of API endpoints to meet the diverse needs of customers and developers. These APIs enable organizations to seamlessly integrate Zoom’s robust communication features into existing workflows, extend functionality, and build custom solutions tailored to specific business requirements.

Currently, many of Zoom's AI features—such as Meeting Summaries, Meeting Transcripts, and Phone Transcripts—are closely tied to individual Zoom products. As a result, APIs related to these features are accessed through their respective product-specific API endpoints. Except for the ability to archive conversations within the AI Chat panel, Zoom does not currently provide API access to AI features.

For detailed information on Zoom AI APIs and guidance on getting started, visit the [Zoom Developer Center](https://developers.zoom.us/docs/api/).

## MCP

Refer to Zoom's developer center for more information on [getting started with MCP at Zoom](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/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.