This URL is the same as the Add Button link on the Zoom App Marketplace. Code verifier transformation method is "S256" or "plain". Defaults to "plain" if not present in the request. (Optional) A method that was used to derive the code challenge. (Optional, but required if using PKCE) A challenge derived from the code verifier sent in the authorization request to verify against the code_verifier later. The authorization server includes this value when redirecting the user-agent back to your app. (Optional) An opaque value that you can use to maintain state between the request and callback. OAuth application's Development or Production Client ID. Must match with Development or Production Redirect URI in your OAuth app settings. URI to handle successful user authorization. The supported authorization workflow requires the value code. Step 1: Request user authorizationĭirect the user to with the following query parameters: Query ParameterĪccess response type being requested. To retain this access level, your app can request refresh tokens.įollow the steps below to request access.
Once the user Authorizes the scopes, your app can request an access token. The user will Authorize or Decline these access permissions for your app. Zoom presents information about these scopes and access requests to the user. To get an access token, you'll set scopes for the level of access that your app needs from the user. If called from the client side, it will throw CORS errors. Follow the Create an OAuth App guide for a full walkthrough.Īll Zoom OAuth and API endpoints must be called from the server side of your application. To set up access credentials and request scopes for your app, create an OAuth app on the Marketplace. The Zoom API uses the OAuth 2.0 authorization framework ( rfc6749) to authenticate and authorize users to make requests.
0 kommentar(er)
