# Oauth App type for multiple distinct domains

**URL:** <https://devforum.zoom.us/t/oauth-app-type-for-multiple-distinct-domains/76823>\
**Category:** App Marketplace\
**Created:** [October 3, 2022, 1:59am UTC](https://devforum.zoom.us/t/oauth-app-type-for-multiple-distinct-domains/76823 "2022-10-03T01:59:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![elearningevolve](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elearningevolve/32/75605_2.png) [@elearningevolve](https://devforum.zoom.us/u/elearningevolve)\
**Post date:** [October 3, 2022, 1:59am UTC](https://devforum.zoom.us/t/oauth-app-type-for-multiple-distinct-domains/76823/1 "2022-10-03T01:59:37Z")

</div>

If a user wants to add the Oauth creds to multiple distinct domains e.g:

1. [example.com](http://example.com)
2. [mytestsite.com](http://mytestsite.com)
3. [mynewsite.com](http://mynewsite.com)

Will the user have to create a new Oauth app type and add the creds separately for each of the domains or is there a better/user-friendly way available to achieve this?

Is a Server-to-Server OAuth app type a better solution in this particular situation? Does it have any downside as compared to the Oauth app type?

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [October 3, 2022, 3:55am UTC](https://devforum.zoom.us/t/oauth-app-type-for-multiple-distinct-domains/76823/2 "2022-10-03T03:55:05Z")

</div>

Hi @elearningevolve ,

Check out our documentation on using multiple subdomains:

> **[OAuth with Zoom](https://marketplace.zoom.us/docs/guides/auth/oauth/#using-multiple-environments)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

Does this work for you?

---

<div class="post-metadata">

**Author:** ![elearningevolve](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elearningevolve/32/75605_2.png) [@elearningevolve](https://devforum.zoom.us/u/elearningevolve)\
**Post date:** [October 3, 2022, 10:04pm UTC](https://devforum.zoom.us/t/oauth-app-type-for-multiple-distinct-domains/76823/3 "2022-10-03T22:04:15Z")

</div>

No, I am not referring to subdomains but rather completely different domains. This is not covered in the documentation and I would appreciate a dedicated response to my earlier question.

> If a user wants to add the Oauth creds to multiple distinct domains e.g:
> 
> 1. [example.com](http://example.com/)
> 2. [mytestsite.com](http://mytestsite.com/)
> 3. [mynewsite.com](http://mynewsite.com/)
> 
> Will the user have to create a new Oauth app type and add the creds separately for each of the domains or is there a better/user-friendly way available to achieve this?
> 
> Is a Server-to-Server OAuth app type a better solution in this particular situation? Does it have any downside as compared to the Oauth app type?

Thanks!

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [October 4, 2022, 12:22am UTC](https://devforum.zoom.us/t/oauth-app-type-for-multiple-distinct-domains/76823/4 "2022-10-04T00:22:09Z")

</div>

@elearningevolve ,

I believe so, as long as it is whitelisted and you can verify each domain.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [November 2, 2022, 11:59am UTC](https://devforum.zoom.us/t/oauth-app-type-for-multiple-distinct-domains/76823/5 "2022-11-02T11:59:52Z")

</div>

Closed on November 2, 2022, 11:59am UTC

This topic was automatically closed after 30 days. New replies are no longer allowed.