Agent skill · marketing growth · anthropics
zoom-oauth
Reference skill for Zoom authentication. Use after routing to an auth workflow when choosing app credentials, grant types, scopes, token refresh behavior, or debugging Zoom OAuth failures.
Why this skill is useful
Provides detailed guidance on Zoom OAuth flows, error handling, and token management that the AI wouldn't reliably generate on its own.
What it needs
Requires zoom account access. About 9k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
Zoom OAuth Background reference for Zoom auth and token lifecycle behavior. Prefer setup-zoom-oauth first, then use this skill for the exact flow, scope, and error details. Zoom OAuth Authentication and authorization for Zoom APIs. 📖 Complete Documentation For comprehensive guides, production patterns, and troubleshooting, see Integrated Index section below. Quick navigation: 5-Minute Runbook - Preflight checks before deep debugging OAuth Flows - Which flow to use and how each works Token Lifecycle - Expiration, refresh, and revocation Production Examples - Redis caching, MySQL storage, auto-refresh Troubleshooting - Error codes 4700-4741 Prerequisites Zoom app created in Marketplace Client ID and Client Secret For S2S OAuth: Account ID Four Authorization Use Cases Use Case App Type Grant Type Industry Name ---------- ---------- ------------ --------------- Account Authorization Server-to-Server accountcredentials Client Credentials Grant, M2M, Two-legged OAuth User Authorization General authorizationcode Authorization Code Grant, Three-legged OAuth Device Authorization General urn:ietf:params:oauth:grant-type:devicecode Device Authorization Grant (RFC 8628) Client Authorization General clientcredentials Client Credentials Grant (chatbot-scoped) Industry Terminology Term Meaning ------ --------- Two-legged OAuth No user involved (client ↔ server) Three-legged OAuth User involved (user ↔ client ↔ server) M2M Machine-to-Machine (backend services) Public client Can't keep secrets (mobile, SPA) → use PKCE Confidential client Can keep secrets (backend servers) PKCE Proof Key for Code Exchange (RFC 7636), pronounced "pixy" Which Flow Should I Use? --- Account Authorization (Server-to-Server OAuth) For backend automation without user interaction. Request Access Token Response Refresh Access tokens expire after 1 hour. No separate refresh flow - just request a new token. --- User Authorization (Authorization Code Flow) For apps that act on behalf of users. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/oauth