# How can I use mutable subdomain for Deauthorization Notification Webhook URL?

**URL:** <https://devforum.zoom.us/t/how-can-i-use-mutable-subdomain-for-deauthorization-notification-webhook-url/14050>\
**Category:** API and Webhooks\
**Created:** [April 20, 2020, 1:38pm UTC](https://devforum.zoom.us/t/how-can-i-use-mutable-subdomain-for-deauthorization-notification-webhook-url/14050 "2020-04-20T13:38:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tuancode](https://avatars.discourse-cdn.com/v4/letter/t/76d3ee/32.png) [@tuancode](https://devforum.zoom.us/u/tuancode)\
**Post date:** [April 20, 2020, 1:38pm UTC](https://devforum.zoom.us/t/how-can-i-use-mutable-subdomain-for-deauthorization-notification-webhook-url/14050/1 "2020-04-20T13:38:23Z")

</div>

**Description**  
Hi team,

Our product is an SaaS, hence, there are thousand of clients using the software distinguishing by subdomain. E.g. [https://client1.product.com](https://client1.product.com), [https://client2.product.com](https://client2.product.com).

I’m trying to integrate Zoom to provide our clients as a video conference tool in our system. However, it seems I can provide only 1 URL for Deauthorization Notification. This leads to a limit on my implementation for multiple clients based on 1 Zoom Oauth App.

Do you have any suggestion for this case?

**Which App Type ?**  
OAuth & Webhook

Thanks!

---

<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, 12:00am UTC](https://devforum.zoom.us/t/how-can-i-use-mutable-subdomain-for-deauthorization-notification-webhook-url/14050/2 "2020-04-21T00:00:35Z")

</div>

Hi @tuancode, reference our OAuth docs section on [Using Multiple Environments](https://marketplace.zoom.us/docs/guides/auth/oauth#advanced):

To support multiple subdomain environments for your users, add any as the subdomain of your Redirect URL (development & production).

**Example: [https://any.yourapp.com](https://any.yourapp.com)**.

In your install link, dynamically set the respective subdomain on the redirect\_uri param:

For [https://sub1.yourapp.com](https://sub1.yourapp.com):

`https://zoom.us/oauth/authorize?response_type=code&client_id=7lstjK9NTyett_oeXtFiEQ&redirect_uri=https://sub1.yourapp.com`

For [https://sub2.yourapp.com](https://sub2.yourapp.com):

`https://zoom.us/oauth/authorize?response_type=code&client_id=7lstjK9NTyett_oeXtFiEQ&redirect_uri=https://sub2.yourapp.com`

For deauthorization, I do not believe we support the same use of multiple environments, but I will confirm this. Each deauthorization event includes a userID; I would handle each userID and direct them to the appropriate environment/database.

Let us know if this helps; I’ll confirm further.

---

<div class="post-metadata">

**Author:** ![tuancode](https://avatars.discourse-cdn.com/v4/letter/t/76d3ee/32.png) [@tuancode](https://devforum.zoom.us/u/tuancode)\
**Post date:** [April 21, 2020, 12:52am UTC](https://devforum.zoom.us/t/how-can-i-use-mutable-subdomain-for-deauthorization-notification-webhook-url/14050/4 "2020-04-21T00:52:07Z")

</div>

Hi @michael.zoom,

Thank you. I think it’s quite impossible because of the event. It is impossible to Zoom can know which user belong to which subdomain. Therefore, the only solution I realise is that I have to implement a Centric API to redirect to corresponding Deauthorization Notification Subdomain URL.

---

<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, 9:47am UTC](https://devforum.zoom.us/t/how-can-i-use-mutable-subdomain-for-deauthorization-notification-webhook-url/14050/5 "2020-04-21T09:47:53Z")

</div>

Hey @tuancode,

As a workaround, you can have one deauth endpoint, that reads the body and then determines which subdomain the respective user\_id or account\_id is in, then make a request to the respective sub domain to complete the [data compliance flow](https://marketplace.zoom.us/docs/guides/app-lifecycle-management/data-compliance).

Thanks.  
Tommy

---

<div class="post-metadata">

**Author:** ![kay.gibbs](https://avatars.discourse-cdn.com/v4/letter/k/9de053/32.png) [@kay.gibbs](https://devforum.zoom.us/u/kay.gibbs)\
**Post date:** [March 15, 2021, 2:05pm UTC](https://devforum.zoom.us/t/how-can-i-use-mutable-subdomain-for-deauthorization-notification-webhook-url/14050/6 "2021-03-15T14:05:43Z")

</div>

Is there any update on this?  
It looks like there is a workaround, but is there the possibility of not limiting the deauth endpoint in the near future?

---

<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:** [March 16, 2021, 5:57pm UTC](https://devforum.zoom.us/t/how-can-i-use-mutable-subdomain-for-deauthorization-notification-webhook-url/14050/7 "2021-03-16T17:57:12Z")

</div>

Hey @kay.gibbs ,

We are considering adding this in the future. Can you please share this and your use case here: #feature-requests

Thanks,  
Tommy