Zoom SDKs & Libraries: Integration Guides (2026)

SDKs overview

Zoom offers a suite of Software Development Kits (SDKs) designed to allow developers to integrate Zoom's core functionalities directly into their applications. These SDKs provide programmatic access to video, audio, chat, and meeting management capabilities, enabling custom user experiences without requiring users to navigate to the standalone Zoom client. The official SDKs are categorized to address different integration needs, ranging from embedding full meeting experiences to custom video applications.

The primary SDK offerings from Zoom include the Zoom Web SDK, which facilitates browser-based integrations; the Client SDKs for native desktop and mobile applications (Windows, macOS, iOS, Android); and the Video SDK, focused on custom video-first applications. Additionally, the Meeting SDK is available for embedding the standard Zoom meeting interface into custom applications. Each SDK provides distinct features and use cases, allowing developers to select the appropriate toolset for their project requirements.

Official SDKs by language

Zoom maintains several official SDKs, each tailored for specific platforms and programming languages. These SDKs are regularly updated to reflect new features and security enhancements. The table below outlines the main official SDKs, their primary programming languages, common package managers for installation, and their general maturity status as of 2026.

Installation

Installation methods vary depending on the chosen SDK and target platform. Below are common installation approaches for the Web SDK and Client SDKs.

Web SDK (JavaScript)

The Zoom Web SDK can be installed via npm or included directly via a Content Delivery Network (CDN).

npm installation:

npm install @zoomus/websdk

After installation, you can import modules into your JavaScript project:

import ZoomMtg from '@zoomus/websdk/ZoomMtg';

ZoomMtg.preLoadWasm();
ZoomMtg.prepareJssdk();
// Initialize and join meeting

CDN inclusion:

For simpler web projects, the SDK can be loaded directly from a CDN:

<script src="https://source.zoom.us/zoom-sdk-videosdk/5.17.0/lib/index.min.js"></script>
<script>
  ZoomMtg.preLoadWasm();
  ZoomMtg.prepareJssdk();
  // Your application logic here
</script>

Developers should refer to the Zoom Web SDK getting started guide for the latest version and detailed configuration.

Client SDKs (iOS/Android/Windows/macOS)

Client SDKs for native applications are typically integrated using platform-specific package managers or by downloading the SDK package directly from the Zoom developer portal.

iOS (Objective-C/Swift) via CocoaPods:

Add the following to your Podfile:

target 'YourApp' do
  use_frameworks!
  pod 'ZoomVideoSDK'
  # For Meeting SDK: pod 'ZoomSDK'
end

Then run:

pod install

Refer to the Zoom iOS Video SDK documentation for comprehensive setup instructions.

Android (Java/Kotlin) via Gradle:

Add the following to your app's build.gradle file:

dependencies {
    implementation 'us.zoom.videosdk:videosdk:latest.release'
    // For Meeting SDK: implementation 'us.zoom.sdk:mobilertc:latest.release'
}

Sync your Gradle project. Detailed steps are available in the Zoom Android Video SDK getting started guide.

Windows (C++/C#) via NuGet or SDK download:

For C# applications, you can install the SDK via NuGet:

Install-Package ZoomDotNetSDK

Alternatively, download the Windows Client SDK package directly and integrate the provided libraries and headers into your C++ or C# project.

Similar processes apply to macOS, typically involving CocoaPods or direct SDK downloads. Always consult the official Zoom Client SDK documentation for the most current and platform-specific instructions.

Quickstart example

This quickstart example demonstrates how to initialize the Zoom Web SDK and join a meeting. This requires a JWT token generated on your backend, as described in the Zoom Web SDK authentication guide.

// index.js (Frontend JavaScript)
import ZoomMtg from '@zoomus/websdk/ZoomMtg';

// Replace with your generated JWT signature, API key, and meeting details
const signature = 'YOUR_JWT_SIGNATURE'; // Generated from your backend
const apiKey = 'YOUR_SDK_KEY';
const meetingNumber = '1234567890';
const role = 0; // 0 for attendee, 1 for host
const userName = 'Developer User';
const userEmail = '[email protected]';
const passWord = 'MEETING_PASSWORD'; // Optional

ZoomMtg.preLoadWasm();
ZoomMtg.prepareJssdk();

const joinMeeting = () => {
  ZoomMtg.init({
    leaveUrl: 'http://localhost:3000/leave',
    success: function () {
      ZoomMtg.join({
        signature: signature,
        meetingNumber: meetingNumber,
        userName: userName,
        apiKey: apiKey,
        userEmail: userEmail,
        passWord: passWord,
        success: function(res) {
          console.log('join meeting success');
          console.log(res);
        },
        error: function(res) {
          console.log(res);
        }
      });
    },
    error: function(res) {
      console.log(res);
    }
  });
};

// Call joinMeeting when a button is clicked or page loads
// For example, on a button click:
document.getElementById('join-meeting-button').addEventListener('click', joinMeeting);

This example sets up the basic framework for a web-based Zoom meeting. Server-side generation of the JWT signature is critical for security, ensuring that sensitive credentials are not exposed client-side. For more in-depth examples and advanced features like custom UI, refer to the Zoom Web SDK sample application.

Community libraries

While Zoom provides official SDKs for core functionalities, the developer community has also contributed various libraries and wrappers that extend or simplify interactions with the Zoom API and SDKs in specific contexts. These community-driven projects can offer solutions for languages not officially supported by a specific SDK or provide higher-level abstractions for common use cases.

Examples of community contributions often include:

• Python Wrappers: Libraries that simplify making Zoom API calls from Python applications, abstracting away the HTTP request and response parsing. These are often found on package indexes like PyPI.
• Ruby Gems: Similar to Python, Ruby developers create gems to interact with the Zoom API, often focusing on webhook handling or meeting scheduling.
• Framework-specific integrations: Libraries designed to integrate Zoom features seamlessly into popular web frameworks like React, Vue, or Angular, providing components or hooks for easier development.
• Unofficial API clients: While not part of the official SDKs, some community projects offer client libraries for the Zoom API in languages like Go or PHP, which might not have official SDK support for all API endpoints.

When considering community libraries, it is important to evaluate their maintenance status, community support, and adherence to security best practices. Developers should check the project's repository (e.g., GitHub) for recent updates, open issues, and contributor activity. For example, a search on GitHub for "Zoom API Python" or "Zoom SDK React" can reveal various community-maintained projects. Always prioritize official SDKs and API documentation for critical production applications, and use community libraries with due diligence, especially concerning authentication and data handling, as outlined in general API security guidelines like those from Cloudflare's API security best practices.