# Deauthorization Notification not working production **URL:** \ **Category:** App Marketplace\ **Created:** [July 10, 2024, 4:06pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408 "2024-07-10T16:06:37Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![yuki.niitsuma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuki.niitsuma/32/61351_2.png) [@yuki.niitsuma](https://devforum.zoom.us/u/yuki.niitsuma)\ **Post date:** [July 10, 2024, 4:06pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/1 "2024-07-10T16:06:37Z")
### Description I am currently facing an issue with the Deauthorization Notification feature in the Zoom application. I have set up the Deauthorization Notification for a private testing application. After establishing a connection with the testing application via OAuth and then removing the connection from the Zoom Marketplace, I confirmed that the notification was successfully sent to the Deauthorization Notification endpoint. However, when I performed the same setup and steps with our public production application, I found that the Deauthorization Notification was not working. In both cases, I used the Zoom account associated this account with for testing. The current issue seems to be most closely related to the one described at - [Deauthorization Endpoint URL Not Sending Data](https://devforum.zoom.us/t/deauthorization-endpoint-url-not-sending-data/48393/7) - [Zoom Deauthorization Notification not working for production environment](https://devforum.zoom.us/t/zoom-deauthorization-notification-not-working-for-production-environment/32905) ### Error No notification is being sent to the Deauthorization Notification endpoint for the public production application. ### How To Reproduce 1. **Applications** - [Testing private application](https://marketplace.zoom.us/apps/VbV2DCIWQ8q7Su8XinCwNA) - [Production public application](https://marketplace.zoom.us/apps/pVB8JrDWTGKgtf4i9Hga5A) 2. **Authentication Method or App Type** - OAuth 3. **Steps to Reproduce** 1’. Set up the Deauthorization Notification for both the private testing application and the public production application. 2’. Establish a connection with each application via OAuth. 3’. Remove the connection from the Zoom Marketplace. 4’. Observe the Deauthorization Notification endpoint for notifications. 4. **Any Errors** - No errors are displayed, but the notification is not received for the public production application. ---
**Author:** ![kwaku.nyante](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kwaku.nyante/32/23475_2.png) [@kwaku.nyante](https://devforum.zoom.us/u/kwaku.nyante)\ **Post date:** [July 11, 2024, 12:28pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/2 "2024-07-11T12:28:45Z")
Hello, @yuki.niitsuma is your App published? I do not believe this will work in Production till your app is published. Regards, Kwaku ---
**Author:** ![yuki.niitsuma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuki.niitsuma/32/61351_2.png) [@yuki.niitsuma](https://devforum.zoom.us/u/yuki.niitsuma)\ **Post date:** [July 12, 2024, 5:50am UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/3 "2024-07-12T05:50:58Z")
Hello @kwaku.nyante , Thank you for your response. I have attached the URL of the [production app](https://marketplace.zoom.us/apps/pVB8JrDWTGKgtf4i9Hga5A) in my forum post, and you should be able to confirm that the app is published by checking the provided URL. I consider the app to be published since it is visible on the store. However, if my understanding is incorrect, please let me know. regards, Yuki.Niitsuma ---
**Author:** ![kwaku.nyante](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kwaku.nyante/32/23475_2.png) [@kwaku.nyante](https://devforum.zoom.us/u/kwaku.nyante)\ **Post date:** [July 15, 2024, 6:02pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/4 "2024-07-15T18:02:59Z")
Hello @yuki.niitsuma OK so your app is Published, so has this never worked or it worked at some point and stopped working? Is this for all accounts or a specific account? Regards, Kwaku ---
**Author:** ![yuki.niitsuma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuki.niitsuma/32/61351_2.png) [@yuki.niitsuma](https://devforum.zoom.us/u/yuki.niitsuma)\ **Post date:** [July 16, 2024, 9:34am UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/5 "2024-07-16T09:34:39Z")
Hello @kwaku.nyante , Thank you for your response. > so has this never worked or it worked at some point and stopped working? Deauthorization Notification maybe has never worked in production app. To be more precise, the URL was set to the wrong Deauthorization Notification URL before the production app was published, but the URL was changed around the time of 2024/07/28 6 AM GMT. However, even though the URL was changed, the notification is not sent to the URL after the change. > Is this for all accounts or a specific account? I have tested it with two different accounts, but unfortunately, it did not work with either account. Regards, Yuki Niitsuma ---
**Author:** ![yuki.niitsuma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuki.niitsuma/32/61351_2.png) [@yuki.niitsuma](https://devforum.zoom.us/u/yuki.niitsuma)\ **Post date:** [July 22, 2024, 5:32am UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/6 "2024-07-22T05:32:59Z")
Hello @kwaku.nyante. Six days have passed, what is the current status? If there is not enough information from me, please reply to me and I’ll add it. Regards, Yuki Niitsuma. ---
**Author:** ![kwaku.nyante](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kwaku.nyante/32/23475_2.png) [@kwaku.nyante](https://devforum.zoom.us/u/kwaku.nyante)\ **Post date:** [July 22, 2024, 5:20pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/7 "2024-07-22T17:20:50Z")
Hello @yuki.niitsuma sorry I had some days off, so when it comes to your de-authorization url are they using the dev client ID or the Prod client ID, it won’t work if it’s using the dev credentials. Regards, Kwaku ---
**Author:** ![kwaku.nyante](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kwaku.nyante/32/23475_2.png) [@kwaku.nyante](https://devforum.zoom.us/u/kwaku.nyante)\ **Post date:** [July 22, 2024, 5:21pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/8 "2024-07-22T17:21:32Z")
Also if the endpoint is not on the whitelist please add it and give that a try too. Regards, Kwaku ---
**Author:** ![yuki.niitsuma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuki.niitsuma/32/61351_2.png) [@yuki.niitsuma](https://devforum.zoom.us/u/yuki.niitsuma)\ **Post date:** [July 23, 2024, 2:27am UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/9 "2024-07-23T02:27:56Z")
Hello, @kwaku.nyante. Thanks for your reply, and I hope your holidays were restful. > when it comes to your de-authorisation url are they using the dev client ID or the prod client ID, it won’t work if it’s using the dev credentials. I use the production client ID for oauth authentication to make sure it works. > Also if the endpoint is not on the whitelist, please add it and try that too. Am I correct in assuming that you want me to add the de-authorisation URL to the OAuth AllowList? If so, I don’t see the need to add the de-authorisation URL to the OAuth AllowList. Does the de-authorisation URL have to be added to the AllowList of OAuth for the de-association webhook to work? Regards, Yuki Niitsuma. ---
**Author:** ![kwaku.nyante](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kwaku.nyante/32/23475_2.png) [@kwaku.nyante](https://devforum.zoom.us/u/kwaku.nyante)\ **Post date:** [July 24, 2024, 1:51pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/10 "2024-07-24T13:51:13Z")
Hello, Yes sometimes that resolves issues like this let’s give this a try, if it doesn’t work we will have engineering get involved. Regards, Kwaku ---
**Author:** ![yuki.niitsuma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuki.niitsuma/32/61351_2.png) [@yuki.niitsuma](https://devforum.zoom.us/u/yuki.niitsuma)\ **Post date:** [July 25, 2024, 2:41am UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/11 "2024-07-25T02:41:48Z")
Hello, @kwaku.nyante I have added de-authorized URLs to the OAuth Allow List. I then linked the app again and “Remove App” from Marketplace, but I did not receive de-authorized notifications. I tried several times with both accounts and the results never changed. Regards, Yuki Niitsuma. ---
**Author:** ![kwaku.nyante](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kwaku.nyante/32/23475_2.png) [@kwaku.nyante](https://devforum.zoom.us/u/kwaku.nyante)\ **Post date:** [July 25, 2024, 4:38pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/12 "2024-07-25T16:38:08Z")
Since your app has been published have you submitted the updates for approval? Regards, Kwaku ---
**Author:** ![yuki.niitsuma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuki.niitsuma/32/61351_2.png) [@yuki.niitsuma](https://devforum.zoom.us/u/yuki.niitsuma)\ **Post date:** [July 26, 2024, 8:01am UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/13 "2024-07-26T08:01:33Z")
Hello, @kwaku.nyante . Thank you for reply. No, I did not submit after being published. Do I need to “Submit for review” even if I only want to change the URL notification address in the de-authorization notification after the app is published? Regards, Yuki Niitsuma. ---
**Author:** ![kwaku.nyante](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kwaku.nyante/32/23475_2.png) [@kwaku.nyante](https://devforum.zoom.us/u/kwaku.nyante)\ **Post date:** [July 26, 2024, 12:59pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/14 "2024-07-26T12:59:05Z")
Hello, Yes that is correct ---
**Author:** ![yuki.niitsuma](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/yuki.niitsuma/32/61351_2.png) [@yuki.niitsuma](https://devforum.zoom.us/u/yuki.niitsuma)\ **Post date:** [August 5, 2024, 6:30am UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/15 "2024-08-05T06:30:56Z")
Hello, @kwaku.nyante . Thank you for reply and sorry for the late reply, I was on vacation. I am going ahead with the “submit for review”. I just want to confirm one thing. I am assuming that “submit for review” will not require re-authentication of users who are already connected to the app, but I would like to know if my understanding of this is correct. I would like to know in advance if I need to re-authenticate, as it would be inconvenient for the current users of the app. Regards, Yuki Niitsuma. ---
**Author:** ![kwaku.nyante](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kwaku.nyante/32/23475_2.png) [@kwaku.nyante](https://devforum.zoom.us/u/kwaku.nyante)\ **Post date:** [August 5, 2024, 1:24pm UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/16 "2024-08-05T13:24:02Z")
Only scope changes require re-authorization. Regards, Kwaku ---
**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:** [August 9, 2025, 5:00am UTC](https://devforum.zoom.us/t/deauthorization-notification-not-working-production/113408/17 "2025-08-09T05:00:22Z")
This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.