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 Meeting Registrants API

Manage meeting registration and registrants.

Zoom Meeting Registrants API is one of 47 APIs that Zoom publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 3 paths, and defines 5 schemas. 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.

4 operations 3 paths 5 schemas 1 GET2 POST1 PUT

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 Meeting Registrants 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 4

Across 3 paths, the API surfaces 4 operations — 1 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Meeting Registrants 4

Manage meeting registration and registrants.

GET
/meetings/{meetingId}/registrants
Zoom List Meeting Registrants
listMeetingRegistrants 5 params → 200400401404
POST
/meetings/{meetingId}/registrants
Zoom Add a Meeting Registrant
addMeetingRegistrant 2 params body → 201400401404
PUT
/meetings/{meetingId}/registrants/status
Zoom Update Registrant Status
updateMeetingRegistrantStatus 2 params body → 204400401404
POST
/meetings/{meetingId}/batch_registrants
Zoom Batch Add Meeting Registrants
batchAddMeetingRegistrants 1 param body → 201400401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Registrant (20 properties), RegistrantCreateRequest (19 properties), RegistrantList (6 properties), RegistrantCreateResponse (6 properties). Each schema is shown below with its type and property counts.

Registrant
object
20 properties
RegistrantCreateResponse
object
6 properties
RegistrantCreateRequest
object
19 properties 2 required
RegistrantList
object
6 properties
ErrorResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zoom-meeting-registrants-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 Meeting Registrants 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.