# Oauth Request Access Token - redirect\_uri - Missing Documentation

**URL:** <https://devforum.zoom.us/t/oauth-request-access-token-redirect-uri-missing-documentation/5387>\
**Category:** API and Webhooks\
**Created:** [August 7, 2019, 6:24pm UTC](https://devforum.zoom.us/t/oauth-request-access-token-redirect-uri-missing-documentation/5387 "2019-08-07T18:24:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![eric](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/eric/32/1490_2.png) [@eric](https://devforum.zoom.us/u/eric)\
**Post date:** [August 7, 2019, 6:24pm UTC](https://devforum.zoom.us/t/oauth-request-access-token-redirect-uri-missing-documentation/5387/1 "2019-08-07T18:24:14Z")

</div>

Documentation should be cleared up on this page: [https://marketplace.zoom.us/docs/guides/authorization/oauth/oauth-with-zoom](https://marketplace.zoom.us/docs/guides/authorization/oauth/oauth-with-zoom)

For the Request Access Token (/oauth/token) It is not clear what the redirect\_uri should be set to and that it has to match the Authorization Code request redirect\_uri. Why is that even needed? The “code” that is returned should be a precise indicator of what access token is being requested, along with the Basic Authentication Header.

Also there is no information on what an error might look like when returned, it’s format, contents, data type, … Will a 400 error always return a json node?

Thanks for cleaning this up for future users.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [August 7, 2019, 9:19pm UTC](https://devforum.zoom.us/t/oauth-request-access-token-redirect-uri-missing-documentation/5387/3 "2019-08-07T21:19:49Z")

</div>

Hey @eric,

Thanks for your feedback on our docs. We do have this line:

“ **NOTE: The redirect\_uri needs to be on your app’s whitelist in order to complete the OAuth transaction.** ”

As well as a description in the table of what the redirect\_uri should be.

 ![54%20PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/c/cdc2f8d8a9ac418206a0a42df5bf339f02e44255.png)

We will work on adding example error message / format.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![james2](https://avatars.discourse-cdn.com/v4/letter/j/6a8cbe/32.png) [@james2](https://devforum.zoom.us/u/james2)\
**Post date:** [May 14, 2020, 6:35am UTC](https://devforum.zoom.us/t/oauth-request-access-token-redirect-uri-missing-documentation/5387/4 "2020-05-14T06:35:31Z")

</div>

I too am baffled about why we need to include a redirect\_uri for a server-to-server call.

Doubly bad is that it doesn’t throw an error if you omit this redirect\_uri during development - you only hit the error once you go to production.

@tommy can you please shed some light on this?

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 19, 2020, 3:53pm UTC](https://devforum.zoom.us/t/oauth-request-access-token-redirect-uri-missing-documentation/5387/5 "2020-05-19T15:53:57Z")

</div>

Hey @james2,

Per our docs, it is a required field.

> **[OAuth 2.0 - Authorization - Documentation](https://marketplace.zoom.us/docs/guides/auth/oauth#step-2-request-access-token)**
>
> OAuth with Zoom
> 
> The Zoom API uses OAuth 2.0 to authenticate and authorize users to make requests. To setup access credentials and request scopes for yo...

Thanks,  
Tommy