# App Deathorized hook not hitting development accounts?

**URL:** <https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514>\
**Category:** API and Webhooks\
**Created:** [November 5, 2019, 10:36am UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514 "2019-11-05T10:36:14Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jimig](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jimig/32/1815_2.png) [@jimig](https://devforum.zoom.us/u/jimig)\
**Post date:** [November 5, 2019, 10:36am UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/1 "2019-11-05T10:36:14Z")

</div>

If we uninstall an app in development, why don’t we get the webhook?

I can confirm it works in production mode.

---

<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:** [November 5, 2019, 9:58pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/3 "2019-11-05T21:58:02Z")

</div>

Hey @jimig,

Currently the deauth webhook only fires for uninstallation of production apps.

As you can see there is no “Development Deauthorization Endpoint URL” field, it is only for production.

 ![58%20PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/6/64c4d722c2966dc69fd7fb3771c98faeaf54125f.png)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![jimig](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jimig/32/1815_2.png) [@jimig](https://devforum.zoom.us/u/jimig)\
**Post date:** [November 6, 2019, 7:59am UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/4 "2019-11-06T07:59:11Z")

</div>

Thanks, but how is one supposed to test this webhook?

---

<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:** [November 6, 2019, 4:52pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/5 "2019-11-06T16:52:39Z")

</div>

Hey @jimig,

For testing in your development environment, you can put your development deauth url as the deauth url, then install the production version of your app, and then uninstall it and the payload will be sent to your development deauth url.

Let me know if that helps! 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![prasanti.prusty](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/prasanti.prusty/32/12025_2.png) [@prasanti.prusty](https://devforum.zoom.us/u/prasanti.prusty)\
**Post date:** [July 16, 2020, 5:32pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/6 "2020-07-16T17:32:15Z")

</div>

Hi @tommy,

I followed the same and used the payload data for compliance post requests.  
But the compliance response gives 404 error code with bellow response.

```
 {"reason":"Invalid client id or client secret","error":"invalid_request"}

```

My app is not yet approved and I followed the below steps.

> [@App Deathorized hook not hitting development accounts?](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/5):
>
> Hey @jimig, For testing in your development environment, you can put your development deauth url as the deauth url, then install the production version of your app, and then uninstall it and the payload will be sent to your development deauth url. Let me know if that helps! slight_smile Thanks, Tommy

Thanks!  
Prasanti

---

<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:** [July 21, 2020, 4:49pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/7 "2020-07-21T16:49:45Z")

</div>

Hey @prasanti.prusty,

Are you setting the authorization basic header when making the deauth request?

`"Authorization": "Basic base64Encode(ClientID:ClientSecret)"`

> **[Data Compliance - Publishing an App - Documentation](https://marketplace.zoom.us/docs/guides/publishing/data-compliance#notify-zoom-of-data-compliance)**
>
> Data Compliance
> 
> All Marketplace app developers must comply with users’ preferences on how their data should be handled. 
> 
> The Zoom Data Compliance requ...

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![victor.koa](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/victor.koa/32/16927_2.png) [@victor.koa](https://devforum.zoom.us/u/victor.koa)\
**Post date:** [October 26, 2020, 9:20am UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/8 "2020-10-26T09:20:55Z")

</div>

> [@tommy](#):
>
> For testing in your development environment, you can put your development deauth url as the deauth url, then install the production version of your app, and then uninstall it and the payload will be sent to your development deauth url.

Hi Tommy, I did this but nothing received. How long does it take to receive the payload?

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 26, 2020, 10:42pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/9 "2020-10-26T22:42:10Z")

</div>

Hi @victor.koa,

This should be relatively immediate. Can you try following the steps outlined here and let me know if you’re still having trouble?

> [@Data Compliance API - Deauthorization Endpoint URL](https://devforum.zoom.us/t/data-compliance-api-deauthorization-endpoint-url/3870/15):
>
> Hey @john! You are correct, you will only receive the Deauthorization Event Notification Webhook with the Production version of your app. You can test this by installing the production version of your app via your apps publishable URL, [54%20PM] And then [uninstalling your app on your “Installed Apps” page.](https://marketplace.zoom.us/user/installed) I made a simple PHP web server and was able to see the Verification Token in the request headers (when testing a Zoom event/webhook sent to my server). Here is my code: Examp…

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![victor.koa](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/victor.koa/32/16927_2.png) [@victor.koa](https://devforum.zoom.us/u/victor.koa)\
**Post date:** [October 27, 2020, 4:05pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/10 "2020-10-27T16:05:26Z")

</div>

Just followed this exact procedure (install by production publishable URL then uninstall from the “Installed apps” page) and did not receive any call on my backend. I receive the zoom emails but that’s it 😕

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 28, 2020, 4:37pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/11 "2020-10-28T16:37:44Z")

</div>

Hey @victor.koa,

Can you confirm that your deauthorization endpoint URL is publicly accessible and is prepared to send back a 200OK response when payloads are received? This must be 200OK (can’t be a 300, etc.).

Let me know,  
Will

---

<div class="post-metadata">

**Author:** ![victor.koa](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/victor.koa/32/16927_2.png) [@victor.koa](https://devforum.zoom.us/u/victor.koa)\
**Post date:** [October 28, 2020, 4:51pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/12 "2020-10-28T16:51:15Z")

</div>

Yes @will.zoom, it is publicly accessible and ready to send 200

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 29, 2020, 6:00pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/13 "2020-10-29T18:00:29Z")

</div>

Hey @victor.koa,

I just DM’d you for some additional details.

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![hsiung](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hsiung/32/19607_2.png) [@hsiung](https://devforum.zoom.us/u/hsiung)\
**Post date:** [December 2, 2020, 5:57pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/15 "2020-12-02T17:57:16Z")

</div>

I’m also experiencing the same issue. I’m not getting a deauthorization webhook notification after uninstalling the production version of the app. The endpoint we configured is publically accessible and I don’t see any activity in the server logs on uninstall.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [December 3, 2020, 5:45pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/16 "2020-12-03T17:45:30Z")

</div>

Hey @hsiung,

Is it possible share the endpoint you’re using so that I can take a closer look? Please ensure it returns a 200OK response upon receipt of receiving payloads as well.

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![hsiung](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hsiung/32/19607_2.png) [@hsiung](https://devforum.zoom.us/u/hsiung)\
**Post date:** [December 4, 2020, 4:12am UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/17 "2020-12-04T04:12:04Z")

</div>

Hi @will.zoom I am using hookbin to debug as well and do not see any notifications. Currently, I have it set to [https://hookb.in/zroxQJ3ZBeHykkGKwlwm](https://hookb.in/zroxQJ3ZBeHykkGKwlwm)

You can view the activity at [https://hookbin.com/zroxQJ3ZBeHykkGKwlwm](https://hookbin.com/zroxQJ3ZBeHykkGKwlwm)

---

<div class="post-metadata">

**Author:** ![hsiung](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/hsiung/32/19607_2.png) [@hsiung](https://devforum.zoom.us/u/hsiung)\
**Post date:** [December 4, 2020, 7:22pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/18 "2020-12-04T19:22:46Z")

</div>

It’s fixed now after I tapped on “Regenerate” for the Publish URL and installed/uninstalled.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [December 7, 2020, 6:24pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/19 "2020-12-07T18:24:38Z")

</div>

Hi @hsiung,

Thanks for confirming, and glad it’s resolved!

Best,  
Will

---

<div class="post-metadata">

**Author:** ![cloudabilitysaas](https://avatars.discourse-cdn.com/v4/letter/c/e36b37/32.png) [@cloudabilitysaas](https://devforum.zoom.us/u/cloudabilitysaas)\
**Post date:** [December 8, 2020, 12:21am UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/20 "2020-12-08T00:21:24Z")

</div>

Hi @will.zoom

I also experienced the same issue. I had set the de-auth webhook URL to be the one we used for testing and uninstalled the App in production and didn’t see the event posted in the dev webhook endpoint. I tried to follow the steps in this thread as well regenerated the publishURL.

Could you please help?

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [December 8, 2020, 8:43pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/21 "2020-12-08T20:43:40Z")

</div>

Hey @cloudabilitysaas,

Thank you for reaching out to Zoom Developer Support. Please double-check the following:

1. You are installing the production instance of your app using the Publishable URL
2. The endpoint that you’ve provided is publicly accessible and returns a 200 OK response to the payload

Would it be possible to share the endpoint that you’re using?

Thanks,  
Max

---

<div class="post-metadata">

**Author:** ![cloudabilitysaas](https://avatars.discourse-cdn.com/v4/letter/c/e36b37/32.png) [@cloudabilitysaas](https://devforum.zoom.us/u/cloudabilitysaas)\
**Post date:** [December 10, 2020, 7:59pm UTC](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514/22 "2020-12-10T19:59:07Z")

</div>

Hi there, I am using [https://saas-alpha.cloudability.com/portal/ZoomOAuth/DeauthorizedEvent](https://saas-alpha.cloudability.com/portal/ZoomOAuth/DeauthorizedEvent) as the endpoint. This is our testing stack.

[Next page](https://devforum.zoom.us/t/app-deathorized-hook-not-hitting-development-accounts/6514.md?page=2)
