Request user authorization
Step 1: Request User Authorization
Click the Params tab.
If this is your first time authorizing Zoom API access, update the
client_id
and
redirect_uri
variables with the appropriate fields from the App Credentials tab of your OAuth app from the Zoom App Marketplace.
To verify that this is your first time, and to test the manual OAuth 2.0 process, navigate to the Local Test tab of your app and check if it says
added
. If so, click
remove
before proceeding with the next action.
After updating the
client_id
and
redirect_uri
variables in the Qodex Params tab, the URL should resemble this:
https://zoom.us/oauth/authorize?response_type=code&client_id={{ClientID}}&redirect_uri={{redirect_uri}}
Now paste that URL in the browser you logged into the Zoom App Marketplace and using to test this flow and hit enter. Follow the prompt to authorize the app. Once you consent, you'll be redirected to a new page confirming the authorization. You'll also see a new url with a 'code' query parameter includes.Copy this 'code' query parameter. It's needed for the
POST Request access token
.
Proceed to the next request in this collection to continue.
Developer Documentation:
Request Params
| Key | Datatype | Required | Description |
| response_type
| string | | |
| client_id
| string | | OAuth application's Development or Production Client ID. |
| redirect_uri
| string | | URI to handle successful user authorization. Must match with Development or Production Redirect URI in your OAuth app settings.
|
| state
| null | | (Optional) An opaque value that you can use to maintain state between the request and callback. The authorization server appends the state value to the redirect URI. This is also useful to prevent cross-site request forgery. |
| code_challenge
| null | | (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. |
| code_challenge_method
| null | | (Optional) A method that was used to derive the code challenge. Defaults to "plain" if not present in the request. Code verifier transformation method is "S256" or "plain".
|
HEADERS
| Key | Datatype | Required | Description |
RESPONSES
status: ``