# Help with OAuth and redirect uri

**URL:** <https://devforum.zoom.us/t/help-with-oauth-and-redirect-uri/95378>\
**Category:** API and Webhooks\
**Created:** [September 19, 2023, 4:02pm UTC](https://devforum.zoom.us/t/help-with-oauth-and-redirect-uri/95378 "2023-09-19T16:02:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jferguson](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jferguson/32/9015_2.png) [@jferguson](https://devforum.zoom.us/u/jferguson)\
**Post date:** [September 19, 2023, 4:02pm UTC](https://devforum.zoom.us/t/help-with-oauth-and-redirect-uri/95378/1 "2023-09-19T16:02:14Z")

</div>

Can someone help me understand how the redirect uri in OAuth works and how I determine what to set that to?

I’ve spent hours going through API documentation and examples and no one really explains what’s behind the redirect uri. Everything simply says “add your redirect uri” but never explains how I’m supposed to know what that is. Do I need to create that backend service? Is it provided by the authentication provider?

What I’m specifically looking for is what redirect uri I should use for Zoom OAuth when our backend authentication mechanism uses SSO Azure? Do I need to build the web service for the uri? Does Zoom provide that? Or should I be pointing somewhere at Azure? Or is there some other third-party app I should look at?

I’m coding this in PowerShell, if there are any examples, but any language would be fine. I mainly just need to know who provides the uri so I can know where to continue to look.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [September 19, 2023, 8:28pm UTC](https://devforum.zoom.us/t/help-with-oauth-and-redirect-uri/95378/2 "2023-09-19T20:28:27Z")

</div>

Hey @jferguson, a Redirect URI is used for apps that handle user authorization. It’s the address a user is directed to after authorizing an app.

If you are integrating a backend service, you may want to use server-to-server OAuth instead.

> **[Server-to-Server OAuth](https://developers.zoom.us/docs/internal-apps/s2s-oauth/)**
>
> 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.

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [September 19, 2023, 8:35pm UTC](https://devforum.zoom.us/t/help-with-oauth-and-redirect-uri/95378/3 "2023-09-19T20:35:41Z")

</div>

If you were creating an app for user authorization, a redirect URI would be the address (created by your app) to handle a user’s successfully authorized state through a code parameter.

In our [user-level OAuth starter](https://github.com/zoom/user-level-oauth-starter/blob/main/routes/api/zoomOauth.js), we use the root of the app (on an HTTPS link created with ngrok) to listen for a ?code={code} query parameter.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [September 20, 2023, 8:36pm UTC](https://devforum.zoom.us/t/help-with-oauth-and-redirect-uri/95378/4 "2023-09-20T20:36:03Z")

</div>

Closed on September 20, 2023, 8:36pm UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.