zoom-websockets

Establish real-time Zoom event streams via WebSockets with OAuth authentication.

65|12|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/zoom/skills --skill zoom-websockets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoom-websockets
Source: https://github.com/zoom/skills/tree/main/websockets
Command: npx skills add https://github.com/zoom/skills --skill zoom-websockets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Zoom WebSockets provide a low-latency, persistent channel to receive real-time event notifications from Zoom, avoiding the overhead and delays of webhooks.

Core Features & Use Cases

  • Persistent WebSocket connection with authenticated subscription to Zoom events (e.g., meeting events, user events).
  • Token management with automatic refresh and single-connection guard per subscription.
  • Keep-alive heartbeats and robust reconnection with exponential backoff to ensure reliability.
  • Clear event payload formats and guidelines for building real-time dashboards and automations.

Quick Start

Configure a Server-to-Server OAuth app, create a WebSocket subscription, and connect using the sample client.

Frequently Asked Questions about zoom-websockets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I receive real-time Zoom events over WebSockets instead of using webhooks?

To receive real-time Zoom events over WebSockets, you establish a persistent, authenticated connection using Server-to-Server OAuth, subscribe to specific event endpoints, and maintain the channel with keep-alive pings.

How does Zoom WebSocket subscription handle token management and authentication?

Zoom WebSocket subscription handles authentication using Server-to-Server OAuth, automatically refreshing tokens to maintain a persistent connection without manual re-authentication interruptions.

What is the best way to manage WebSocket reconnection for Zoom real-time events?

The best way to manage WebSocket reconnection for Zoom events is using exponential backoff combined with keep-alive heartbeats, ensuring reliable recovery and single-connection enforcement per subscription.

Do I need a Server-to-Server OAuth app to subscribe to Zoom WebSocket events?

Yes, you need a Server-to-Server OAuth app to authenticate your WebSocket connection, create your event subscription, and securely stream real-time meeting and user updates from Zoom.

Why use Zoom WebSockets for real-time meeting updates instead of webhooks?

Use Zoom WebSockets for real-time meeting updates to achieve low-latency event delivery, avoiding the processing overhead and delays inherent in traditional webhook HTTP requests.

Can I enforce a single WebSocket connection per Zoom event subscription?

Yes, the connection implementation includes a single-connection guard per subscription, ensuring only one active WebSocket stream operates for each configured Zoom event subscription.