# Need help to rollback one account's Webhook App setting using Verification Token

**URL:** <https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489>\
**Category:** API and Webhooks\
**Tags:** webhooks\
**Created:** [January 16, 2023, 4:08am UTC](https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489 "2023-01-16T04:08:29Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ct\_yen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ct_yen/32/20956_2.png) [@ct\_yen](https://devforum.zoom.us/u/ct_yen)\
**Post date:** [January 16, 2023, 4:08am UTC](https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489/1 "2023-01-16T04:08:29Z")

</div>

### Before Creating a New Topic:

_If you’re experiencing unexpected API/Zoom API Events (webhooks) behavior please search the forum with relevant keywords (e.x. error message) and follow the guidance outlined in those posts. Please also leverage the following support links:_

- Zoom Developer Changelog for Dev Product Changes: [https://marketplace.zoom.us/docs/guides/stay-up-to-date/changelog/](https://marketplace.zoom.us/docs/guides/stay-up-to-date/changelog/)
- General Troubleshooting: [Support](https://devsupport.zoom.us/hc/en-us)
- To Submit a Ticket for Unexpected API/Zoom API Events Behavior: [Official Zoom Support | Help Center](https://support.zoom.us/hc/en-us)
- For General & Integrations Related Guidance: [https://community.zoom.com/](https://community.zoom.com/)
- For Troubleshooting Webhooks: [Guide: "We Are Not Receiving Webhooks As Expected" -- Here's What to Do! - #2](https://devforum.zoom.us/t/we-are-not-receiving-webhooks-as-expected-heres-what-to-do/64846/2)

* * *

### Format Your New Topic as Follows:

**API Endpoint(s) and/or Zoom API Event(s)**  
_Link the API endpoint(s) and/orZoom API Event(s) you’re working with to help give context._

**Description**  
_Details on your question, workflow or the problem you’re trying to solve._  
Account ID: 740751  
We would like to test our new code in order to receive events from Zoom Webhook to support both **Verification Token** and **Secret Token**. However, even though, we leave the Secret Token field in blank but we still can’t receive any events from Zoom to the Event notification endpoint URL that we provided in the Webhook App.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/f/c/fc39eb24a584fe714c787b54232882273a0e3e5d.png)

We would like to seek your help, to re-allow this account using the legacy Verification Token to send events to us so we can test our modified code to receive and process events sent by Zoom Webhook, no matter the setting is based on the Verification Token or based on the Secret Token. Thank you.

**Error?**  
_The full error message or issue you are running into, where applicable._

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1. Request URL / Headers **(without credentials or sensitive info like emails, uuid, etc.)** / Body_  
_2. Authentication method or app type_  
_3. Any errors_

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 19, 2023, 3:52pm UTC](https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489/2 "2023-01-19T15:52:19Z")

</div>

Hi @ct_yen  
Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!  
As far as I am aware, you are still receiving the Verification token in the headers when getting events from Zoom, we won’t retire this field until later this year

 ![Screen Shot 2023-01-19 at 10.51.01 AM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/d/4/d481bc2bb073a3aa77c91babab607fa6d226a9a2.png)

[https://marketplace.zoom.us/docs/api-reference/webhook-reference/#webhook-structure](https://marketplace.zoom.us/docs/api-reference/webhook-reference/#webhook-structure)

You should be getting an ‘authorization’ field in your headers, and the value should match your Verification Token.

Let me know if this helps!  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![ct\_yen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ct_yen/32/20956_2.png) [@ct\_yen](https://devforum.zoom.us/u/ct_yen)\
**Post date:** [January 19, 2023, 6:24pm UTC](https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489/3 "2023-01-19T18:24:45Z")

</div>

Hi, Elisa

The problem here is we need to change the Event notification endpoint URL to the testing environment URL, this action stops the Verification Token working because the validation should be done by clicking the “Valid” button. Since the endpint URL changed and the validation is not passed, no events are sent and nothing logs in the Webhook Logs even we tried to do some actions for the subscribed events.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/9/a/9a6eb982535d808111917f50c63289b1af6f2cf5.png)

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 20, 2023, 6:20pm UTC](https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489/4 "2023-01-20T18:20:53Z")

</div>

@ct_yen  
I understand, unfortunately, there is no way to skip this validation URL.  
In order for you to receive zoom events, you must validate your event notification endpoint URL.

We have a sample app that you can use to achieve the Validation URL

> **[GitHub - zoom/webhook-sample-node.js: Receive Zoom Webhooks](https://github.com/zoom/webhook-sample-node.js)**
>
> Receive Zoom Webhooks. Contribute to zoom/webhook-sample-node.js development by creating an account on GitHub.

Let me know if this helps, I am happy to provide you more support on this.  
Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![ct\_yen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ct_yen/32/20956_2.png) [@ct\_yen](https://devforum.zoom.us/u/ct_yen)\
**Post date:** [January 21, 2023, 9:28am UTC](https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489/5 "2023-01-21T09:28:21Z")

</div>

Hi, Elisa

The validation is only for the Secret Token, not for the verification token.

So how can we validate the URL for the verification token format if we would like to use the legacy token for testing?

Best wishes,

CT

Elisa via Zoom Developer Forum \<[notifications@zoomdeveloper.discoursemail.com](mailto:notifications@zoomdeveloper.discoursemail.com)\>於 2023年1月21日 週六，02:30寫道：

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 23, 2023, 10:15pm UTC](https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489/6 "2023-01-23T22:15:26Z")

</div>

@ct_yen  
Hi, I understand now.  
Unfortunately, we can not rollback this new feature.  
But what you can do is validate your endpoint using the secret token and you can continue using the verification token to validate that the event is coming from Zoom.

---

<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:** [January 27, 2024, 1:51pm UTC](https://devforum.zoom.us/t/need-help-to-rollback-one-accounts-webhook-app-setting-using-verification-token/81489/7 "2024-01-27T13:51:31Z")

</div>

Closed on January 27, 2024, 1:51pm UTC

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