# Data Compliance API - Deauthorization Endpoint URL

**URL:** <https://devforum.zoom.us/t/data-compliance-api-deauthorization-endpoint-url/3870>\
**Category:** API and Webhooks\
**Created:** [April 5, 2019, 5:17pm UTC](https://devforum.zoom.us/t/data-compliance-api-deauthorization-endpoint-url/3870 "2019-04-05T17:17:11Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![zeus](https://avatars.discourse-cdn.com/v4/letter/z/a4c791/32.png) [@zeus](https://devforum.zoom.us/u/zeus)\
**Post date:** [October 7, 2019, 6:24pm UTC](https://devforum.zoom.us/t/data-compliance-api-deauthorization-endpoint-url/3870/18 "2019-10-07T18:24:51Z")

</div>

We are facing the same issue as raise by the OP.

Has there been an update to the endpoints/interfaces to allow applications that only need `meeting` related endpoints to be able to determine which account a deauthorization event notification refers to?

If not, does this mean the deauthorization event handling is not required for compliance?

Are there any plans to include the account\_id along with the payload that returns the refresh token during the oAuth process? Doing so would allow us to store the account\_id along with the credentials which would enable us to lookup the account referenced in a future deauthorization notification.

---

_[View the full topic](https://devforum.zoom.us/t/data-compliance-api-deauthorization-endpoint-url/3870)._