# Deauthorization flow

**URL:** <https://devforum.zoom.us/t/deauthorization-flow/78491>\
**Category:** API and Webhooks\
**Created:** [November 8, 2022, 5:21pm UTC](https://devforum.zoom.us/t/deauthorization-flow/78491 "2022-11-08T17:21:26Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [November 29, 2022, 11:14pm UTC](https://devforum.zoom.us/t/deauthorization-flow/78491/8 "2022-11-29T23:14:57Z")

</div>

Hi @rmjuarez12 ,

Currently, best practice is to grab the access token during authorization. See below for outlined process:

> [@Deauthorization endpoint user identification](https://devforum.zoom.us/t/deauthorization-endpoint-user-identification/33047/6):
>
> Hey @dave2 , Thank you for clarifying, and my sincere apologies for not catching your concern from the onset. I understand now that you’re essentially looking to make this connection with a customer’s Account ID as soon as they authorize/install the app, so that you can then have this record on your end when they uninstall (but please correct me if I’m misunderstanding). While there’s not a completely straight forward way to track this, there is a suggestion I can make: When an account author…

---

_[View the full topic](https://devforum.zoom.us/t/deauthorization-flow/78491)._