# OAuth - how to generate multiple publishable URL

**URL:** <https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111>\
**Category:** App Marketplace\
**Created:** [April 20, 2020, 6:36pm UTC](https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111 "2020-04-20T18:36:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![rjd](https://avatars.discourse-cdn.com/v4/letter/r/bb73d2/32.png) [@rjd](https://devforum.zoom.us/u/rjd)\
**Post date:** [April 20, 2020, 6:36pm UTC](https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111/1 "2020-04-20T18:36:10Z")

</div>

Our zoom oauth app can only be installed after users sign in to our web site. Also we use different redirect URLs based on which environment the users sign in. We achieve this by 1) whitelisting URLs on our zoom oauth app; 2) creating the oauth app in the same accounts as the zoom users.

Then we wat to move oauth app into a different zoom account and need to create a publishable URL to test the app. How can we request multiple publishable URLs for the oauth app? I would like to avoid creating one zoom app for each of our environments.

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [April 21, 2020, 3:10am UTC](https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111/2 "2020-04-21T03:10:23Z")

</div>

Hi @rjd, you may not create OAuth apps on a user’s account - this is outside the terms of the [Zoom App Marketplace Terms of Use](https://zoom.us/docs/en-us/marketplace_tou.html) (Section 9, bullet 3).

Instead, you should release your app publicly on the Marketplace to allow for other users to install this app. Let us know if you have any questions on this process, we’re happy to help. 🙂

Instead of using this system of multiple apps, use one single subdomain `any` in your Redirect URL. Reference our documentation on [Using Multiple Environments](http://marketplace.zoom.us/docs/guides/auth/oauth#advanced).

---

<div class="post-metadata">

**Author:** ![rjd](https://avatars.discourse-cdn.com/v4/letter/r/bb73d2/32.png) [@rjd](https://devforum.zoom.us/u/rjd)\
**Post date:** [April 21, 2020, 4:30am UTC](https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111/3 "2020-04-21T04:30:38Z")

</div>

Hi Michael,

We currently have 3 domains

1. [any.outreach-dev.com](http://any.outreach-dev.com)  
Developers use this to test their changes before merging the changes to master branch.
2. [any.outreach-staging.com](http://any.outreach-staging.com)  
QA uses this to test the app in master branch before the app is prompted to production environment
3. [any.outreach.io](http://any.outreach.io)  
This is the production environment.

My questions are:

1. any suggestions on how to set up the oauth2 app to accommodate the 3 domains?
2. How can we test our zoom app before publishing it?  
Thanks

Jiandong

1.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [April 21, 2020, 5:54am UTC](https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111/4 "2020-04-21T05:54:55Z")

</div>

Hey @rjd,

You can accomplish this if you use the same base domain and use sub domains:

> [@Does zoom support more than two environments for oauth2?](https://devforum.zoom.us/t/does-zoom-support-more-than-two-environments-for-oauth2/11052/12):
>
> Hey @tuancode, @michael.solomon, This is totally possible! slight_smile 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](https://marketplace.zoom.us/docs/guides/auth/oauth#getting-access-token)) in your code, dyna…

You can test your app on your on Zoom account, or, request a beta testing url on the “Submit” page in your app settings.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![rjd](https://avatars.discourse-cdn.com/v4/letter/r/bb73d2/32.png) [@rjd](https://devforum.zoom.us/u/rjd)\
**Post date:** [May 16, 2020, 1:37am UTC](https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111/5 "2020-05-16T01:37:46Z")

</div>

I have requested publishable URL for testing. It will expire on May 22nd. I don’t think I can publish the app before the expiration date. I understand I will not be able to use the publishable URL for testing after expiration. But will I also lose the permission to publish the app?

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 19, 2020, 11:32pm UTC](https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111/6 "2020-05-19T23:32:14Z")

</div>

Hey @rjd,

No, you will not loose permission to publish the app. You will still be able to publish it once you are ready. 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 9:25pm UTC](https://devforum.zoom.us/t/oauth-how-to-generate-multiple-publishable-url/14111/7 "2020-08-21T21:25:53Z")

</div>

Closed on August 21, 2020, 9:25pm UTC


