> 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/admin-corner/third-party-integrations/zoom-calendaring-integration-explainer/appendix.md).

# Appendix

### Service and authentication method matrix

<table data-header-hidden="false" data-header-sticky><thead><tr><th></th><th>Service</th><th>Auth Method</th><th>Zoom Calendaring Service Stores</th><th>Endpoint Receives at Sign-In</th><th>Endpoint Retrieves Calendar From</th></tr></thead><tbody><tr><td><strong>User Calendars</strong></td><td>Microsoft 365</td><td>OAuth</td><td>Access and refresh token for each user account.</td><td>Access token from Zoom Calendaring Service.</td><td>Microsoft 365</td></tr><tr><td><strong>Exchange Server</strong></td><td>Basic</td><td>Username and password for each user account.</td><td>Username and password from Zoom Calendaring Service.</td><td>Exchange Server</td><td></td></tr><tr><td><strong>Google Workspace</strong></td><td>OAuth</td><td>Access and refresh token for each user account.</td><td>Access token from Zoom Calendaring Service.</td><td>Google Workspace</td><td></td></tr><tr><td><p><strong>Zoom Rooms</strong></p><p><br></p></td><td>Microsoft 365</td><td>OAuth</td><td>Access and refresh token for the Zoom Rooms service account.</td><td>Access token for Zoom Rooms service account from Zoom Calendaring Service.</td><td>Microsoft 365</td></tr><tr><td><strong>Exchange Server</strong></td><td>Basic</td><td>Username and password for the Zoom Rooms service account.</td><td>Username and password for the Zoom Rooms service account from Zoom Calendaring Service.</td><td>Exchange Server</td><td></td></tr><tr><td><strong>Google Workspace</strong></td><td>OAuth</td><td>Access and refresh token for the Zoom Rooms service account.</td><td>Access token for Zoom Rooms service account from Zoom Calendaring Service.</td><td>Google Workspace</td><td></td></tr><tr><td><strong>Enhanced API Connector (EAC)</strong></td><td>Microsoft 365</td><td>OAuth</td><td>Access and refresh token for the EAC service account.</td><td>Calendaring data</td><td>Enhanced API Connector*</td></tr><tr><td><strong>Exchange Server</strong></td><td>Basic</td><td>Username and password for the EAC service account.</td><td>Calendaring data</td><td>Enhanced API Connector*</td><td></td></tr><tr><td><strong>Google Workspace</strong></td><td>OAuth</td><td>Access and refresh token for the EAC service account.</td><td>Calendaring data</td><td>Enhanced API Connector*</td><td></td></tr></tbody></table>

{% hint style="info" %}
\*EAC endpoints retrieve their calendaring data from the EAC, which in turn retrieves its calendaring data from the Zoom Calendaring Service. In other words, the EAC service and its associated endpoints do not connect to Microsoft 365, Exchange, or Google Workspace.
{% endhint %}


---

# 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/admin-corner/third-party-integrations/zoom-calendaring-integration-explainer/appendix.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.