How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Zoom Phone

Zoom Phone Users API

The Users API from Zoom Phone — 13 operation(s) for users.

Documentation Provider Profile APIs.io OpenAPI GitHub

Zoom Phone Users API is one of 51 APIs that Zoom Phone publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 24 operations across 13 paths. It is described by OpenAPI 3.2.0, at version 2.

Requests are made against a single base URL, https://api.zoom.us/v2.

24 operations 13 paths 0 schemas 5 DELETE6 GET5 PATCH6 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2
Base URL
https://api.zoom.us/v2
Authentication
API Key, OAuth 2.0
Contact
Zoom Developers
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

Zoom Phone Users API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (openapi_authorization). It supports OAuth 2.0 (openapi_oauth) using the authorizationCode flow, exposing 410 scopes.

Paths & Operations 24

Across 13 paths, the API surfaces 24 operations — 5 DELETE, 6 GET, 5 PATCH, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Users 24
GET
/phone/users
List phone users
listPhoneUsers 8 params → 200400404429
PUT
/phone/users/batch
Update multiple users' properties in batch
updateUsersPropertiesInBatch body → 204400404429
POST
/phone/users/batch
Batch add users
batchAddUsers body → 201400404429
GET
/phone/users/{userId}
Get a user's profile
phoneUser 1 param → 200400404429
PATCH
/phone/users/{userId}
Update a user's profile
updateUserProfile 1 param body → 204400404429
POST
/phone/users/{userId}/call_forward_settings/{hourType}
Add user call forward setting
addUserCallForwardSetting 2 params body → 201400404
DELETE
/phone/users/{userId}/call_forward_settings/{hourType}
Delete user call forward setting
deleteUserCallForwardSetting 3 params → 204400404
GET
/phone/users/{userId}/call_handling/settings
Get user call handling setting
getUserCallHandlingSetting 4 params → 200400404
PATCH
/phone/users/{userId}/call_handling/settings/{hourType}
Update user call handling setting
updateUserCallHandlingSetting 2 params body → 204400404
PUT
/phone/users/{userId}/calling_plans
Update user's calling plan
updateCallingPlan 1 param body → 204400404429
POST
/phone/users/{userId}/calling_plans
Assign calling plan to a user
assignCallingPlan 1 param body → 200400404429
DELETE
/phone/users/{userId}/calling_plans/{planType}
Unassign user's calling plan
unassignCallingPlan 3 params → 204400404429
GET
/phone/users/{userId}/outbound_caller_id/customized_numbers
List users' phone numbers for a customized outbound caller ID
listUserCustomizeOutboundCallerNumbers 7 params → 200400404429
POST
/phone/users/{userId}/outbound_caller_id/customized_numbers
Add phone numbers for users' customized outbound caller ID
addUserOutboundCallerNumbers 1 param body → 201400404429
DELETE
/phone/users/{userId}/outbound_caller_id/customized_numbers
Remove users' customized outbound caller ID phone numbers
deleteUserOutboundCallerNumbers 2 params → 204400429
GET
/phone/users/{userId}/policies/{policyType}
Get user policy details
GetUserPolicyDetails 2 params → 200400404429
PATCH
/phone/users/{userId}/policies/{policyType}
Update user policy
updateUserPolicy 2 params body → 204400404429
POST
/phone/users/{userId}/profile_settings/{settingType}
Add a user's profile setting
addUserProfileSetting 2 params body → 201400404
DELETE
/phone/users/{userId}/profile_settings/{settingType}
Delete a user's profile profile setting
deleteUserProfileSetting 4 params → 204400404
GET
/phone/users/{userId}/settings
Get a user's profile settings
phoneUserSettings 1 param → 200400404429
PATCH
/phone/users/{userId}/settings
Update a user's profile settings
updateUserSettings 1 param body → 204400404429
POST
/phone/users/{userId}/settings/{settingType}
Add a user's shared access setting
addUserSetting 2 params body → 201400404429
DELETE
/phone/users/{userId}/settings/{settingType}
Delete a user's shared access setting
deleteUserSetting 6 params → 204400404429
PATCH
/phone/users/{userId}/settings/{settingType}
Update a user's shared access setting
updateUserSetting 2 params body → 204400404429

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoom-phone-users-api-openapi.yml Raw ↑

Other APIs Zoom Phone publishes across the network.

Zoom Phone Accounts API
AE Profile APIs.io
Zoom Phone Alerts API
AE Profile APIs.io
Zoom Phone Audio Library API
AE Profile APIs.io
Zoom Phone Auto Receptionists API
AE Profile APIs.io
Zoom Phone Billing Account API
AE Profile APIs.io
Zoom Phone Blocked List API
AE Profile APIs.io
Zoom Phone Call Handling API
AE Profile APIs.io
Zoom Phone Call Logs API
AE Profile APIs.io
Zoom Phone Call Queues API
AE Profile APIs.io
Zoom Phone Carrier Reseller API
AE Profile APIs.io
Zoom Phone Cloud Peering Provider Exchange API
AE Profile APIs.io
Zoom Phone Common Areas API
AE Profile APIs.io
#User
← Back to Z APIs
API Details
ID
zoom-phone:zoom-phone-users-api
Base URL
https://api.zoom.us/v2
Docs
https://developers.zoom.us/docs/api/phone/
Provider
Zoom Phone
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=zoom-phone-users-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/zoom-phone-users-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Zoom Phone Users API, 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.