# Get started with Zoom Meeting SDK for Windows > **Beginning March 2 2026**, apps joining meetings outside their account must be authorized. Authorize apps by using either ZAK or OBF tokens, or RTMS. [Learn more](/docs/meeting-sdk/obf-faq/). > **Requirements for external meeting access** > > To join meetings outside of your developer account, your app must: > > - Be [reviewed by Zoom](/docs/build-flow/submitting-apps-for-review/). > - Authenticate with either a ZAK or On Behalf Of (OBF) token to attribute to a user in a meeting. > > You can: > > - [Publish the approved app on the Zoom App Marketplace](/docs/distribute/). > - Set your app to [unlisted](/docs/build-flow/app-listing/eu-and-discoverability/#app-discoverability). > - Contact the [Integrated Software Vendor (ISV) sales team](https://explore.zoom.us/en/isv/#isv) for other options. ## Prerequisites See the [Changelog](/changelog) for the **latest** supported Zoom Meeting SDK version. See [Minimum SDK version](/docs/meeting-sdk/minimum-version/) for the **minimum** supported version. - Use [Visual Studio 2019](https://visualstudio.microsoft.com/) or newer. In this documentation, we use Visual Studio 2019 as our default IDE. - When installing Visual Studio, install **Desktop development with C++** workloads and the platform SDKs that you're building for. - A [JWT token](/docs/sdk/meeting-sdk/auth) to authenticate the app - **For individual users, a Zoom Access Key (ZAK)** - send a **GET** request to the https://api.zoom.us/v2/users/{userId}/token with `type="zak"` and pass it to the SDK with [JoinMeetingParam4WithoutLogin](https://marketplacefront.zoom.us/sdk/meeting/windows/structtag_join_param4_without_login.html)'s [userZAK](https://marketplacefront.zoom.us/sdk/meeting/windows/structtag_join_param4_without_login.html#a83c6513e5d1822596445622d19f514af) or [StartMeetingParamsWithoutLogin](https://marketplacefront.zoom.us/sdk/meeting/windows/structtag_start_param4_without_login.html)'s [userZAK](https://marketplacefront.zoom.us/sdk/meeting/windows/structtag_start_param4_without_login.html#a0af5af5f511af4a8f66ecd31f8361844). - **For apps that need to join the meeting as individual users, an OnBehalf Of (OBF) token** - send a GET request to https://api.zoom.us/v2/users/{userId}/token with `type="onbehalf"` and pass it to the SDK with [JoinMeetingParam4WithoutLogin](https://marketplacefront.zoom.us/sdk/meeting/windows/structtag_join_param4_without_login.html)'s [onBehalfToken](https://marketplacefront.zoom.us/sdk/meeting/windows/structtag_join_param4_without_login.html#aa3c0a12a7f76a735d1a6bf4aef227ead). - To run the demo app, you'll need a meeting ID and passcode. > **Note** The Meeting SDK for Windows supports the same version as the Zoom client. See Zoom system requirements: Windows, macOS, Linux for details. > **Note** > > Universal Windows Platform (UWP) is not supported. ## Download the Meeting SDK for Windows The Meeting SDK for Windows is available in C#, with or without a C# wrapper. > The C# wrapper is provided as a reference, and is not actively supported by Zoom. To access the SDK download files, you must be logged in to your Zoom App Marketplace developer account, and you need at least one app registered on the Zoom App Marketplace. If you **don't already have at least one registered app**, follow these steps to create an app and download the SDK files.
  1. Sign in to your developer account on the [Zoom App Marketplace](https://marketplace.zoom.us/?ampDeviceId=cf401538-835f-45ce-a7f1-1035e348c982&SessionId=1771892802618).
  2. Select **Develop > Build App > General app**, and then select **Create**.
  3. Go to **Features** and select **Embed**.
  4. On the **Embed** page, enable **Meeting SDK**.
  5. Under the **Meeting SDK** section, configure the settings as appropriate for your app.
  6. To download the SDK files, select the platform **Windows**. This page displays available SDK versions for the selected platform, along with links to their corresponding release notes.
  7. Finally, select the **Download** button.
If you **already have at least one registered app**, follow these steps to download the SDK files using your existing app.
  1. Sign in to your developer account on the [Zoom App Marketplace](https://marketplace.zoom.us/?ampDeviceId=cf401538-835f-45ce-a7f1-1035e348c982&SessionId=1771892802618).
  2. Select **Manage**, and open your SDK app.
  3. Go to **Features** and select **Embed**.
  4. On the **Embed** page, go to the **Meeting SDK** section.
  5. To download the SDK files, select the platform **Windows**. This page displays available SDK versions for the selected platform, along with links to their corresponding release notes.
  6. Finally, select the **Download** button.
## Verify files Your downloaded ZIP file should have these files and folders inside the **zoom-sdk-windows-master** folder. ```plaintext ├─ CHANGELOG.md ├─ README.md ├─── x64 (or x86) ├───── bin ├───── h (wrapperless version only) ├───── lib (wrapperless version only) ├───── zoom_sdk_c_sharp_wrap (c# wrapper version only) ├───── [demo] or [zoom_sdk_demo] <- Examples are inside └─ version.txt ``` The wrapper **DLL** is located at `zoom-c-sharp-wrapper-master\bin\zoom_sdk_dotnet_wrap.dll`. If you have different file structures or have missing files, download the SDK package from the [App Marketplace](https://marketplace.zoom.us/) again. ### Get the version number The downloaded Meeting SDK folder contains a file called `version.txt`. The number inside that text file is the version number of the downloaded SDK. Always include the **version number** when you post a question to get support from our premiere developer support or on our [community forum](https://devforum.zoom.us/). ## Load the project In **Visual Studio**, open the `demo/sdk_demo_v2/sdk_demo_v2.sln` file. Use the included `sdk_util.cpp` high-level application to understand how to call the stack functions and register callbacks. The Zoom SDK runs as a `DLL` in the context of the calling application process. In **Visual Studio**, open the `zoom_sdk_demo/zoom_sdk_demo.csproj` file. > **Note:** Starting from 4.6.15798.0403, all DLL files(_.dll) and EXE files(_.exe) cannot be re-signed. DO NOT re-sign or assign new digital signatures to those files as this could lead to fatal errors.