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

# Zoom Phone

You can access information from Zoom with Zoom Phone APIs to build private services or public applications on the [Zoom App Marketplace](https://marketplace.zoom.us/). To learn how to get your credentials and create private or public applications, see Zoom APIs use [OAuth 2.0 authorization](https://developers.zoom.us/docs/integrations/oauth/). All endpoints are available through `https` at `api.zo. The API exposes 337 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically list an account's zoom phone settings, add phone numbers for an account's customized outbound caller id. Covers 337 operations with apiKey, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- List an account's Zoom phone settings
- Add phone numbers for an account's customized outbound caller ID
- Delete phone numbers for an account's customized outbound caller ID
- Get alert setting details
- Monitor Phone operational status and events

## Use cases

### E-Commerce Operations

Use the Phone to perform e commerce operations programmatically. The API provides 337 endpoints covering core functionality including list an account's zoom phone settings, add phone numbers for an account's customized outbound caller id, list an account's customized outbound caller id phone numbers.

Example prompt: Call GET /phone/account_settings to list an account's zoom phone settings

### Automated Phone Management

Automate phone operations by combining multiple Phone endpoints. Agents can add phone numbers for an account's customized outbound caller id and then list an account's customized outbound caller id phone numbers in a single workflow.

Example prompt: Call POST /phone/outbound_caller_id/customized_numbers to add phone numbers for an account's customized outbound caller id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Phone endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, oauth2 tokens manually.

Example prompt: Search Jentic for 'list an account's zoom phone settings', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /phone/account_settings | List an account's Zoom phone settings |
| POST | /phone/outbound_caller_id/customized_numbers | Add phone numbers for an account's customized outbound caller ID |
| GET | /phone/outbound_caller_id/customized_numbers | List an account's customized outbound caller ID phone numbers |
| DELETE | /phone/outbound_caller_id/customized_numbers | Delete phone numbers for an account's customized outbound caller ID |
| POST | /phone/alert_settings | Add an alert setting |
| GET | /phone/alert_settings | List alert settings with paging query |
| GET | /phone/alert_settings/{alertSettingId} | Get alert setting details |
| PATCH | /phone/alert_settings/{alertSettingId} | Update an alert setting |

## Key resources

- **Phone** — Operations for phone

## Why Jentic

- **Setup:** Wiring Zoom Phone by hand means handling its Authorization header token or OAuth2 scopes like phone:read:admin, pointing at the single api.zoom.us/v2 host, and managing token refresh yourself. Through Jentic you install once, import Zoom Phone from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Zoom Phone puts the setting id in the URL path (/phone/alert_settings/{alertSettingId}), so a rule can pin your agent to one alert setting: it can read and patch that setting and nothing else. You choose the operations it may call, so destructive ones like deleting a customized caller-id number are not included unless you add them.
- **Credential handling:** Your Zoom Phone token 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.
- **Discovery method:** Agents search Jentic by intent such as 'read an account's Zoom Phone settings' or 'update phone alert settings', and Jentic returns the matching Zoom Phone operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Phone use?

The Phone uses apiKey, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list an account's zoom phone settings with the Phone?

Yes. Use the GET /phone/account_settings endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Phone?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list an account's zoom phone settings through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list an account's zoom phone settings'. Jentic returns the matching Phone operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Phone have?

The Phone exposes 337 endpoints covering phone operations.

### Can I limit what my agent is allowed to do with the Zoom Phone API?

Yes. Because you run Jentic One yourself, your own rules decide which Zoom Phone operations and credentials the agent may use. Zoom Phone puts the setting id in the URL path (/phone/alert_settings/{alertSettingId}), so a rule can pin the agent to a single alert setting, letting it read and patch that one setting and nothing else. You pick the operations it can call, so destructive ones like deleting a customized outbound caller-id number are left out unless you add them.