build-zoom-rest-api-app

This is a reference and background-knowledge skill for building server-side integrations against the Zoom REST API. It exists to solve a discovery-and-correctness problem: Zoom exposes 600+ endpoints across meetings, users, webinars, recordings, reports, phone, contact center, and many other domains, and developers routinely get tripped up by authentication modes, identifier formats, regional routing, and rate limits. The skill provides endpoint selection guidance, resource-management patterns, OAuth requirements, rate-limit awareness, and API error debugging so an agent can generate deterministic, working Zoom automation.

The content is organized into concept docs (API architecture, authentication flows, rate-limiting strategy, meeting URLs vs SDK joining), worked examples (meeting lifecycle, webhook server with CRC validation, recording pipeline, user management), and a large library of per-domain reference files aligned to Zoom's official API Hub endpoints.json inventories. It documents Server-to-Server, User, PKCE, and Device Code OAuth flows, the `me` keyword semantics per app type, meeting ID vs UUID handling with double-URL-encoding, ISO 8601 time formats, authenticated download_url retrieval, and regional/data-residency base URLs. Troubleshooting playbooks cover common errors, token/scope failures, pagination, and forum-derived FAQs.

The target users are backend and integration developers, platform engineers, and automation authors building against Zoom programmatically, plus AI agents that need authoritative endpoint-level detail after a higher-level planning skill has chosen an API workflow. Typical use cases include provisioning users, creating and managing meetings/webinars, downloading cloud recordings via webhooks, and debugging 401/429 responses.