#Zoom account types code#

This process is provisioned by Zoom via the Publishable URL. The user will see a dialog box with permission request for access. The Client directs the user to the Zoom authorization server.

#Zoom account types code#

The following steps provide an overview of the Authorization Code grant flow: The usage of this grant type is described in detail in the OAuth with Zoom guide. Authorization CodeĪn Authorization Code is the most commonly-used grant type for Zoom APIs. However, with Zoom APIs, you should use either the Authorization Code or Client Credentials grant types. The grant type refers to the method the Client uses to request authorization. OAuth grant typesĪn Authorization Grant is the authorization assigned to the Client by the resource owner.

The Server-to-Server OAuth app type skips the end user authorization step as well as the redirect URL and refresh token. Server-to-server authentication does not require the end user to authorize the app to access the user's information. If the authentication fails, an error is thrown stating what caused the error.

After the Zoom API server authenticates the app, it sends back the Requested Resource in the form of a JSON response.

In this case, the client must use the Refresh Token to request another valid access token. When an access token expires, it becomes invalid.

The app calls the Zoom API to access requested resource by including the Access Token in the request as a means of authentication.

The access token must be used as a means of authentication while making API calls to the Zoom API Server.

The Zoom Authorization Server acknowledges that user has permitted the app with requested access and it sends an Access Token along with a Refresh Token back to the app.

The app presents the Authorization Grant to the Zoom Authorization Server to verify that it has received the user's permission to access user information.

The user authorizes the app and the app receives an Authorization Grant.

The Client (your app) requests authorization from the Zoom user to access the user's information.

Zoom Authorization Server - The authorization server issues access tokens to the client after successfully authenticating and obtaining authorization from the resource owner.

If your app makes access requests to the Zoom API, then your app is considered the Client.

Client - The application that requests access to the user's information.

If your app is integrating with the Zoom API to obtain user-related information, then the Zoom API server is considered the resource server.

Resource Server - The server that hosts the resource.

Resource Owner - A user in a Zoom account who can either authorize or decline a Client from accessing information related to the user's Zoom account.

These roles are actively involved in the process of authentication with Zoom APIs: The OAuth protocol defines four specific roles. To begin using the OAuth protocol for your app's authentication with Zoom, you must create either an OAuth app or a Server-to-Server OAuth app in the Zoom App Marketplace. The following sections provide an overview on the OAuth protocol. OAuth 2.0 lets applications obtain access to Zoom resources, such as the user's profile information, via the Zoom API. Zoom must authenticate each HTTP request made to the Zoom API.

Understanding Personal Meeting ID (PMI).

Both of these terms refer to an app integrating with the Zoom API. Note: In this document, you will see the terms client and app used interchangeably.