Build Zoom Video SDK App
AnthropicOfficialCreated by ZoomDistributed by Anthropic
- Skill
- Tool integration
- Software development
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Zoom Video SDK allows developers to build bespoke video applications with complete control over the user interface and branding. Unlike the standard Zoom Meeting SDK, this tool provides core video infrastructure for ad-hoc sessions that are created just-in-time. This skill provides the necessary architectural patterns, lifecycle management, and security practices for integrating the SDK into web and mobile applications.
What it does
- Provides a framework for building custom real-time video interfaces.
- Explains the session lifecycle, including client initialization, joining, and media stream handling.
- Details the server-side JWT signature generation required for secure authentication.
- Outlines event-driven patterns for rendering participant video and audio.
- Covers Bring Your Own Storage (BYOS) configurations for direct cloud recording.
- Offers troubleshooting guidance and platform-specific integration references.
When to use it
- When you need full control over the video UI rather than using the default Zoom interface.
- When building custom video-session products like virtual event platforms or telehealth apps.
- When you require ad-hoc video sessions that do not rely on pre-scheduled Zoom meetings.
- When you need to integrate video capabilities directly into your own application's branding.
Advantages
- Complete UI and branding flexibility.
- Ad-hoc session creation without pre-scheduling.
- Direct cloud recording storage to your own S3 bucket.
- Granular control over participant roles and session management via JWT.
Usage examples
- “How do I start a video session using the Zoom Video SDK?”
- The agent provides the strict lifecycle order: create client, initialize, join with a topic and signature, then access the media stream to start audio and video.
- “How do I handle participant video rendering in my custom app?”
- The agent explains the event-driven approach, specifically using 'peer-video-state-change' events to trigger 'attachVideo' for rendering.
- “How do I secure my Video SDK implementation?”
- The agent provides a Node.js example for generating short-lived JWT signatures server-side to protect the SDK Secret.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/anthropics/build-zoom-video-sdk-app/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip build-zoom-video-sdk-app.zip -d .agents/skills
Documentation by Zoom
/build-zoom-video-sdk-app
Background reference for fully custom video-session products. Prefer plan-zoom-product first when the boundary between Meeting SDK and Video SDK is still unclear.
Build custom video experiences powered by Zoom's infrastructure.
Hard Routing Guardrail (Read First)
If the user asks for custom real-time video app behavior (topic/session join, custom rendering, attach/detach), route to Video SDK.
Do not switch to REST meeting endpoints for Video SDK join flows.
Video SDK does not use Meeting IDs,
join_url, or Meeting SDK join payload fields (meetingNumber,passWord).
Meeting SDK vs Video SDK
| Feature | Meeting SDK | Video SDK |
|---|---|---|
| UI | Default Zoom UI or Custom UI | Fully custom UI (you build it) |
| Experience | Zoom meetings | Video sessions |
| Branding | Limited customization | Full branding control |
| Features | Full Zoom features | Core video features |
UI Options (Web)
Video SDK gives you full control over the UI:
| Option | Description |
|---|---|
| UI Toolkit | Pre-built React components (low-code) |
| Custom UI | Build your own UI using the SDK APIs |
Prerequisites
Zoom Video SDK credentials from Marketplace
SDK Key and Secret
Web development environment
Need help with OAuth or signatures? See the zoom-oauth skill for authentication flows.
Need pre-join diagnostics on web? Use probe-sdk before Video SDK
join()to reduce first-minute failures.
Start troubleshooting fast: Use the 5-Minute Runbook before deep debugging.
Quick Start (Web)
NPM Usage (Bundler like Vite/Webpack)
import ZoomVideo from '@zoom/videosdk';
const client = ZoomVideo.createClient();
await client.init('en-US', 'Global', { patchJsMedia: true });
await client.join(topic, signature, userName, password);
// IMPORTANT: getMediaStream() ONLY works AFTER join()
const stream = client.getMediaStream();
await stream.startVideo();
await stream.startAudio();CDN Usage (No Bundler)
WARNING: Ad blockers block
source.zoom.us. Self-host the SDK to avoid issues.
# Download SDK locally
curl "https://source.zoom.us/videosdk/zoom-video-1.12.0.min.js" -o js/zoom-video-sdk.min.js<script src="js/zoom-video-sdk.min.js"></script>// CDN exports as WebVideoSDK, NOT ZoomVideo
// Must use .default property
const ZoomVideo = WebVideoSDK.default;
const client = ZoomVideo.createClient();
await client.init('en-US', 'Global', { patchJsMedia: true });
await client.join(topic, signature, userName, password);
// IMPORTANT: getMediaStream() ONLY works AFTER join()
const stream = client.getMediaStream();
await stream.startVideo();
await stream.startAudio();ES Module with CDN (Race Condition Fix)
When using <script type="module"> with CDN, SDK may not be loaded yet:
// Wait for SDK to load before using
function waitForSDK(timeout = 10000) {
return new Promise((resolve, reject) => {
if (typeof WebVideoSDK !== 'undefined') {
resolve();
return;
}
const start = Date.now();
const check = setInterval(() => {
if (typeof WebVideoSDK !== 'undefined') {
clearInterval(check);
resolve();
} else if (Date.now() - start > timeout) {
clearInterval(check);
reject(new Error('SDK failed to load'));
}
}, 100);
});
}
// Usage
await waitForSDK();
const ZoomVideo = WebVideoSDK.default;
const client = ZoomVideo.createClient();SDK Lifecycle (CRITICAL ORDER)
The SDK has a strict lifecycle. Violating it causes silent failures.
1. Create client: client = ZoomVideo.createClient()
2. Initialize: await client.init('en-US', 'Global', options)
3. Join session: await client.join(topic, signature, userName, password)
4. Get stream: stream = client.getMediaStream() ← ONLY AFTER JOIN
5. Start media: await stream.startVideo() / await stream.startAudio()Common Mistake (Silent Failure):
// ❌ WRONG: Getting stream before joining
const client = ZoomVideo.createClient();
await client.init('en-US', 'Global');
const stream = client.getMediaStream(); // Returns undefined!
await client.join(...);
// ✅ CORRECT: Get stream after joining
const client = ZoomVideo.createClient();
await client.init('en-US', 'Global');
await client.join(...);
const stream = client.getMediaStream(); // Works!Video Rendering (Event-Driven)
The SDK is event-driven. You must listen for events and render videos accordingly.
Use attachVideo() NOT renderVideo()
import { VideoQuality } from '@zoom/videosdk';
// Start your camera
await stream.startVideo();
// Attach video - returns element to append to DOM
const element = await stream.attachVideo(userId, VideoQuality.Video_360P);
container.appendChild(element);
// Detach when done
await stream.detachVideo(userId);Required Events
// When other participant's video turns on/off
client.on('peer-video-state-change', async (payload) => {
const { action, userId } = payload;
if (action === 'Start') {
const el = await stream.attachVideo(userId, VideoQuality.Video_360P);
container.appendChild(el);
} else {
await stream.detachVideo(userId);
}
});
// When participants join/leave
client.on('user-added', (payload) => { /* check bVideoOn */ });
client.on('user-removed', (payload) => { stream.detachVideo(payload.userId); });See web/references/web.md for complete event handling patterns.
Key Concepts
| Concept | Description |
|---|---|
| Session | Video session (not a meeting) |
| Topic | Session identifier (any string you choose) |
| Signature | JWT for authorization |
| MediaStream | Audio/video stream control |
Session Creation Model
Important: Video SDK sessions are created just-in-time, not in advance.
| Aspect | Video SDK | Meeting SDK |
|---|---|---|
| Pre-creation | NOT required | Create meeting via API first |
| Session start | First participant joins with topic | Join existing meeting ID |
| Topic | Any string (you define it) | Meeting ID from API |
| Scheduling | N/A - sessions are ad-hoc | Meetings can be scheduled |
How Sessions Work
No pre-creation needed: Sessions don't exist until someone joins
Topic = Session ID: Any participants joining with the same
topicstring join the same sessionFirst join creates it: The session is created when the first participant joins
No meeting ID: There's no numeric meeting ID like in Zoom Meetings
// Session is created on-the-fly when first user joins
// Any string can be the topic - it becomes the session identifier
await client.join('my-custom-session-123', signature, 'User Name');
// Other participants join the SAME session by using the SAME topic
await client.join('my-custom-session-123', signature, 'Another User');Signature Endpoint Setup
The signature endpoint must be accessible from your frontend without CORS issues.
Option 1: Same-Origin Proxy (Recommended)
# Nginx config
location /api/ {
proxy_pass http://YOUR_BACKEND_HOST:3005/api/;
proxy_http_version 1.1;
proxy_set_header Host $host;
}// Frontend uses relative URL (same origin)
const response = await fetch('/api/signature', { ... });Option 2: CORS Configuration
// Express.js backend
const cors = require('cors');
app.use(cors({
origin: ['https://your-domain.com'],
credentials: true
}));WARNING: Mixed content (HTTPS page → HTTP API) will be blocked by browsers.
Use Cases
| Use Case | Description |
|---|---|
| Video SDK BYOS (Bring Your Own Storage) | Save recordings directly to your S3 bucket |
BYOS (Bring Your Own Storage)
Video SDK feature - Zoom saves cloud recordings directly to your Amazon S3 bucket. No downloading required.
Official docs: https://developers.zoom.us/docs/build/storage/
Prerequisites:
Video SDK account with Cloud Recording add-on (Universal Credit includes this)
AWS S3 bucket
Authentication options:
AWS Access Key - simpler setup
Cross Account Access - more secure (IAM role assumption)
S3 path structure:
Buckets/{bucketName}/cmr/byos/{YYYY}/{MM}/{DD}/{GUID}/cmr_byos/Key benefits:
Zero download bandwidth costs
Direct storage during recording
Config-only setup (no webhook/download code needed)
Setup location: Developer Portal → Account Settings → General → Communications Content Storage Location
See ../general/use-cases/video-sdk-bring-your-own-storage.md for complete setup guide.
Detailed References
UI & Components
references/ui-toolkit.md - Pre-built UI components (Web)
references/triage-intake.md - What to ask first (turn vague reports into answers)
references/session-lifecycle.md - Correct API ordering + event-driven rendering
references/licensing-and-entitlements.md - License/admin prerequisites
references/token-contract-test-spec.md - Shared backend token contract and cross-platform smoke test
Platform Guides
references/authorization.md - Video SDK JWT generation
web/SKILL.md - Web Video SDK (JavaScript/TypeScript)
web/SKILL.md - Complete documentation navigation
web/examples/react-hooks.md - Official React hooks library
web/examples/framework-integrations.md - Next.js, Vue/Nuxt patterns
react-native/SKILL.md - React Native Video SDK (mobile wrapper, helper/event architecture)
react-native/SKILL.md - React Native documentation navigation
react-native/examples/session-join-pattern.md - Tokenized session join flow
flutter/SKILL.md - Flutter Video SDK (mobile wrapper, event-driven architecture)
flutter/SKILL.md - Flutter documentation navigation
flutter/examples/session-join-pattern.md - Tokenized session join flow
android/SKILL.md - Android Video SDK (native mobile custom UI, tokenized sessions)
ios/SKILL.md - iOS Video SDK (native mobile custom UI, delegate-driven lifecycle)
macos/SKILL.md - macOS Video SDK (desktop native apps, custom session windows)
unity/SKILL.md - Unity Video SDK wrapper (game-engine integration, scene-driven UX)
linux/SKILL.md - Linux Video SDK overview (C++ headless bots)
linux/linux.md - Linux C++ SDK (headless bots, raw media capture/injection)
linux/references/linux-reference.md - Linux API Reference
windows/SKILL.md - Windows C++ SDK (desktop applications, raw media capture/injection)
windows/references/windows-reference.md - Windows API Reference
references/troubleshooting.md - Common issues and solutions
references/forum-top-questions.md - Common forum question patterns (what to cover)
Sample Repositories
Official (by Zoom)
| Type | Repository | Stars |
|---|---|---|
| Web | videosdk-web-sample | 137 |
| Web NPM | videosdk-web | 56 |
| Auth | videosdk-auth-endpoint-sample | 23 |
| UI Toolkit Web | videosdk-zoom-ui-toolkit-web | 17 |
| UI Toolkit React | videosdk-zoom-ui-toolkit-react-sample | 17 |
| Next.js | videosdk-nextjs-quickstart | 16 |
| Telehealth | VideoSDK-Web-Telehealth | 11 |
| Linux | videosdk-linux-raw-recording-sample | - |
Full list: See general/references/community-repos.md
Resources
Official docs: https://developers.zoom.us/docs/video-sdk/
Developer forum: https://devforum.zoom.us/
Environment Variables
See references/environment-variables.md for standardized
.envkeys and where to find each value.
Linux Operations
linux/RUNBOOK.md - Linux platform preflight and debugging checklist.
Files
- ATTRIBUTION.mdAdded by AutoGineer989 B
- LICENSELicence file added by AutoGineer1.1 KiB
- RUNBOOK.md2.4 KiB
- SKILL.md13.6 KiB
- references/authorization.md3.9 KiB
- references/environment-variables.md1.3 KiB
- references/forum-top-questions.md1.9 KiB
- references/licensing-and-entitlements.md760 B
- references/session-lifecycle.md959 B
- references/token-contract-test-spec.md1.6 KiB
- references/triage-intake.md1.2 KiB
- references/troubleshooting.md1.8 KiB
- references/ui-toolkit.md5.6 KiB
references/authorization.md
Video SDK - Authorization
Generate JWT signatures for Video SDK authentication.
Overview
Video SDK uses JWT (JSON Web Token) signatures to authenticate users joining video sessions. Signatures must be generated server-side to protect your SDK Secret.
Important: Unlike Zoom Meetings, Video SDK sessions are NOT pre-created. The tpc (topic) in your JWT can be any string you choose - the session is created when the first participant joins with that topic.
Prerequisites
Video SDK Key and Secret from Marketplace (sign-in required)
Server-side code to generate signatures
JWT Structure
| Claim | Description |
|---|---|
app_key | Your SDK Key |
tpc | Topic (session name) - any string you choose |
role_type | 0 = participant, 1 = host |
user_identity | (Optional) Unique user identifier |
iat | Issued at timestamp |
exp | Expiration timestamp |
Note on tpc (Topic):
Can be any string (e.g.,
"room-123","consultation-abc","game-lobby-5")All users joining with the same
tpcvalue join the same sessionSession is created automatically when first user joins
No API call needed to create the session beforehand
Host and Co-Host via roleType
In Video SDK, host/co-host status is determined entirely by role_type in the JWT — not by runtime API calls.
| role_type | First to Join | Subsequent Joiners |
|---|---|---|
| 1 | Host | Co-host |
| 0 | Participant | Participant |
Only host or co-host can call
client.leave(true)to end session for allA participant calling
leave(true)only leaves themselvesNo need for
makeHost()ormakeManager()API calls — use JWT roleType instead
Session Creation Pattern (Bot as Host)
For scenarios where you need a bot to create and manage the session:
Bot joins with
role_type: 1→ becomes host (creates session)User A joins with
role_type: 1→ becomes co-hostBot leaves → User A remains as co-host, can end session
User B joins with
role_type: 0→ participant
This pattern avoids race conditions from runtime host assignment.
// JWT generation examples
generateJWT(key, secret, sessionName, 1, 'SessionBot'); // Bot: host
generateJWT(key, secret, sessionName, 1, 'Advisor'); // Advisor: co-host
generateJWT(key, secret, sessionName, 0, 'Customer'); // Customer: participantSignature Generation Best Practices
Short-Lived Tokens (Recommended)
For security, generate tokens with short expiry:
const iat = Math.floor(Date.now() / 1000) - 7200; // 2 hours in the past
const exp = Math.floor(Date.now() / 1000) + 10; // 10 seconds from now
const payload = {
app_key: SDK_KEY,
tpc: topic,
role_type: role,
user_identity: userIdentity,
iat: iat,
exp: exp
};Why this works:
expis only 10 seconds after generation (short-lived for security)iatis set 2 hours in the past to satisfy Zoom's requirement thatexp - iat >= 2 hoursToken is generated just before joining, so 10 second window is sufficient
Server-Side Example (Node.js)
const jwt = require('jsonwebtoken');
function generateSignature(sdkKey, sdkSecret, topic, role, userIdentity) {
const iat = Math.floor(Date.now() / 1000) - 7200; // 2 hours ago
const exp = Math.floor(Date.now() / 1000) + 10; // 10 seconds from now
const payload = {
app_key: sdkKey,
tpc: topic,
role_type: role,
user_identity: userIdentity || '',
iat: iat,
exp: exp
};
return jwt.sign(payload, sdkSecret, { algorithm: 'HS256' });
}Security Guidelines
| Do | Don't |
|---|---|
| Generate signatures server-side | Expose SDK Secret in client code |
| Use short expiry times | Use long-lived tokens |
| Validate user before generating | Generate for unauthenticated users |
Resources
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs network access
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Zoom
- Publisher
- Anthropic (Official)
- Distributed by
- Anthropic
- Source
- anthropics/knowledge-work-plugins · partner-built/zoom-plugin/skills/video-sdk · commit e050c2e
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from partner-built/zoom-plugin/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Zoom or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download build-zoom-video-sdk-app.zip