ZoomNet 0.47.0

.NET 5.0 .NET Standard 2.1 .NET Framework 4.8
Install-Package ZoomNet -Version 0.47.0
dotnet add package ZoomNet --version 0.47.0
<PackageReference Include="ZoomNet" Version="0.47.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add ZoomNet --version 0.47.0
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: ZoomNet, 0.47.0"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install ZoomNet as a Cake Addin
#addin nuget:?package=ZoomNet&version=0.47.0

// Install ZoomNet as a Cake Tool
#tool nuget:?package=ZoomNet&version=0.47.0
The NuGet Team does not provide support for this client. Please contact its maintainers for support.


License Sourcelink

Build status Tests Coverage Status CodeFactor

Release Notes NuGet (stable) MyGet (prerelease)
GitHub release NuGet Version MyGet Pre Release



The easiest way to include ZoomNet in your C# project is by adding the nuget package to your project:

PM> Install-Package ZoomNet

.NET framework suport

ZoomNet currently supports:

  • .NET framework 4.8
  • any framework supporting .NET Standard 2.1 (which includes .NET Core 3.x and ASP.NET Core 3.x)
  • .NET 5.0
  • .NET 6.0

The last version of ZoomNet that supported .NET 4.6.1, .NET 4.7.2 and .NET Standard 2.0 was 0.35.0


Connection Information

Before you start using the ZoomNet client, you must decide how you are going to connect to the Zoom API. ZoomNet supports two distinct ways of connecting to Zoom: JWT and OAuth.

Connection using JWT

This is the simplest way to connect to the Zoom API. Zoom expects you to use a key and a secret to generate a JSON object with a signed payload and to provide this JSON object with every API request. The good news is that ZoomNet takes care of the intricacies of generating this JSON object: you simply provide the key and the secret and ZoomNet takes care of the rest. Super easy!

As the Zoom documentation mentions, this is perfect if you're looking to build an app that provides server-to-server interaction with Zoom APIs.

Here is an except from the Zoom documentation that explains how to get your API key and secret:

JWT apps provide an API Key and Secret required to authenticate with JWT. To access the API Key and Secret, Create a JWT App on the Marketplace. After providing basic information about your app, locate your API Key and Secret in the App Credentials page.

When you have the API key and secret, you can instantiate a 'connection info' object like so:

var apiKey = "... your API key ...";
var apiSecret = "... your API secret ...";
var connectionInfo = new JwtConnectionInfo(apiKey, apiSecret);

Warning: <a href="https://marketplace.zoom.us/docs/guides/build/jwt-app/jwt-faq/">Zoom has announced</a> that this authentication method would be obsolete in June 2023. The recommendation is to swith to Server-to-Server OAuth.

Connection using OAuth

Using OAuth is much more complicated than using JWT but at the same time, it is more flexible because you can define which permissions your app requires. When a user installs your app, they are presented with the list of permissions your app requires and they are given the opportunity to accept.

The Zoom documentation has a document about how to create an OAuth app and another document about the OAuth autorization flow but I personnality was very confused by the later document so here is a brief step-by-step summary:

  • you create an OAuth app, define which permissions your app requires and publish the app in the Zoom marketplace.
  • user installs your app. During installation, user is presentd with a screen listing the permissons your app requires. User must click accept.
  • Zoom generates a "authorization code". This code can be used only once to generate the first access token and refresh token. I CAN'T STRESS THIS ENOUGH: the authorization code can be used only one time. This was the confusing part to me: somehow I didn't understand that this code could be used only one time and I was attempting to use it repeatedly. Zoom would accept the code the first time and would reject it subsequently, which lead to many hours of frustration while trying to figure out why the code was sometimes rejected.
  • The access token is valid for 60 minutes and must therefore be "refreshed" periodically.

ZoomNet takes care of generating the access token and the refresh token but it's your responsability to store these generated values.

var clientId = "... your client ID ...";
var clientSecret = "... your client secret ...";
var refreshToken = "... the refresh token previously issued by Zoom ...";
var accessToken = "... the access token previously issued by Zoom ...";
var connectionInfo = new OAuthConnectionInfo(clientId, clientSecret, refreshToken, accessToken,
    (newRefreshToken, newAccessToken) =>
            Save the new refresh token and the access token to
            a safe place so you can provide it the next time
            you need to instantiate an OAuthConnectionInfo.

For demonstration purposes, here's how you could use your operating system's environment variables to store the tokens

var clientId = "... your client ID ...";
var clientSecret = "... your client secret ...";
var refreshToken = Environment.GetEnvironmentVariable("ZOOM_OAUTH_REFRESHTOKEN", EnvironmentVariableTarget.User);
var accessToken = Environment.GetEnvironmentVariable("ZOOM_OAUTH_ACCESSTOKEN", EnvironmentVariableTarget.User);
var connectionInfo = new OAuthConnectionInfo(clientId, clientSecret, refreshToken, accessToken,
    (newRefreshToken, newAccessToken) =>
        Environment.SetEnvironmentVariable("ZOOM_OAUTH_REFRESHTOKEN", newRefreshToken, EnvironmentVariableTarget.User);
        Environment.SetEnvironmentVariable("ZOOM_OAUTH_ACCESSTOKEN", newAccessToken, EnvironmentVariableTarget.User);
Connection using Server-to-Server OAuth

This authentication method is the replacement for JWT authentication which Zoom announced will be made obsolete in June 2023.

From Zoom's documentation:

A Server-to-Server OAuth app enables you to securely integrate with Zoom APIs and get your account owner access token without user interaction. This is different from the OAuth app type, which requires user authentication. See Using OAuth 2.0 for details.

ZoomNet takes care of getting a new access token and it also refreshes a previously issued token when it expires (Server-to-Server access token are valid for one hour). Therefore

var clientId = "... your client ID ...";
var clientSecret = "... your client secret ...";
var accountId = "... your account id ...";
var connectionInfo = new OAuthConnectionInfo(clientId, clientSecret, accountId,
	(_, newAccessToken) =>
            Server-to-Server OAuth does not use a refresh token. That's why I used '_' as the first parameter
            in this delegate declaration. Furthermore, ZoomNet will take care of getting a new access token
            and to refresh it whenever it expires therefore there is no need for you to preserve the token
            like you must do for the 'standard' OAuth authentication.

            In fact, this delegate is completely optional when using Server-to-Server OAuth. Feel free to pass
            a null value in lieu of a delegate.

The delegate being optional in the server-to-server scenario you can therefore simplify the connection info declaration like so:

var connectionInfo = new OAuthConnectionInfo(clientId, clientSecret, accountId, null);


You declare your client variable like so:

var zoomClient = new ZoomClient(connectionInfo);
Product Versions
.NET net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows
.NET Core netcoreapp3.0 netcoreapp3.1
.NET Standard netstandard2.1
.NET Framework net48
MonoAndroid monoandroid
MonoMac monomac
MonoTouch monotouch
Tizen tizen60
Xamarin.iOS xamarinios
Xamarin.Mac xamarinmac
Xamarin.TVOS xamarintvos
Xamarin.WatchOS xamarinwatchos
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.47.0 107 8/3/2022
0.46.0 243 7/16/2022
0.45.0 98 7/8/2022
0.44.0 101 6/30/2022
0.43.0 1,022 5/31/2022
0.42.3 1,280 4/27/2022
0.42.2 94 4/25/2022
0.42.1 5,213 3/12/2022
0.42.0 2,027 3/7/2022
0.41.0 557 3/1/2022
0.40.0 249 2/22/2022
0.39.0 797 2/4/2022
0.38.0 119 1/31/2022
0.37.0 379 1/15/2022
0.36.0 3,349 11/29/2021
0.35.0 377 11/17/2021
0.34.0 923 10/25/2021
0.33.0 2,095 10/4/2021
0.32.4 275 9/21/2021
0.32.3 197 9/21/2021
0.32.2 3,061 9/16/2021
0.32.1 151 9/15/2021
0.31.0 15,368 6/7/2021
0.30.0 324 6/1/2021
0.29.0 4,723 5/12/2021
0.28.0 182 5/11/2021
0.27.2 1,716 4/7/2021
0.27.1 480 3/26/2021
0.27.0 184 3/25/2021
0.26.0 357 3/18/2021
0.25.0 431 3/4/2021
0.24.0 265 3/1/2021
0.23.0 17,885 2/27/2021
0.22.0 146 2/27/2021
0.21.0 460 2/18/2021
0.20.0 195 2/13/2021
0.19.0 295 2/9/2021
0.18.0 1,363 1/26/2021
0.17.0 241 1/22/2021
0.16.0 1,231 1/20/2021
0.15.0 1,440 1/14/2021
0.14.0 225 1/12/2021
0.13.0 201 1/12/2021
0.12.0 236 1/6/2021
0.11.0 361 12/31/2020
0.10.0 922 11/22/2020
0.9.0 4,710 10/2/2020
0.8.3 1,681 9/9/2020
0.8.2 219 9/8/2020
0.8.1 295 9/7/2020
0.7.0 270 8/29/2020
0.6.0 11,171 6/30/2020
0.5.1 314 6/17/2020
0.5.0 308 6/15/2020
0.4.1 303 6/1/2020
0.4.0 289 5/27/2020
0.3.0 252 5/26/2020
0.2.0 301 5/11/2020
0.1.0 272 5/6/2020