C✳CODEZ.WIN
🌐 English

Localized reading guide

zoom-oauthPurpose, usage and source

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.

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
partner-built/zoom-plugin/skills/oauth/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Development
Last collected

License: License file needs review

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

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.

How the upstream workflow works

Quick Start Path

If you're new to Zoom OAuth, follow this order: Run preflight checks first → RUNBOOK.md Choose your OAuth flow → concepts/oauth-flows.md 4 flows: S2S (backend), User (SaaS), Device (no browser), Chatbot

Upstream passage · L630 ↗

Step 1: Redirect User to Authorize

Use https://zoom.us/oauth/authorize for consent, but https://zoom.us/oauth/token for token exchange.

Upstream passage · L147 ↗

Step 2: User Authorizes

User signs in and grants permission Redirects to redirect_uri with authorization code:

Upstream passage · L163 ↗
Upstream passage · bash ↗
POST https://zoom.us/oauth/token?grant_type=account_credentials&account_id={ACCOUNT_ID}

Headers:
Authorization: Basic {Base64(ClientID:ClientSecret)}

Requirements and setup

Prerequisites

Zoom app created in Marketplace Client ID and Client Secret

Upstream passage · L42 ↗

Prerequisites

Enable "Use App on Device" in: Features > Embed > Enable Meeting SDK

Upstream passage · L222 ↗

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
126c291d7d80aceaf694968fc66d0f0552c04bfe99a8121b16de3955521656f9
Back to the full Skill catalog