Oauth Request Access Token - redirect_uri - Missing Documentation

API and Webhooks
1

Documentation should be cleared up on this page: 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.

1 Like
3

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
Screen Shot 2019-08-07 at 3.17.54 PM.png733×106 7.84 KB

We will work on adding example error message / format.

Thanks,
Tommy

4

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?

5

Hey @james2,

Per our docs, it is a required field.

Thanks,
Tommy