setup-zoom-websockets

Implement Zoom WebSocket connections with S2S OAuth and automatic reconnection.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This reference provides a structured guide for implementing Zoom WebSockets, enabling real-time event delivery with secure authentication and robust connection management, instead of relying on ad-hoc polling.

Core Features & Use Cases

  • S2S OAuth-based access and token management for WebSocket sessions
  • WebSocket connection lifecycle handling, keep-alive pings, and reconnection strategies
  • Event parsing, filtering, and safe error handling with clear debugging guidance
  • Troubleshooting and best practices for production-grade deployments

Quick Start

Create a Server-to-Server OAuth app, enable WebSocket subscriptions in the Zoom Marketplace, and connect to the provided WebSocket URL using a valid access token.

Frequently Asked Questions about setup-zoom-websockets

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

FAQPage Schema
How do I get real-time Zoom events using WebSockets instead of polling?

To receive real-time Zoom events via WebSockets, you create a Server-to-Server OAuth app, enable WebSocket subscriptions in the Zoom Marketplace, and connect to the provided WebSocket URL using a valid access token.

How does authentication work for Zoom WebSocket connections?

Zoom WebSocket authentication uses Server-to-Server (S2S) OAuth token retrieval. You must generate a valid access token through your S2S OAuth app and use it when constructing your WebSocket URL for secure session authorization.

What is the best way to handle Zoom WebSocket reconnection and keep-alive?

For robust Zoom WebSocket connection management, implement heartbeat keep-alive pings and automatic reconnection with backoff. This ensures continuous event delivery and reliable recovery during temporary network disruptions.

How do I parse and filter event formats from Zoom WebSocket subscriptions?

Zoom WebSocket event parsing involves filtering incoming event payloads and applying safe error handling. The reference guide provides structured formats and debugging guidance to accurately process real-time subscription data.

Do I need a Server-to-Server OAuth app to enable Zoom WebSocket subscriptions?

Yes, a Server-to-Server OAuth app is required. You must create this app in the Zoom Marketplace, enable WebSocket subscriptions, and retrieve S2S OAuth tokens to authenticate your real-time event delivery sessions.

Why does my Zoom WebSocket connection drop and how can I troubleshoot it?

Zoom WebSocket connections drop due to missed heartbeat pings or network failures. Troubleshoot by verifying keep-alive pings, checking token validity, and implementing automatic reconnection with backoff for production-grade deployments.