We have a clinical SaaS application to manage appointments. A clinic can have one or more doctors. Some of our doctors would like to use Zoom for telemedicine. We have completed the OAuth integration at the Account level, so a clinic in our system gets linked to their own account in Zoom. After that they map the Zoom users in their account to doctors in our system.
As our clinical setup is complex and we want to make Zoom integration available only to our registered clinics only, from inside our application. We don’t have a workflow where people can visit Zoom marketplace and install their app from there. Therefore, we don’t have a use-case to publish the app in the marketplace. But, without publishing the app, we are not able to use it outside our account.
Could someone please tell us whether it is possible to use Zoom integration without publishing the app in the marketplace? If so, how can we go about it?
Any help is greatly appreciated!
The only way to share your Zoom OAuth app outside your Zoom account is to publish it.
That being said, you could use the “visit site to install” option (which hides the install url from the public):
Or, after a user installs your app, you can do a check on the account_id and compare that with your whitelist of companies who are allowed to install your app.
Our app has a similar requirement. How does “publishable URL” work in conjunction with “Visit Site to Install”? We need to test the app from another account outside the app. Users can’t really click the “publishable URL” to install the app since the app can only be installed from our own landing page.
The publishable URL is a beta testing url.
The “Visit Site to Install” option means your app will still be listed on the marketplace, but instead of an install button showing, it will show a link to your site, then on your site, you can display the install link on your own landing page.