domain: developers.zoom.us · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get an OAuth access token (a Server-to-Server OAuth app is typical for backend automation) with webinar:write scope.
POST to https://api.zoom.us/v2/users/{userId}/webinars with topic, start_time, duration, timezone, and a settings object (e.g., approval_type, practice_session, hd_video).
Confirm the host account has a paid plan with the Webinar add-on license, since the call fails otherwise.
Read back the id (webinar ID), join_url (for host/panelists), and registration_url if approval_type requires registration.
Set recurrence in the body for a recurring webinar series instead of calling create repeatedly.
Known gotchas
Webinars require a distinct license/add-on from regular Zoom Meetings — an OAuth app scoped only for meetings will fail even with otherwise-valid auth.
Some settings fields (like practice_session or hd_video) silently no-op if the account plan doesn't support them, rather than returning an error.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?