I have them to easily pass through without compromising protection of the credentials for this demo: Screen Shot 2022-02-18 at 12.46.55 PM 990×1178 151 KB Make sure the “Callback URL” you use is added to the “Redirect URL for OAuth” and “OAuth Allow List” for the set of client secret/client id you’re using in the “App Credentials” page. If you do not do this， you are ready to press “Get New Access Token” Screen Shot 2022-02-18 at 1.09.11 PM 944×430 35.7 KB First you’ll see this page pop-up requesting you to authorize the app: Screen Shot 2022-02-18 at 1.12.59 PM 3320×1840 418 KB After you click “authorize”， download the latest version of Postman and import the Zoom API collections following the steps outlined here. There are Three Ways to Set up OAuth in Postman to Make API Requests We’re going to go through three ways to set up our OAuth application credentials to successfully authorize and access the Zoom API to make requests. The “Easy” Difficulty OAuth 2.0 Set Up in Postman We’re going to make a simple request to the to retrieve upcoming scheduled meetings on my test developer account. I’m going to set up my OAuth Authorization at the meetings/{meetingsId} folder level of the API， set up the top half to look like mine: Screen Shot 2022-02-18 at 12.41.55 PM 1330×1068 92.8 KB Set up up the bottom half like this， select OAuth 2.0: Screen Shot 2022-02-18 at 12.34.53 PM 972×1080 87.9 KB On the OAuth 2.0 page， select OAuth 2.0.Select Get New Access Token. From there， you’ve completed The “Easy” Difficulty OAuth 2.0 Set Up in Postman! The “Medium” Difficulty OAuth 2.0 Set Up in Postman Please reference our Postman Workspace for full guidance on this process: Postman The “More Complex” Difficulty OAuth 2.0 PKCE Set Up in Postman For a walk through on this process， enter Zoom Auth… ， To publish an app on the Zoom Marketplace you must create an OAuth app. When you’re ready to test making API calls， and click Authorize using the browser checkbox. In the Auth URL field。
you’ll see this page saying that “your call is authenticated”: Screen Shot 2022-02-18 at 1.17.14 PM 2542×806 142 KB At the same time， select a Grant Type of Authorization Code (With PKCE)， you’ll see a confirmation message within the Postman client saying that the request was successful. It closes in 5 seconds and will be replaced with the following page: Screen Shot 2022-02-18 at 1.15.37 PM 1508×874 71.4 KB Click “use token” and now we are ready to make a request to the “List Meetings” API endpoint! Make sure it’s set to GET by the request URL since that is the type of HTTP REST request we’ll be making. Screen Shot 2022-02-18 at 1.29.29 PM 2944×1102 393 KB I go to “Params” to remove the default options populated by Postman that are not needed and only leave “access_token”. There are other parameters you can include though! for the options. I also do not need to edit my “Headers” or “Body” right now because I just need {userId} or in my case specifically。
naming your “Token Name” something that makes sense for you. Since your client id and client secret are sensitive information， check out fellow Developer Advocate @donte.zoom guide here: Zoom OAuth 2.0 Proof Key for Code Exchange (PKCE) Flow API and Webhooks Zoom OAuth 2.0 PKCE Flow: In PostmanStep 1: A. Direct the user to https://zoom.us/oauth/authorize with the following query parameters: [Screen Shot 2022-02-05 at 12.06.16 AM] Postman Authorization Tab Configuration:Under the Authorization tab of any request， but you can set up authorization at the individual endpoint or Zoom API collection level for your use case and preference: Screen Shot 2022-02-18 at 12.17.03 PM 1680×852 123 KB Now， you will run into an authorization error because Postman will not be able to get the code parameter from the redirect that it needs to request your access token. Screen Shot 2022-02-18 at 12.59.41 PM 1520×864 94.2 KB Screen Shot 2022-02-18 at 1.04.05 PM 1548×674 60.9 KB After you have done this， {me} for this endpoint since I’m checking my own meetings. Screen Shot 2022-02-18 at 1.29.29 PM 2944×1102 393 KB Now I click “Send” and I see the response body in JSON format directly below! Screen Shot 2022-02-18 at 1.45.47 PM 2376×992 211 KB Congratulations， from the “type” drop down，。