zoom-oauth

Files (23)

• RUNBOOK.md
• SKILL.md
• oauth-flows.md · concepts/
• pkce.md · concepts/
• scopes-architecture.md · concepts/
• state-parameter.md · concepts/
• token-lifecycle.md · concepts/
• device-flow.md · examples/
• pkce-implementation.md · examples/
• s2s-oauth-basic.md · examples/
• s2s-oauth-redis.md · examples/
• token-refresh.md · examples/
• user-oauth-basic.md · examples/
• user-oauth-mysql.md · examples/
• classic-scopes.md · references/
• environment-variables.md · references/
• full-guide.md · references/
• granular-scopes.md · references/
• oauth-errors.md · references/
• common-errors.md · troubleshooting/
• redirect-uri-issues.md · troubleshooting/
• scope-issues.md · troubleshooting/
• token-issues.md · troubleshooting/

SKILL.md (first lines)

# Zoom OAuth

Use this skill for concrete Zoom authentication implementation and troubleshooting. Prefer `setup-zoom-oauth` for the first-pass setup plan, then return here for exact flows, scope behavior, refresh handling, and error diagnosis.

## Workflow

1. Identify the app type and actor: user-level OAuth, account-level OAuth, server-to-server OAuth where officially supported, SDK JWT, or Build-platform credentials.
2. Create or validate the app with the Marketplace template selector and machine-readable index before implementing token flows; do not treat native S2S or Meeting SDK create requests as General App manifests.
3. Confirm the target API, SDK, or app surface, because scopes and token audiences differ by surface.
4. Choose the grant flow: authorization code with PKCE for public clients, authorization code for confidential web apps, device authorization where appropriate, or account credentials for supported account-level automation.
5. Store refresh tokens as single-use values: persist the replacement refresh token returned by each refresh response before reusing the old one.
6. Validate requests against redirect URI, account ID, scopes, app publication state, and token expiration before changing application code.
7. For local development, keep access tokens out of logs and treat refresh tokens as single-use when rotating credentials.

## References

- Full preserved guide: [references/full-guide.md](references/full-guide.md)
- Marketplace template selector: [../rest-api/references/marketplace-app-templates.md](../rest-api/references/marketplace-app-templates.md)
- Marketplace template index: [../rest-api/assets/marketplace-apps/marketplace-manifest-template-index.json](../rest-api/assets/marketplace-apps/marketplace-manifest-template-index.json)
- OAuth flows: [concepts/oauth-flows.md](concepts/oauth-flows.md)
- Token lifecycle: [concepts/token-lifecycle.md](concepts/token-lifecycle.md)
- Scope architecture: [concepts/scopes-architecture.md](concepts/scopes-architecture.md)
- Granular scopes: [references/granular-scopes.md](references/granular-scopes.md)
- OAuth errors: [references/oauth-errors.md](references/oauth-errors.md)
- Redirect URI issues: [troubleshooting/redirect-uri-issues.md](troubleshooting/redirect-uri-issues.md)

From zoom/zoom-plugin-codex, MIT.

More from zoom/zoom-plugin-codex