Zoom Phone

Name: Phone API
Brand: Phone
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey, oauth2337 EndpointsREST

Install Jentic One Beta

Connect the Phone to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Phone, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzoom.us%2Fphone" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzoom.us%2Fphone" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Phone API.

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

GET STARTED

Start building with Phone API

Explore with Jentic One

View OpenAPI Document

For 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.

Use for: I need to an account's zoom phone settings, I want to add phone numbers for an account's customized outbound caller id, Search for an account's customized outbound caller id phone numbers, Find all phone numbers for an account's customized outbound caller id

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

Use Cases

Patterns agents use Phone API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

337 endpoints — you can access information from zoom with zoom phone apis to build private services or public applications on the [zoom app marketplace](https://marketplace.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Phone API through Jentic.

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.