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 once they install and authorize your app and land on your redirect url. Notice how I set the state query param on the install url and it persists through the install process to your redirect url.

https://zoom.us/oauth/authorize?client_id=7lstjK9NTyett_oeXtFiE&response_type=code&redirect_uri=http%3A%2F%2Flocalhost%3A4000?state=customer=cus1
\/
https://sumtotal.host/oauth/redirect?state=customer=cus1

https://zoom.us/oauth/authorize?client_id=7lstjK9NTyett_oeXtFiE&response_type=code&redirect_uri=http%3A%2F%2Flocalhost%3A4000?state=customer=cus2
\/
https://sumtotal.host/oauth/redirect?state=customer=cus2

https://marketplace.zoom.us/docs/guides/authorization/oauth/oauth-with-zoom#authorization-code

See this thread for more info on this question:

Thanks,
Tommy