# Deauthorization endpoint and expectation

**URL:** <https://devforum.zoom.us/t/deauthorization-endpoint-and-expectation/43170>\
**Category:** API and Webhooks\
**Created:** [February 12, 2021, 12:21am UTC](https://devforum.zoom.us/t/deauthorization-endpoint-and-expectation/43170 "2021-02-12T00:21:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![bhavik.bhagat](https://avatars.discourse-cdn.com/v4/letter/b/eada6e/32.png) [@bhavik.bhagat](https://devforum.zoom.us/u/bhavik.bhagat)\
**Post date:** [February 18, 2021, 10:15pm UTC](https://devforum.zoom.us/t/deauthorization-endpoint-and-expectation/43170/4 "2021-02-18T22:15:39Z")

</div>

Thanks for the details on what data to remove. For clarity, in the situation where messages stored in the system might contain zoom meeting info, do we have to remove that meeting info from the messages as well?

As for point 2, is the approach mentioned in [https://devforum.zoom.us/t/deauthorization-endpoint-user-identification/33047/7](https://devforum.zoom.us/t/deauthorization-endpoint-user-identification/33047/7) still suggested for our situation?

Also in the case there is any problem with the deauthorization call reaching us, is there any retry logic on Zoom’s end? Do you have any recommendations on retry logic, like how often we should retry to send the confirmation if there is a problem on our end?

---

_[View the full topic](https://devforum.zoom.us/t/deauthorization-endpoint-and-expectation/43170)._