Not Receiving Deauthorization Notifications at Webhook Endpoint for App Integration

Hello Zoom Developer Team,

I am experiencing an issue with deauthorization notifications for our Zoom integration, specifically related to the Dotdigital app.

Background:

Our application was previously receiving deauthorization notifications at a webhook endpoint managed through Blendr, which we have now discontinued. We recently updated the deauthorization URL in our app settings so that notifications should be sent to our Tray.ai webhook endpoint instead. Since making this change, we are no longer receiving deauthorization events when users delete the app from Zoom.

We have checked both the Tray.ai side and our Zoom settings, and there are no error messages or logs indicating a problem. The app itself was fully functional before this update, and no other changes have been made.

Could you please confirm the following:

  1. Is there an additional approval process or step required after specifying a new webhook URL before deauthorization notifications are sent?

  2. Is there any other configuration that needs to be done on Zoom’s side to activate these notifications?

  3. Can you provide troubleshooting advice, or are there any known issues with deauthorization notifications not being triggered after updating the webhook URL?

Please let me know if you require any further details, logs, or screenshots from our setup.

Thank you for your assistance!

Kind regards,
Unarine Makhesha

Hi @Rainbow1
Thanks for reaching out to us! Sorry to hear you are having issues receiving the Deauthorization notification webhook! I am happy to look further into this.
Quick question, did you submit your app for update review after you changed your endpoint URL? If not, this could be the reason why. Any changes you make to your app need to be reviewed and approved by our Marketplace team so they can be reflected in production

Hi Elisa

Thanks for your response and insight , we haven’t actually resubmitted our app for review after the update , which could’ve been the issue, will update that

1 Like