Hi @dhruv
Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!
To get an access_token from our OAuth endpoint, you should be sending a POST request instead of a GET.
Could you pleas try with the POST method?
@dhruv ,
If you’re looking to understand how to implement the OAuth authorization flow, the first thing I would recommend is to reference our sample GitHub repo :
This will provide a great OAuth implementation reference.
Hi @donte.zoom
The provided solution didn’t work. In response to this, Zoom is sending us to the Sign in page. For context, we are using Python 3.7.4 and Django 2.2.8 on the server side. Ideally, we would want a Django based solution.
@dhruv ,
That’s expected behavior when you first go through the OAuth flow. You will have to sign in then you will be redirected to the endpoint you entered in the Marketplace OAUTH app. That aside, I just tested on my end and the solution is working as expected. It is likely something may be off in how its implemented in your application. Can you describe how you are handling implementing OAuth and tell us what you’ve tried ? Also, please post the entire script used so we so can see how you’ve implemented it.
@donte.zoom
I’m sharing this document which covers our use-case as well as the solution we are looking for, along with screenshots for reference. Kindly refer to it once.
Thank you for sharing more details about your use case. One potential path forward you can consider is using the Sever-to-Server OAuth in your backend to get an access token and make request against Zoom API to schedule a meeting. Server-to-server only requires making one request to get an access token, unlike the two-step OAuth 2.0 flow.
Here is our help documentation for Server-to-server OAuth