Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计提醒

build-zoom-rest-api-app构建 zoom rest API 应用

Agent Skill

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则;涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

总安装

6,605

周安装

278

GitHub Stars

11,715

下载量

2,313
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:build-zoom-rest-api-app(构建 zoom rest API 应用)
来源仓库:https://github.com/anthropics/knowledge-work-plugins
仓库路径:skills/build-zoom-rest-api-app
安装命令:
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill build-zoom-rest-api-app
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill build-zoom-rest-api-app

简介

用于辅助 API 设计、接口文档和请求响应结构梳理。

  • 适合生成 OpenAPI 草稿、检查字段命名和整理错误码。
  • 需确认真实业务语义、鉴权方式和分页规则。
  • 避免凭空补字段,最好从现有代码或样例中提取事实。
  • build-zoom-rest-api-app 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

/build-zoom-rest-api-app

Background reference for deterministic server-side Zoom automation and resource management. Prefer plan-zoom-product, plan-zoom-integration, or debug-zoom first, then route here for endpoint-level detail.

Zoom REST API

Expert guidance for building server-side integrations with the Zoom REST API. This API provides 600+ endpoints for managing meetings, users, webinars, recordings, reports, and all Zoom platform resources programmatically.

Official Documentation: https://developers.zoom.us/api-hub/ API Hub Reference: https://developers.zoom.us/api-hub/meetings/ OpenAPI Inventories: https://developers.zoom.us/api-hub/<domain>/methods/endpoints.json

Quick Links

New to Zoom REST API? Follow this path:

  1. API Architecture - Base URLs, regional URLs, me keyword, ID vs UUID, time formats
  2. Authentication Flows - OAuth setup (S2S, User, PKCE, Device Code)
  3. Meeting URLs vs Meeting SDK - Stop mixing join_url with Meeting SDK
  4. Meeting Lifecycle - Create → Update → Start → End → Delete with webhooks
  5. Rate Limiting Strategy - Plan tiers, per-user limits, retry patterns

Reference:

  • Meetings - Meeting CRUD, types, settings
  • Users - User provisioning and management
  • Recordings - Cloud recording access and download
  • AI Services - Scribe endpoint inventory and current AI Services path surface
  • GraphQL Queries - Alternative query API (beta)
  • Integrated Index - see the section below in this file

Most domain files under references/ are aligned to the official API Hub endpoints.json inventories. Treat those files as the local source of truth for method/path discovery.

Having issues?

Building event-driven integrations?

Quick Start

Get an Access Token (Server-to-Server OAuth)

curl -X POST "https://zoom.us/oauth/token" \
  -H "Authorization: Basic $(echo -n 'CLIENT_ID:CLIENT_SECRET' | base64)" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=account_credentials&account_id=ACCOUNT_ID"

Response:

{
  "access_token": "eyJhbGciOiJIUzI1NiJ9...",
  "token_type": "bearer",
  "expires_in": 3600,
  "scope": "meeting:read meeting:write user:read"
}

Create a Meeting

curl -X POST "https://api.zoom.us/v2/users/HOST_USER_ID/meetings" \
  -H "Authorization: Bearer ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "Team Standup",
    "type": 2,
    "start_time": "2025-03-15T10:00:00Z",
    "duration": 30,
    "settings": {
      "join_before_host": false,
      "waiting_room": true
    }
  }'

For S2S OAuth, use an explicit host user ID or email in the path. Do not use me.

List Users with Pagination

curl "https://api.zoom.us/v2/users?page_size=300&status=active" \
  -H "Authorization: Bearer ACCESS_TOKEN"

Base URL

https://api.zoom.us/v2

Regional Base URLs

The api_url field in OAuth token responses indicates the user's region. Use regional URLs for data residency compliance:

RegionURL
Global (default)https://api.zoom.us/v2
Australiahttps://api-au.zoom.us/v2
Canadahttps://api-ca.zoom.us/v2
European Unionhttps://api-eu.zoom.us/v2
Indiahttps://api-in.zoom.us/v2
Saudi Arabiahttps://api-sa.zoom.us/v2
Singaporehttps://api-sg.zoom.us/v2
United Kingdomhttps://api-uk.zoom.us/v2
United Stateshttps://api-us.zoom.us/v2

Note: You can always use the global URL https://api.zoom.us regardless of the api_url value.

Key Features

FeatureDescription
Meeting ManagementCreate, read, update, delete meetings with full scheduling control
User ProvisioningAutomated user lifecycle (create, update, deactivate, delete)
Webinar OperationsWebinar CRUD, registrant management, panelist control
Cloud RecordingsList, download, delete recordings with file-type filtering
Reports & AnalyticsUsage reports, participant data, daily statistics
Team ChatChannel management, messaging, chatbot integration
Zoom PhoneCall management, voicemail, call routing
Zoom RoomsRoom management, device control, scheduling
WebhooksReal-time event notifications for 100+ event types
WebSocketsPersistent event streaming without public endpoints
GraphQL (Beta)Single-endpoint flexible queries at v3/graphql
AI CompanionMeeting summaries, transcripts, AI-generated content
AI Services / ScribeFile and archive transcription via Build-platform JWT-authenticated endpoints

Prerequisites

  • Zoom account (Free tier has API access with lower rate limits)
  • App registered on Zoom App Marketplace
  • OAuth credentials (Server-to-Server OAuth or User OAuth)
  • Appropriate scopes for target endpoints
Need help with authentication? See the zoom-oauth skill for complete OAuth flow implementation.

Critical Gotchas and Best Practices

⚠️ JWT App Type is Deprecated

The JWT app type is deprecated. Migrate to Server-to-Server OAuth. This does NOT affect JWT token signatures used in Video SDK — only the Marketplace "JWT" app type for REST API access.

// OLD (JWT app type - DEPRECATED)
const token = jwt.sign({ iss: apiKey, exp: expiry }, apiSecret);

// NEW (Server-to-Server OAuth)
const token = await getServerToServerToken(accountId, clientId, clientSecret);

⚠️ The me Keyword Rules

  • User-level OAuth apps: MUST use me instead of userId (otherwise: invalid token error)
  • Server-to-Server OAuth apps: MUST NOT use me — provide the actual userId or email
  • Account-level OAuth apps: Can use either me or userId

⚠️ Meeting ID vs UUID — Double Encoding

UUIDs that begin with / or contain // must be double URL-encoded:

// UUID: /abc==
// Single encode: %2Fabc%3D%3D
// Double encode: %252Fabc%253D%253D  ← USE THIS

const uuid = '/abc==';
const encoded = encodeURIComponent(encodeURIComponent(uuid));
const url = `https://api.zoom.us/v2/meetings/${encoded}`;

⚠️ Time Formats

  • yyyy-MM-ddTHH:mm:ssZUTC time (note the Z suffix)
  • yyyy-MM-ddTHH:mm:ssLocal time (no Z, uses timezone field)
  • Some report APIs only accept UTC. Check the API reference for each endpoint.

⚠️ Rate Limits Are Per-Account, Not Per-App

All apps on the same Zoom account share rate limits. One heavy app can impact others. Monitor X-RateLimit-Remaining headers proactively.

⚠️ Per-User Daily Limits

Meeting/Webinar create/update operations are limited to 100 per day per user (resets at 00:00 UTC). Distribute operations across different host users when doing bulk operations.

⚠️ Download URLs Require Auth and Follow Redirects

Recording download_url values require Bearer token authentication and may redirect. Always follow redirects:

curl -L -H "Authorization: Bearer ACCESS_TOKEN" "https://zoom.us/rec/download/..."

Use Webhooks Instead of Polling

// DON'T: Poll every minute (wastes API quota)
setInterval(() => getMeetings(), 60000);

// DO: Receive webhook events in real-time
app.post('/webhook', (req, res) => {
  if (req.body.event === 'meeting.started') {
    handleMeetingStarted(req.body.payload);
  }
  res.status(200).send();
});
Webhook setup details: See the zoom-webhooks skill for comprehensive webhook implementation.

Complete Documentation Library

This skill includes comprehensive guides organized by category:

Core Concepts

Complete Examples

Troubleshooting

  • Common Errors - HTTP status codes, Zoom error codes, error response formats
  • Common Issues - Rate limits, token refresh, pagination pitfalls, gotchas

References (39 files covering all Zoom API domains)

Core APIs

Communication

Infrastructure

Advanced

Additional API Domains

Sample Repositories

Official (by Zoom)

Resources


Need help? Start with Integrated Index section below for complete navigation.


Integrated Index

*This section was migrated from SKILL.md.*

Quick Start Path

If you're new to the Zoom REST API, follow this order:

  1. Run preflight checks firstRUNBOOK.md
  2. Understand the API designconcepts/api-architecture.md

- Base URLs, regional endpoints, me keyword rules - Meeting ID vs UUID, double-encoding, time formats

  1. Set up authenticationconcepts/authentication-flows.md

- Server-to-Server OAuth (backend automation) - User OAuth with PKCE (user-facing apps) - Cross-reference: zoom-oauth

  1. Create your first meetingexamples/meeting-lifecycle.md

- Full CRUD with curl and Node.js examples - Webhook event integration

  1. Handle rate limitsconcepts/rate-limiting-strategy.md

- Plan-based limits, retry patterns, request queuing

  1. Set up webhooksexamples/webhook-server.md

- CRC validation, signature verification, event handling

  1. Troubleshoot issuestroubleshooting/common-issues.md

- Token refresh, pagination pitfalls, common gotchas


Documentation Structure

rest-api/
├── SKILL.md                              # Main skill overview + quick start
├── SKILL.md                              # This file - navigation guide
│
├── concepts/                             # Core architectural concepts
│   ├── api-architecture.md              # REST design, URLs, IDs, time formats
│   ├── authentication-flows.md          # OAuth flows (S2S, User, PKCE, Device)
│   └── rate-limiting-strategy.md        # Limits by plan, retry, queuing
│
├── examples/                             # Complete working code
│   ├── meeting-lifecycle.md             # Create→Update→Start→End→Delete
│   ├── user-management.md              # CRUD users, pagination, bulk ops
│   ├── recording-pipeline.md           # Download recordings via webhooks
│   ├── webhook-server.md               # Express.js CRC + signature verification
│   └── graphql-queries.md              # GraphQL queries, mutations, pagination
│
├── troubleshooting/                      # Problem solving
│   ├── common-errors.md                # HTTP codes, Zoom error codes table
│   └── common-issues.md               # Rate limits, tokens, pagination pitfalls
│
└── references/                           # 39 domain-specific reference files
    ├── authentication.md                # Auth methods reference
    ├── meetings.md                      # Meeting endpoints
    ├── users.md                         # User management endpoints
    ├── webinars.md                      # Webinar endpoints
    ├── recordings.md                    # Cloud recording endpoints
    ├── reports.md                       # Reports & analytics
    ├── accounts.md                      # Account management
    ├── rate-limits.md                   # Rate limit details
    ├── graphql.md                       # GraphQL API (beta)
    ├── zoom-team-chat.md                     # Team Chat messaging
    ├── chatbot.md                       # Chatbot integration
    ├── phone.md                         # Zoom Phone
    ├── rooms.md                         # Zoom Rooms
    ├── calendar.md                      # Zoom Calendar
    ├── mail.md                          # Zoom Mail
    ├── ai-companion.md                  # AI features
    ├── openapi.md                       # OpenAPI specs
    ├── qss.md                           # Quality of Service
    ├── contact-center.md                # Contact Center
    ├── events.md                        # Zoom Events
    ├── whiteboard.md                    # Whiteboard
    ├── clips.md                         # Zoom Clips
    ├── scheduler.md                     # Scheduler
    ├── scim2.md                         # SCIM 2.0
    ├── marketplace-apps.md              # App management
    ├── zoom-video-sdk-api.md                 # Video SDK REST
    └── ... (39 total files)

By Use Case

I want to create and manage meetings

  1. API Architecture - Base URL, time formats
  2. Meeting Lifecycle - Full CRUD + webhook events
  3. Meetings Reference - All endpoints, types, settings

I want to manage users programmatically

  1. User Management - CRUD, pagination, bulk ops
  2. Users Reference - Endpoints, user types, scopes

I want to download recordings automatically

  1. Recording Pipeline - Webhook-triggered downloads
  2. Recordings Reference - File types, download auth

I want to receive real-time events

  1. Webhook Server - CRC validation, signature check
  2. Cross-reference: zoom-webhooks for comprehensive webhook docs
  3. Cross-reference: zoom-websockets for WebSocket events

I want to use GraphQL instead of REST

  1. GraphQL Queries - Queries, mutations, pagination
  2. GraphQL Reference - Available entities, scopes, rate limits

I want to set up authentication

  1. Authentication Flows - All OAuth methods
  2. Cross-reference: zoom-oauth for full OAuth implementation

I'm hitting rate limits

  1. Rate Limiting Strategy - Limits by plan, strategies
  2. Rate Limits Reference - Detailed tables
  3. Common Issues - Practical solutions

I'm getting errors

  1. Common Errors - Error code tables
  2. Common Issues - Diagnostic workflow

I want to build webinars

  1. Webinars Reference - Endpoints, types, registrants
  2. Meeting Lifecycle - Similar patterns apply

I want to integrate Zoom Phone

  1. Phone Reference - Phone API endpoints
  2. Rate Limiting Strategy - Separate Phone rate limits

Most Critical Documents

1. API Architecture (FOUNDATION)

concepts/api-architecture.md

Essential knowledge before making any API call:

  • Base URLs and regional endpoints
  • The me keyword rules (different per app type!)
  • Meeting ID vs UUID double-encoding
  • ISO 8601 time formats (UTC vs local)
  • Download URL authentication

2. Rate Limiting Strategy (MOST COMMON PRODUCTION ISSUE)

concepts/rate-limiting-strategy.md

Rate limits are per-account, shared across all apps:

  • Free: 4/sec Light, 2/sec Medium, 1/sec Heavy
  • Pro: 30/sec Light, 20/sec Medium, 10/sec Heavy
  • Business+: 80/sec Light, 60/sec Medium, 40/sec Heavy
  • Per-user: 100 meeting create/update per day

3. Meeting Lifecycle (MOST COMMON TASK)

examples/meeting-lifecycle.md

Complete CRUD with webhook integration — the pattern most developers need first.


Key Learnings

Critical Discoveries:

  1. JWT app type is deprecated — use Server-to-Server OAuth

- The JWT *app type* on Marketplace is deprecated, NOT JWT token signatures - See: Authentication Flows

  1. me keyword behaves differently by app type

- User OAuth: MUST use me - S2S OAuth: MUST NOT use me - See: API Architecture

  1. Rate limiting is nuanced (don’t assume a single global rule)

- Limits can vary by endpoint and may be enforced at account/app/user levels - Treat quotas as potentially shared across your account and implement backoff - Monitor rate limit response headers (for example X-RateLimit-Remaining) - See: Rate Limiting Strategy

  1. 100 meeting creates per user per day

- This is a hard per-user limit, not related to rate limits - Distribute across host users for bulk operations - See: Rate Limiting Strategy

  1. UUID double-encoding is required for certain UUIDs

- UUIDs starting with / or containing // must be double-encoded - See: API Architecture

  1. Pagination: use next_page_token, not page_number

- page_number is legacy and being phased out - next_page_token is the recommended approach - See: Common Issues

  1. GraphQL is at /v3/graphql, not /v2/

- Single endpoint, cursor-based pagination - Rate limits apply per-field (each field = one REST equivalent) - See: GraphQL Queries


Quick Reference

"401 Unauthorized"

Authentication Flows - Token expired or wrong scopes

"429 Too Many Requests"

Rate Limiting Strategy - Check headers for reset time

"Invalid token" when using userId

API Architecture - User OAuth apps must use me

"How do I paginate results?"

Common Issues - Use next_page_token

"Webhooks not arriving"

Webhook Server - CRC validation required

"Recording download fails"

Recording Pipeline - Bearer auth + follow redirects

"How do I create a meeting?"

Meeting Lifecycle - Full working examples


Related Skills

SkillUse When
zoom-oauthImplementing OAuth flows, token management
zoom-webhooksDeep webhook implementation, event catalog
zoom-websocketsWebSocket event streaming
zoom-generalCross-product patterns, community repos

Based on Zoom REST API v2 (current) and GraphQL v3 (beta)

Environment Variables

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.1%
按下载量换算812

Claude

30.69%
按下载量换算710

Cursor

17.7%
按下载量换算409

Gemini CLI

8.72%
按下载量换算202

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills