'Invalid request : Redirect URI mismatch.' despite using ngrok

[tommy (Tommy Gaessler)]

Hey @Nad,

Let me know if this helps explain things:

---

The Redirect URI needs to be the same URI from the authorization (install URL) through to the Get Access Token request. So with these URLs set:

When I go to install the app from the “Activation” page, it defaults the redirect URI to the one specified in the “Redirect URL for OAuth” input:

https://zoom.us/oauth/authorize?response_type=code&client_id=ztmR8sxaSBGZ66b5laR7Ag&redirect_uri=https://zoom.us

So if I proceed to install the app, the redirect uri needs to be exactly https://zoom.us for the get access token request or else you will see the Redirect URI mismatch error

That being said, if from the start with the same settings above, I add the /meetings path to the authorize install url:

https://zoom.us/oauth/authorize?response_type=code&client_id=ztmR8sxaSBGZ66b5laR7Ag&redirect_uri=https://zoom.us/meeting

And then after I get the auth code, I make the access token request and set the redirect uri to the same as the one in the install url https://zoom.us/meeting it will work.

Does that make sense? So you can have dynamic redirect urls, but they need to be the same for both the authorize url and the get access token url requests.

More details here on how to handle this in your code:

Does zoom support more than two environments for oauth2?

Hey @tuancode, @michael.solomon, This is totally possible! Let me walk you through how to do this with the base domain of example.com For your whitelist, simply add your base domain: https://example.com Then in your dev/prod redirect url field, add a default redirect, https://any.example.com (this will be programmatically overridden to the correct sub domain, continue reading below) Now, with your install URL (the url mentioned in Step 1. of the OAuth guide) in your code, dyna…

---

Thanks,
Tommy