canonical: https://jentic.com/apis/zoom.us

# Zoom APIs

Zoom is a communications platform whose APIs let developers work with video meetings and webinars, cloud phone, contact center, and video session storage on one account. Across four APIs on the api.zoom.us/v2 host, an application can schedule and manage meetings and webinars, register attendees and panelists, retrieve cloud recordings and analytics, configure Zoom Phone settings and outbound caller ID, manage contact center address books, and control Video SDK bring-your-own-storage locations.

## For AI agents

An agent can schedule Zoom meetings and webinars, register attendees, pull cloud recordings and analytics, manage phone account settings and outbound caller ID, maintain contact center address books, and configure Video SDK storage locations. All four APIs share the same Zoom account credential and v2 host, so one integration reaches meetings, phone, contact center, and video session storage.

## Scope

Use for: Automating Zoom video meetings and webinars, cloud phone settings, contact center address books, and Video SDK recording storage through the api.zoom.us v2 platform

Not supported:
- real-time media streams
- in-client meeting UI
- chat messaging
- payment processing
- endpoint device provisioning

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Phone | e-commerce | 337 | Programmatically list an account's zoom phone settings, add phone numbers for an account's customized outbound caller id. |
| Contact Center | crm | 225 | Programmatically create an address book, list address books. |
| Meetings | communications | 186 | Schedule and manage Zoom meetings and webinars, handle registrants and panelists, retrieve cloud recordings and archive files, and pull recording analytics. |
| Video SDK | identity-auth | 36 | Programmatically update bring your own storage settings, add storage location. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Schedule meetings and webinars, manage registrants and panelists, and retrieve cloud recordings and analytics | meetings | The Meetings API covers the full video meeting and webinar lifecycle plus cloud recording retrieval and recording analytics. |
| Configure Zoom Phone account settings, outbound caller ID numbers, and alert settings | phone | The Phone API manages the cloud phone system, including account phone settings and customized outbound caller ID. |
| Create and manage contact center address books and address book units | contact-center | The Contact Center API handles address book and unit records for contact center workflows. |
| Manage Video SDK bring-your-own-storage settings, storage locations, and session recordings | video-sdk | The Video SDK API controls storage location configuration and lists account and session recordings for embedded video sessions. |

## Cross-API use cases

### Schedule a meeting and store its recording

A workflow schedules a Zoom meeting or webinar and returns the join URL, then configures where the resulting video session recording is stored. The Meetings API creates the session and later retrieves its cloud recordings, while the Video SDK API sets the bring-your-own-storage location so recordings land in the account's chosen bucket.

Example prompt: Create a meeting with the Meetings API, then set the recording storage location with the Video SDK API and retrieve the recording after the session

### Unified voice and video contact for a customer

A support workflow keeps a customer reachable across channels by scheduling a Zoom meeting for a scheduled call and configuring the outbound caller ID used for phone follow-ups. The Meetings API books the video session and the Phone API sets the account's customized outbound caller ID number.

Example prompt: Schedule the meeting with the Meetings API, then add the customized outbound caller ID number with the Phone API

### Sync contact records with call routing

A contact center workflow maintains an address book of customers and pairs it with the phone account settings that route their calls. The Contact Center API creates and lists address books and units, and the Phone API reads and updates the account phone settings and alert configuration.

Example prompt: Create an address book with the Contact Center API, then read and update the related phone account settings with the Phone API

## Why Jentic

- **Setup:** Wiring Zoom by hand means running its OAuth 2.0 flow or setting the Authorization header, refreshing tokens, and mapping meeting, phone, contact center, and storage shapes against the api.zoom.us host yourself. Through Jentic you install Jentic One once, add the Zoom APIs you need from the Jentic API Directory, store the credential once, and your agent calls any of them.
- **Permission scoping:** Zoom addresses meetings, phone settings, address books, and storage locations by id in the URL path, so a rule in your own Jentic One instance can pin an agent to one resource and read or update it and nothing else. You choose which operations the agent may call, so destructive ones like deleting a meeting or an address book unit are excluded unless you add them.
- **Credential handling:** Your Zoom credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and the same stored credential can serve every Zoom API you add.
- **Discovery method:** Agents search Jentic by intent such as 'schedule a Zoom meeting', 'read Zoom Phone settings', or 'create an address book', and Jentic returns the matching Zoom operation with its input schema so the agent calls the right endpoint across the four APIs without browsing the reference docs.

## Related vendors

- **Webex** — Cisco's video meeting and webinar platform, an alternative for teams standardized on Cisco.
- **Google Workspace** — Google Calendar and Meet pair with Zoom for availability, scheduling, and alternative video sessions.
- **Twilio** — Programmable voice and messaging that complements Zoom Phone for telephony and contact routing.
- **Salesforce** — CRM that pairs with Zoom Contact Center address books for customer records and support workflows.

## FAQ

### What can an agent do across Zoom's APIs?

An agent can schedule and manage meetings and webinars, register attendees and panelists, retrieve cloud recordings and analytics, configure phone account settings and outbound caller ID, maintain contact center address books, and manage Video SDK storage locations and session recordings. Together the four APIs cover video, voice, contact center, and recording storage on one Zoom account.

### Do all four Zoom APIs use the same account and credential?

Yes. Meetings, Phone, Contact Center, and Video SDK all run on the api.zoom.us v2 host and use the same apiKey or OAuth 2.0 authorization model, so a single Zoom marketplace app credential with the correct scopes can reach every API.

### How do I choose between the Meetings API and the Video SDK API?

Use the Meetings API to schedule and run standard Zoom meetings and webinars and to retrieve their cloud recordings. Use the Video SDK API when you are configuring where recordings are stored through bring-your-own-storage settings and listing account or session recordings for embedded video sessions.

### Can these APIs handle both voice and video communication?

Yes. The Meetings API covers video meetings and webinars, and the Phone API covers the Zoom Phone cloud telephony system, including account phone settings and customized outbound caller ID. An agent can coordinate both from the same account.

### Which OAuth scopes do the different APIs need?

Each API requires its own OAuth scopes, such as phone settings scopes for the Phone API or meeting scopes for the Meetings API. Grant only the scopes the workflow needs when you register the marketplace app, since the account credential can span all four APIs.

### How does an agent connect to Zoom's APIs through Jentic?

You install Jentic One, then find and add the Zoom API you need from the Jentic API Directory. Your Zoom credential is stored encrypted by your own Jentic One instance, and the agent searches by intent, loads the matching operation schema, and executes the call with the credential injected at request time.