Why the deauthorization endpoint url does not work

[henry1 (Henry)]

Hi Support Team:
I created a Oauth app and set the deauthorization endpoint link for it. While, after user uninstall the oauth app, i can not receive any event notification at that endpoint url. What should i do further?

Thanks so much!

[DeveloperBot]

Hey @henry1

Thanks for posting on the Zoom Devforum! I am still learning, but I will try my best to help answer your question.

Checkout these related threads that may have the answer you are looking for:

Deauthorization API - not webhook

Hi, When a user requests to disconnect my app, or for example, my app would like to disconnect inactive users (to avoid extraneous webhooks) - I need some deauthorization API call for Zoom. Is there a app deauthorization API? (i.e: not the webhook callback when the user deauthorizes on Zoom end) Thanks, Alon

Deauthorization API

I am trying to figure out how to comply with your deauthorization webhook call (https://marketplace.zoom.us/docs/api-reference/webhook-reference/app-events). I am currently only storing the tokens that I receive when authorizing, so I can’t identify the connection from any of the data that are included in the payload here. I do make calls to the users endpoint, so I guess I might have the user id of the person who created the connection but I am not sure how to determine this. Do I need to make…

If these threads did not help, please let us know by replying back here and someone from the Developer Relations team will get back to you shortly.

Thanks,
DeveloperBot

[henry1 (Henry)]

Sorry, I can not get help from the above threads. The issue i encountered is that, i can not get the deauthorization event notification from the deauthorization endpoint url which is set in the Oauth app. BTW, the oauth app is not published yet. fyi.

Thanks

[henry1 (Henry)]

Hello,
Anyone can help advise it?

Thanks

[will.zoom (Will)]

Hey @henry1,

Thanks for reaching out about this—as it turns out, in order to get the de-authorization webhook event to fire, you’ll need to ensure you’re testing with the production version of the app (you can find the install link for this under ‘Publishable URL’ on the Submit page of your app in the marketplace.

This post provides some more in-depth detail:

Data Compliance API - Deauthorization Endpoint URL

Hi Tommy, Thanks! I still don’t see my app’s Verification Token: I’m working in PHP so I would expect to find it (I think!) in the incoming request’s headers (as obtained from PHP’s apache_request_headers() function, or directly in $_SERVER['HTTP_{uppercaseHeaderName}'], i.e. $_SERVER['HTTP_AUTHENTICATION'] in this case). Even if I’m looking it up in the wrong way I would expect to see that token value present SOMEWHERE in the payload, but I don’t. Perhaps this is because my app is still not…

Can you let me know if this clears things up?

Best,
Will