# Why the deauthorization endpoint url does not work

**URL:** <https://devforum.zoom.us/t/why-the-deauthorization-endpoint-url-does-not-work/28877>\
**Category:** App Marketplace\
**Created:** [September 2, 2020, 10:00am UTC](https://devforum.zoom.us/t/why-the-deauthorization-endpoint-url-does-not-work/28877 "2020-09-02T10:00:34Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [September 4, 2020, 8:14pm UTC](https://devforum.zoom.us/t/why-the-deauthorization-endpoint-url-does-not-work/28877/5 "2020-09-04T20:14:41Z")

</div>

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](https://devforum.zoom.us/t/data-compliance-api-deauthorization-endpoint-url/3870/14):
>
> 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

---

_[View the full topic](https://devforum.zoom.us/t/why-the-deauthorization-endpoint-url-does-not-work/28877)._