Zoom Meeting SDK (Windows)

Embed Zoom meeting capabilities into Windows desktop applications for native C++ integrations and headless bots.

New to Zoom SDK? Start Here!

The fastest way to master the SDK:

1. SDK Architecture Pattern - Learn the universal pattern that works for ALL 35+ features
2. Authentication Pattern - Get a working bot joining meetings
3. Windows Message Loop - Fix the #1 reason callbacks don't fire

Building a Custom UI?

• Custom UI Architecture - How SDK rendering actually works (child HWNDs, D3D, etc.)
• Custom UI Video Rendering Example - Complete working code
• SDK-Rendered vs Self-Rendered - Choose the right approach
• Custom UI Interface Methods - All 13 required virtual methods

Having issues?

• Build errors → Build Errors Guide
• Callbacks not firing → Windows Message Loop
• Quick diagnostics → Common Issues
• Performance / service quality → service-quality.md
• Deployment notes → deployment.md
• MSBuild from git bash → Build Errors Guide
• Complete navigation → SKILL.md

Prerequisites

• Zoom app with Meeting SDK credentials (Client ID & Secret)
• Visual Studio 2019/2022 or later
• Windows 10 or later
• C++ development environment
• vcpkg for dependency management

Need help with authentication? See the zoom-oauth skill for JWT token generation.

Project Preferences & Learnings

IMPORTANT: These are hard-won preferences from real project experience. Follow these when creating new projects.

Do NOT use CMake — Use native Visual Studio .vcxproj

Always create a native Visual Studio .sln + .vcxproj project, not a CMake project. Reasons:

• More standard and familiar for Windows C++ developers
• Developers can double-click the .sln to open in Visual Studio immediately
• Project settings (include dirs, lib dirs, preprocessor defines) are easier to see and edit in the VS Property Pages UI
• No extra CMake tooling or configuration step required
• Friendlier and easier for developers to understand and maintain

config.json must be visible in Solution Explorer

The config.json file (containing sdk_jwt, meeting_number, passcode) must be:

1. Included in the .vcxproj as a <None> item with <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
2. Placed in a "Config" filter in the .vcxproj.filters file so it appears under a "Config" folder in Solution Explorer
3. Easily editable by developers directly from Solution Explorer — they should never have to hunt for it in File Explorer

Example .vcxproj entry:

<ItemGroup>
  <None Include="config.json">
    <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
  </None>
</ItemGroup>

Example .vcxproj.filters entry:

<ItemGroup>
  <Filter Include="Config">
    <UniqueIdentifier>{GUID-HERE}</UniqueIdentifier>
  </Filter>
</ItemGroup>
<ItemGroup>
  <None Include="config.json">
    <Filter>Config</Filter>
  </None>
</ItemGroup>

Overview

The Windows SDK is a C++ native SDK designed for:

• Desktop applications - Native Windows apps with full UI control
• Headless bots - Join meetings without UI
• Raw media access - Capture/send audio/video streams
• Local recording - Record meetings locally or to cloud

Key Architectural Insight

The SDK follows a universal 3-step pattern for every feature:

1. Get controller (singleton): meetingService->Get[Feature]Controller()

…