Generated banner for Zoom Apps SDK
Generated logo for Zoom Apps SDK

Zoom Apps SDK

OpenAIOfficialCreated by ZoomDistributed by OpenAI

  • Skill
  • Tool integration
  • Software development
  • MIT
  • Medium risk

From the author

Use when using Apps SDK.
— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Zoom Apps SDK skill provides a structured approach for developers building applications that run directly inside the Zoom client. It covers the lifecycle of a Zoom App, from initial configuration and context verification to implementing advanced features like the Layers API, in-client OAuth, and inter-instance communication. The skill emphasizes the importance of identifying the correct running context—such as meetings, webinars, or the main client—to ensure features are gated appropriately and the user experience remains consistent across different Zoom environments.

What it does

  • Initializes the Zoom Apps SDK with required capabilities.
  • Identifies the current running context, such as meeting or main client.
  • Facilitates in-client OAuth flows for secure user authentication.
  • Enables communication between different app instances.
  • Provides access to meeting-specific data and participant information.
  • Supports advanced UI and media features like virtual backgrounds and notification management.

When to use it

  • When building an application intended to run inside the Zoom client interface.
  • When you need to access meeting context, participant lists, or recording status.
  • When implementing custom UI overlays or media controls within a Zoom meeting.
  • When you need to authenticate users without redirecting them to an external browser.

Advantages

  • Provides a unified API for interacting with various Zoom client contexts.
  • Supports secure, in-client authentication workflows.
  • Enables deep integration with Zoom meeting features and participant data.
  • Offers clear patterns for handling cross-instance communication.

Usage examples

“How do I initialize the Zoom Apps SDK?”
You must call zoomSdk.config() first, passing in the required capabilities and version to initialize the SDK and declare the features your app intends to use.
“How can I get the current meeting ID?”
After initializing the SDK, you can call zoomSdk.getMeetingContext() to retrieve the meetingID, meetingTopic, and meetingStatus.
“How do I trigger authentication within the Zoom client?”
Use the zoomSdk.authorize() method to trigger the in-client OAuth flow, which avoids external browser redirects and fires an onAuthorized event upon completion.
“How do I send a message to another instance of my app?”
First call zoomSdk.connect() to establish the connection, then use zoomSdk.postMessage() to send a payload to other app instances.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/openai/zoom-apps-sdk/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip zoom-apps-sdk.zip -d .agents/skills

Documentation by Zoom

Zoom Apps SDK

Use this skill when the app runs inside the Zoom client. If the user only needs to embed a meeting in an external app, route to Meeting SDK instead.

Workflow

  1. Confirm the running context: meeting, webinar, main client, phone, collaborate mode, immersive mode, camera mode, or Layers API.

  2. Configure Marketplace app settings, allowed domains, redirect URIs, and in-client OAuth before implementing SDK calls.

  3. Initialize zoomSdk and gate features by capability and running context.

  4. Design client communication and data flow: frontend SDK calls, backend REST calls, in-client OAuth tokens, and webhook handoff.

  5. Implement advanced client features only after the base app loads reliably: Layers API, breakout rooms, guest mode, collaborate mode, or ZMail.

  6. Debug blank panels, domain allowlist issues, CSP, missing capabilities, running-context mismatch, and OAuth redirect problems independently.

References

Files

troubleshooting/migration.md

SDK Version Migration

Notes on upgrading @zoom/appssdk versions and handling deprecations.

Current Version

Recommended: @zoom/appssdk v0.16.26+ (latest stable)

{
  "dependencies": {
    "@zoom/appssdk": "^0.16.26"
  }
}

Version Pinning Strategy

Strategypackage.jsonRiskUse When
Exact"0.16.26"LowestProduction apps, critical stability
Patch"~0.16.26"LowMost apps
Minor"^0.16.26"MediumActive development

Checking API Availability at Runtime

Not all APIs are available in all Zoom client versions. Always check:

const { supportedApis } = await zoomSdk.getSupportedJsApis();

// Check before using an API
if (supportedApis.includes('authorize')) {
  // Safe to use In-Client OAuth
  await zoomSdk.authorize({...});
} else {
  // Fall back to web redirect OAuth
  window.location.href = '/install';
}

Also check unsupportedApis after config():

const config = await zoomSdk.config({
  capabilities: ['authorize', 'getMeetingContext', 'newFeature'],
  version: '0.16'
});

if (config.unsupportedApis.includes('newFeature')) {
  console.log('newFeature not available in this client version');
  // Graceful degradation
}

Config Version Parameter

The version parameter in config() indicates which SDK API version you expect:

await zoomSdk.config({
  capabilities: [...],
  version: '0.16'  // API version, not NPM package version
});

This helps Zoom maintain backward compatibility. Use the latest supported version.

Sample App SDK Versions

Status of official sample repositories:

RepositorySDK VersionStatusNotes
zoomapps-sample-js^0.16.26CurrentBest reference
zoomapps-advancedsample-react0.16.0OutdatedWorks but update recommended
zoomapps-customlayout-js^0.16.8OutdatedLayers API may differ
zoomapps-texteditor-vuejs^0.16.7OutdatedY.js pattern still valid
zoomapps-serverless-vuejs^0.16.21Slightly outdatedFirebase pattern still valid

Deprecation Pattern

Zoom typically deprecates APIs gradually:

  1. API marked deprecated in docs

  2. unsupportedApis starts returning it in newer clients

  3. API stops working in future client versions

Best practice: Check getSupportedJsApis() at startup and implement fallbacks.

Migration Checklist

When upgrading SDK version:

  • [ ] Update @zoom/appssdk in package.json

  • [ ] Run npm install

  • [ ] Check changelog for breaking changes

  • [ ] Test all capabilities in Zoom client

  • [ ] Verify getSupportedJsApis() includes your APIs

  • [ ] Test in both meeting and main client contexts

  • [ ] Test browser preview fallback still works

  • [ ] Update version parameter in config() if needed

Resources

Requirements and compatibility

Written for: OpenAI Codex

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.

Security

What our scanner noticed· Medium risk

  • Possible data-exfiltration endpoints

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
OpenAI (Official)
Distributed by
OpenAI
Source
openai/plugins · plugins/zoom/skills/zoom-apps-sdk · commit d420d13
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from plugins/zoom/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or OpenAI.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download zoom-apps-sdk.zip