1. Pre-Requisite

In order to use the SDK, you need to make sure that the RETS API and the mobile SDK is enabled in your account. If not, please contact your account admin. Our windows SDK is written in C++ – if you are writing a C#/.NET application, you need to make sure that you can call the C++ library functions from within your application space.

Note that our SDK supports meeting service and do not support messaging currently.

  • Get the SDK key and secret from here

 

  • Depend on what your apps authentication option is, you might need to use the REST APIs to get the user id and user token. If your app is authenticating users with zoom user name and password, then you can ignore this step.  If not, use our APIs in your app to get the user id and usertoken or calling the REST API with a tool like Postman. The REST API “getbyemail” should provide the user id and usertoken

 

2. SDK Architecture and Workflow

Zoom SDK supports two options for user authentication.

  1. You can pass the user id of the user to the SDK initialization and all the meetings will start on that user’s account. This is referred to as API user
  2. There are times it might be cumbersome to get the user id and you might want to distribute your app to all Zoom users – in this case, you can ask the user to enter the Zoom login credentials (username /password) in your app and then pass it to the SDK.
  • API User join/start and leave:

  • Normal User join/start and leave meeting:

  • Normal User list/schedule/edit/delete meeting: