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

Zoom User API

User operations

Zoom User API is one of 47 APIs that Zoom 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 20 operations across 20 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

20 operations 20 paths 0 schemas 20 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.zoom.us/v2
Authentication
API Key, API Key
License
Resource Areas
1

Authentication & Security 2

Zoom User API declares 2 security schemes for authenticating requests. An API key is passed in the query as api_key (api_key). An API key is passed in the query as api_secret (api_secret). By default, every request must be authenticated.

Paths & Operations 20

Across 20 paths, the API surfaces 20 operations — 20 POST. Each is listed below with its method, path, parameters, and response codes.

User 20

User operations

POST
/user/assistant/delete
User assistant delete
userAssistantDelete body → 200
POST
/user/assistant/set
User assistant set
userAssistantSet body → 200
POST
/user/autocreate
User autocreate
userAutocreate body → 200
POST
/user/checkemail
User checkemail
userCheckemail body → 200
POST
/user/checkzpk
User checkzpk
userCheckzpk body → 200
POST
/user/create
User create
userCreate body → 200
POST
/user/custcreate
User custcreate
userCustcreate body → 200
POST
/user/activate
User activate
userActivate body → 200
POST
/user/deactivate
User deactivate
userDeactivate body → 200
POST
/user/delete
User delete
userDelete body → 200
POST
/user/get
User get
userGet body → 200
POST
/user/getbyemail
User getbyemail
userGetbyemail body → 200
POST
/user/list
User list
userList body → 200
POST
/user/pending
User pending
userPending body → 200
POST
/user/permanentdelete
User permanentdelete
userPermanentdelete body → 200
POST
/user/revoketoken
User revoketoken
userRevoketoken body → 200
POST
/user/scheduleforhost/list
User scheduleforhost list
userScheduleforhostList body → 200
POST
/user/ssocreate
User ssocreate
userSsocreate body → 200
POST
/user/update
User update
userUpdate body → 200
POST
/user/updatepassword
User updatepassword
userUpdatepassword body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoom-user-api-openapi.yml Raw ↑

Other APIs Zoom publishes across the network.

Zoom Meeting API
Zoom Phone API
Zoom Team Chat API
Zoom Contact Center API
Zoom Webinars Plus and Events API
Zoom Marketplace API
Zoom Revenue Accelerator API
Zoom Whiteboard API
Zoom Rooms API
Zoom Clips API
Zoom Mail API
Zoom Calendar API
Where this information came from

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