Zoom Phone
Zoom Phone is the cloud PBX / UCaaS voice product of Zoom Communications, headquartered in San Jose, California, and sold worldwide from its United States home market. It replaces on-premise telephony with a cloud calling service — extensions, auto receptionists, IVR, call queues, shared line groups, voicemail, call recording, fax, emergency (E911) addressing, and SMS/MMS — delivered either on Zoom-provided PSTN service, on a customer's own carrier through BYOC and Cloud Peering (Provider Exchange), or resold through carrier partners. In the telecom value chain Zoom Phone sits above the network as a UCaaS application layer that buys wholesale connectivity and number inventory from carriers rather than operating a mobile network, and its API posture reflects the software half of that split rather than the carrier half: the Zoom Phone API is fully self-serve, published as downloadable OpenAPI 3.0 with 391 documented operations across 46 resource groups, a 71-event webhook catalog, a separate Number Management API covering number allocation, BYOC numbers, ported number orders, SIP trunks and 10DLC SMS campaigns, OAuth 2.0 with fine-grained phone:* scopes, a public Postman workspace, and an official Node/TypeScript SDK. It is not a mobile network operator, is not a GSMA Open Gateway signatory, and exposes no CAMARA network APIs — no CAMARA reference was found anywhere in its developer surface.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Zoom Phone the way a machine reads it — 63 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zoom Phone scores 72.4/100 (exemplar), with a separate agent-readiness read of 52/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Zoom Phone's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zoom-phone/"
title="Zoom Phone on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zoom-phone.svg"
alt="Zoom Phone Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/zoom-phone/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zoom-phone/"
title="Zoom Phone on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zoom-phone/card.svg"
alt="Zoom Phone Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Zoom Phone
Each block below is one kind of artifact we hold for Zoom Phone. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 51
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Zoom Phone Accounts API
The Accounts API from Zoom Phone — 2 operation(s) for accounts.
Zoom Phone Alerts API
The Alerts API from Zoom Phone — 2 operation(s) for alerts.
Zoom Phone Audio Library API
The Audio Library API from Zoom Phone — 3 operation(s) for audio library.
Zoom Phone Auto Receptionists API
The Auto Receptionists API from Zoom Phone — 10 operation(s) for auto receptionists.
Zoom Phone Billing Account API
The Billing Account API from Zoom Phone — 2 operation(s) for billing account.
Zoom Phone Blocked List API
The Blocked List API from Zoom Phone — 2 operation(s) for blocked list.
Zoom Phone Call Handling API
The Call Handling API from Zoom Phone — 2 operation(s) for call handling.
Zoom Phone Call Logs API
The Call Logs API from Zoom Phone — 15 operation(s) for call logs.
Zoom Phone Call Queues API
The Call Queues API from Zoom Phone — 18 operation(s) for call queues.
Zoom Phone Carrier Reseller API
The Carrier Reseller API from Zoom Phone — 2 operation(s) for carrier reseller.
Zoom Phone Cloud Peering Provider Exchange API
The Cloud Peering Provider Exchange API from Zoom Phone — 2 operation(s) for cloud peering provider exchange.
Zoom Phone Common Areas API
The Common Areas API from Zoom Phone — 14 operation(s) for common areas.
Zoom Phone Dashboard API
The Dashboard API from Zoom Phone — 11 operation(s) for dashboard.
Zoom Phone Device Line Keys API
The Device Line Keys API from Zoom Phone — 1 operation(s) for device line keys.
Zoom Phone Dial by Name Directory API
The Dial by Name Directory API from Zoom Phone — 2 operation(s) for dial by name directory.
Zoom Phone Emergency Addresses API
The Emergency Addresses API from Zoom Phone — 2 operation(s) for emergency addresses.
Zoom Phone Emergency Service Locations API
The Emergency Service Locations API from Zoom Phone — 3 operation(s) for emergency service locations.
Zoom Phone External Contacts API
The External Contacts API from Zoom Phone — 2 operation(s) for external contacts.
Zoom Phone Fax API
The Fax API from Zoom Phone — 6 operation(s) for fax.
Zoom Phone Firmware Update Rules API
The Firmware Update Rules API from Zoom Phone — 3 operation(s) for firmware update rules.
Zoom Phone Group Call Pickup API
The Group Call Pickup API from Zoom Phone — 4 operation(s) for group call pickup.
Zoom Phone Groups API
The Groups API from Zoom Phone — 2 operation(s) for groups.
Zoom Phone Inbound Blocked List API
The Inbound Blocked List API from Zoom Phone — 5 operation(s) for inbound blocked list.
Zoom Phone IVR API
The IVR API from Zoom Phone — 1 operation(s) for ivr.
Zoom Phone Line Keys API
The Line Keys API from Zoom Phone — 2 operation(s) for line keys.
Zoom Phone Monitoring Groups API
The Monitoring Groups API from Zoom Phone — 4 operation(s) for monitoring groups.
Zoom Phone Outbound Calling API
The Outbound Calling API from Zoom Phone — 12 operation(s) for outbound calling.
Zoom Phone Phone Devices API
The Phone Devices API from Zoom Phone — 8 operation(s) for phone devices.
Zoom Phone Phone Numbers API
The Phone Numbers API from Zoom Phone — 10 operation(s) for phone numbers.
Zoom Phone Phone Plan API
The Phone Plan API from Zoom Phone — 1 operation(s) for phone plan.
Zoom Phone Phone Plans API
The Phone Plans API from Zoom Phone — 2 operation(s) for phone plans.
Zoom Phone Phone Roles API
The Phone Roles API from Zoom Phone — 4 operation(s) for phone roles.
Zoom Phone Private Directory API
The Private Directory API from Zoom Phone — 2 operation(s) for private directory.
Zoom Phone Provider Exchange API
The Provider Exchange API from Zoom Phone — 2 operation(s) for provider exchange.
Zoom Phone Provision Templates API
The Provision Templates API from Zoom Phone — 2 operation(s) for provision templates.
Zoom Phone Recordings API
The Recordings API from Zoom Phone — 8 operation(s) for recordings.
Zoom Phone Reports API
The Reports API from Zoom Phone — 4 operation(s) for reports.
Zoom Phone Routing Rules API
The Routing Rules API from Zoom Phone — 2 operation(s) for routing rules.
Zoom Phone Setting API
The Setting API from Zoom Phone — 4 operation(s) for setting.
Zoom Phone Setting Templates API
The Setting Templates API from Zoom Phone — 2 operation(s) for setting templates.
Zoom Phone Settings API
The Settings API from Zoom Phone — 6 operation(s) for settings.
Zoom Phone Shared Line Appearance API
The Shared Line Appearance API from Zoom Phone — 1 operation(s) for shared line appearance.
Zoom Phone Shared Line Group API
The Shared Line Group API from Zoom Phone — 13 operation(s) for shared line group.
Zoom Phone Sites API
The Sites API from Zoom Phone — 4 operation(s) for sites.
Zoom Phone SMS API
The SMS API from Zoom Phone — 7 operation(s) for sms.
Zoom Phone SMS Campaign API
The SMS Campaign API from Zoom Phone — 6 operation(s) for sms campaign.
Zoom Phone SMS Campaigns API
The SMS Campaigns API from Zoom Phone — 3 operation(s) for sms campaigns.
Zoom Phone SMS Consent API
The SMS Consent API from Zoom Phone — 4 operation(s) for sms consent.
Zoom Phone Users API
The Users API from Zoom Phone — 13 operation(s) for users.
Zoom Phone Voicemails API
The Voicemails API from Zoom Phone — 6 operation(s) for voicemails.
Zoom Phone Zoom Rooms API
The Zoom Rooms API from Zoom Phone — 7 operation(s) for zoom rooms.
Scroll within the panel for all 51 ·
Open Collections 3
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Zoom MCP Server (Workspace)
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Zoom Phone Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Zoom Phone Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Zoom Phone — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
Access & Security 9
Authentication, authorization, and security posture
Scroll within the panel for all 9 ·
Operate 8
Status, limits, changes, and where to get help
Scroll within the panel for all 8 ·
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zoom-phone · machine-readable index on apis.io
This is an independent, third-party profile of Zoom Phone, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.