# Meeting SDK 2.9.0

**URL:** <https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105>\
**Category:** Meeting SDK\
**Created:** [November 21, 2022, 10:19am UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105 "2022-11-21T10:19:07Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![dhruv](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dhruv/32/43182_2.png) [@dhruv](https://devforum.zoom.us/u/dhruv)\
**Post date:** [November 21, 2022, 10:19am UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/1 "2022-11-21T10:19:08Z")

</div>

**Description**  
Unable to fetch code from “[https://zoom.us/oauth/authorize”](https://zoom.us/oauth/authorize%E2%80%9D)

**Browser Console Error**  
when we are sending a GET request from our server to this URL “[https://zoom.us/oauth/authorize?response\_type=code&client\_id={our\_cilent\_id}&redirect\_uri=https://example.com/interview/zoom-auth-callback/”](https://zoom.us/oauth/authorize?response_type=code&client_id=%7Bour_cilent_id%7D&redirect_uri=https://example.com/interview/zoom-auth-callback/%E2%80%9D)  
in response to this zoom is sending us Sign in page HTML.

**Which Web Meeting SDK version?**  
2.9.0

**Device (please complete the following information):**

- Device: Lenovo V14
- OS: Ubuntu 18.04
- Browser: Google Chrome
- Browser Version: 107.0.5304.110

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [November 21, 2022, 6:30pm UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/2 "2022-11-21T18:30:01Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![dhruv](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dhruv/32/43182_2.png) [@dhruv](https://devforum.zoom.us/u/dhruv)\
**Post date:** [November 22, 2022, 11:24am UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/3 "2022-11-22T11:24:12Z")

</div>

Hi @elisa.zoom  
Thanks for reverting. We did try the POST method but the result is still the same.  
Can you suggest something else?

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [November 22, 2022, 1:38pm UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/4 "2022-11-22T13:38:06Z")

</div>

@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 :

> **[GitHub - zoom/zoom-oauth-sample-app: Sample Zoom Oauth App NodeJS app to call...](https://github.com/zoom/zoom-oauth-sample-app)**
>
> Sample Zoom Oauth App NodeJS app to call Zoom's APIs - GitHub - zoom/zoom-oauth-sample-app: Sample Zoom Oauth App NodeJS app to call Zoom's APIs

This will provide a great OAuth implementation reference.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [November 22, 2022, 5:00pm UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/5 "2022-11-22T17:00:36Z")

</div>

Thanks for jumping in @donte.zoom

---

<div class="post-metadata">

**Author:** ![dhruv](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dhruv/32/43182_2.png) [@dhruv](https://devforum.zoom.us/u/dhruv)\
**Post date:** [November 23, 2022, 6:36am UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/6 "2022-11-23T06:36:46Z")

</div>

Hi @donte.zoom  
We are currently using Python3.7.4 on our server, and not NodeJS. Could you share any link/documentation around Python?

I’m pasting below the code we are using currently:

import requests  
def get\_access\_code():  
url = “[Error - Zoom](https://zoom.us/oauth/authorize?response_type=code)”  
token = requests.post(url, params={  
‘client\_id’: xxxxxxx,  
‘redirect\_uri’: [example.com/interview/zoom-auth-callback/](http://example.com/interview/zoom-auth-callback/)  
})  
return token

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [November 23, 2022, 1:28pm UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/7 "2022-11-23T13:28:46Z")

</div>

@dhruv ,

Please this post for OAuth python example :

> [@Zoom Oauth python example](https://devforum.zoom.us/t/zoom-oauth-python-example/78181/2):
>
> Hi, @asanford, Welcome to the Zoom Developer Platform – happy to help. Please see the below OAuth2 Python example script smiley #!/usr/bin/env python from flask import Flask, abort, request from uuid import uuid4 import requests import requests.auth import urllib CLIENT\_ID = "YOUR\_ZOOM\_CLIENT\_ID" # Fill this in with your client ID CLIENT\_SECRET = "YOUR\_ZOOM\_SECRET" # Fill this in with your client secret REDIRECT\_URI = "http://localhost:65010/zoom\_callback" app = Flask(\_\_name\_\_) @app.route…

Let me know if you have any questions !

---

<div class="post-metadata">

**Author:** ![dhruv](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dhruv/32/43182_2.png) [@dhruv](https://devforum.zoom.us/u/dhruv)\
**Post date:** [November 24, 2022, 7:29am UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/8 "2022-11-24T07:29:51Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [November 24, 2022, 2:32pm UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/9 "2022-11-24T14:32:28Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![dhruv](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dhruv/32/43182_2.png) [@dhruv](https://devforum.zoom.us/u/dhruv)\
**Post date:** [November 25, 2022, 10:10am UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/10 "2022-11-25T10:10:53Z")

</div>

@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.

> **[Zoom Integration](https://docs.google.com/document/d/1m0U3r34aVGlOfUWxrHJWraxtcD1yALcLpHEpMpfYU3Y/edit?usp=sharing)**
>
> Use Case: There are following 3 parties who will be participating in the zoom call Flexing it Consultant Company A company will create a calendar and a consultant will block the calendar. As soon as the calendar is blocked for a specific day and...

---

<div class="post-metadata">

**Author:** ![dhruv](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dhruv/32/43182_2.png) [@dhruv](https://devforum.zoom.us/u/dhruv)\
**Post date:** [November 28, 2022, 9:28am UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/11 "2022-11-28T09:28:21Z")

</div>

Hey @donte.zoom  
Quickly wanted to follow up here. Did you find time to refer to the shared doc?

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [November 29, 2022, 2:11am UTC](https://devforum.zoom.us/t/meeting-sdk-2-9-0/79105/12 "2022-11-29T02:11:44Z")

</div>

@dhruv,

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 😃

> **[Create a Server-to-Server OAuth app](https://marketplace.zoom.us/docs/guides/build/server-to-server-oauth-app/)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

Let me know if this helps.
