Dynamic Installation and Deauthorization URLs

[tommy (Tommy Gaessler)]

Hey @darren,

I understand your architecture of the url paths.

I don’t see the issue for the DeAuth url because that URL is for accepting a POST request with the Zoom user in the payload, so I think this would not affect your company specific URL paths. (Of course correct me if I am wrong.)

As for the Installation URL, you could include the company slug in a query param at the end of the install URL, which persists through the OAuth flow, and handle the redirect once you the user lands on the redirect URL.

For example:

{oauth_zoom_install_url}?state=zoom
{oauth_zoom_install_url}?state=google

After install and redirect:

{oauth_redirect_url}?state=zoom
{oauth_redirect_url}?state=google

See the second part of my post here for more details:

Develop and publish an oAuth App

Hey @ravikumar.boddu, thanks for posting and using Zoom! No, the user who installs your app does not see the Client Secret, and cannot change either the client ID or Client Secret. For their instance of the installation, you can request an access_token to make API requests. You can either publish 2 Apps to the Marketplace, one per customer, or you can add a state query param to the install url to pass data like who that customer is, then read the state query param and do the logic you need o…

Let me know if that helps!

Thanks
Tommy