# Oauth verification token for Deauthorization

**URL:** <https://devforum.zoom.us/t/oauth-verification-token-for-deauthorization/56816>\
**Category:** API and Webhooks\
**Tags:** faq\
**Created:** [September 2, 2021, 4:09am UTC](https://devforum.zoom.us/t/oauth-verification-token-for-deauthorization/56816 "2021-09-02T04:09:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vince246](https://avatars.discourse-cdn.com/v4/letter/v/3bc359/32.png) [@vince246](https://devforum.zoom.us/u/vince246)\
**Post date:** [September 2, 2021, 4:09am UTC](https://devforum.zoom.us/t/oauth-verification-token-for-deauthorization/56816/1 "2021-09-02T04:09:01Z")

</div>

Hi Zoom master,

**Description**  
Verification Token is now show in App **management page** → **feature** tab only when I created a event subscriptions. But before this, it is always show in feature tab. We use this token to verify deauthorize event when user uninstall app.

I want to confirm that is the Verification Token still contained in deauthorize event request header. And is it always same with the Verification Token shows in **feature** tab after I set event subscriptions？

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
OAuth

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [September 7, 2021, 10:57pm UTC](https://devforum.zoom.us/t/oauth-verification-token-for-deauthorization/56816/2 "2021-09-07T22:57:35Z")

</div>

Hey @vince246,

Thank you for reaching out to the Zoom Developer Forum. Yes, the verification token sent in the Deauthorization post request should still include the verification token from the webhook feature tab.

Let me know if that helps.

Thanks,  
Max

---

<div class="post-metadata">

**Author:** ![vince246](https://avatars.discourse-cdn.com/v4/letter/v/3bc359/32.png) [@vince246](https://devforum.zoom.us/u/vince246)\
**Post date:** [September 8, 2021, 6:08am UTC](https://devforum.zoom.us/t/oauth-verification-token-for-deauthorization/56816/3 "2021-09-08T06:08:00Z")

</div>

Hi MaxM  
I got it. Thanks for your confirmation!

---

<div class="post-metadata">

**Author:** ![BobT](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bobt/32/17873_2.png) [@BobT](https://devforum.zoom.us/u/BobT)\
**Post date:** [September 9, 2021, 9:01pm UTC](https://devforum.zoom.us/t/oauth-verification-token-for-deauthorization/56816/4 "2021-09-09T21:01:02Z")

</div>

I also don’t see a verification token displayed on the Feature tab when I only have a deauthorization URL set but no other event subscriptions. If I add some other random event subscription, it will generate a verification token, but if I remove it, the token disappears again. I don’t really want to leave my app subscribed to events that I don’t need just to be able to verify the deauthorization event.

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [September 14, 2021, 10:30pm UTC](https://devforum.zoom.us/t/oauth-verification-token-for-deauthorization/56816/5 "2021-09-14T22:30:51Z")

</div>

Hey @BobT,

You’re right in identifying that this is a user experience flaw on our end. I’ll work with our team to make sure this is fixed. For the time being, you will want to create an event subscription even if you’re not consuming the events that are generated.

Thanks,  
Max

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [October 15, 2021, 8:31am UTC](https://devforum.zoom.us/t/oauth-verification-token-for-deauthorization/56816/6 "2021-10-15T08:31:08Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
