# Error verifying during webhook verification

**URL:** <https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131>\
**Category:** API and Webhooks\
**Tags:** webhooks\
**Created:** [January 19, 2024, 1:33am UTC](https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131 "2024-01-19T01:33:11Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![stanley1](https://avatars.discourse-cdn.com/v4/letter/s/2bfe46/32.png) [@stanley1](https://devforum.zoom.us/u/stanley1)\
**Post date:** [January 19, 2024, 1:33am UTC](https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131/1 "2024-01-19T01:33:11Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
**[Webhook verification](https://developers.zoom.us/docs/api/rest/webhook-reference/)**

**Description**  
So I was trying to set up a webhook to my django application inside my docker container. I was also using ngrok to create a public URL to connect to my docker instance. When I reach the [verification](https://developers.zoom.us/docs/api/rest/webhook-reference/) step, and try to verify the url, I keep getting the error `URL validation failed. Try again later`. When I check the ngrok instance, I don’t see any requests coming in. Just to confirm that ngrok was working, I used postman to create a post request and was able to see my own request come in. As another option, I tried using my staging environment to test the verification process as well, and still had the same error.

**Error message**  
URL validation failed. Try again later.

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1. Create a new endpoint for receiving zoom webhooks_  
_2. Start a backend API inside a docker container_  
_3. Start a ngrok instance exposing the local docker image port_  
_4. On zoom dashboard, try to verify the webhook URL_  
_5. See that the error on Zoom dashboard_

---

<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:** [January 19, 2024, 2:38am UTC](https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131/2 "2024-01-19T02:38:11Z")

</div>

Hi @stanley1 ,

Which of the verification options from our docs are you using? Can you walk us how to reproduce?

---

<div class="post-metadata">

**Author:** ![stanley1](https://avatars.discourse-cdn.com/v4/letter/s/2bfe46/32.png) [@stanley1](https://devforum.zoom.us/u/stanley1)\
**Post date:** [January 19, 2024, 2:18pm UTC](https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131/4 "2024-01-19T14:18:06Z")

</div>

Hi @gianni.zoom,

I was using the `Default Header Provided by Zoom` option.

To reproduce it:  
_1. Create a new endpoint for receiving zoom webhooks_  
_2. Add webhook secrets token to the platform_  
_3. Start a backend API inside a docker container_  
_4. Start a ngrok instance exposing the local docker image port_  
_5. On zoom dashboard, try to verify the webhook URL_  
_6. See the error, “URL validation failed, Try again later.” on Zoom webhook verification dashboard_

I appreciate the help!

---

<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:** [January 19, 2024, 5:00pm UTC](https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131/5 "2024-01-19T17:00:56Z")

</div>

Hi @stanley1 ,

Please respond to my private message with the following:

- client id of app
- developer id
- endpoint url
- recording of undergoing [the verification process](https://developers.zoom.us/docs/api/rest/webhook-reference/#verify-with-zooms-header) and subsequent error

---

<div class="post-metadata">

**Author:** ![pragyansh](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@pragyansh](https://devforum.zoom.us/u/pragyansh)\
**Post date:** [January 22, 2024, 5:59am UTC](https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131/6 "2024-01-22T05:59:27Z")

</div>

Hello @gianni.zoom, I’m encountering the identical error message: **“URL validation failed. Try again later.”**

I’ve set up a legacy app and configured a few event subscriptions. I’m attempting to test the events locally using ngrok as the Event notification endpoint URL. However, the URL validation is unsuccessful, and I’m also experiencing a **403 Forbidden** error for the subscribed events.

Would you mind assisting me in getting started? Your help is much appreciated. Thank you!

---

<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:** [January 26, 2024, 4:56pm UTC](https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131/7 "2024-01-26T16:56:20Z")

</div>

Hi @pragyansh ,

Of course! Can you try running through set up with our sample app?

> **[GitHub - zoom/zoom-webhook-verification-headers: Custom Headers (Basic, Token...](https://github.com/zoom/zoom-webhook-verification-headers)**
>
> Custom Headers (Basic, Token and custom header) authorization & Zoom Webhook Validation with Express.js Server - GitHub - zoom/zoom-webhook-verification-headers: Custom Headers (Basic, Token an...

If it fails, please let me know I’ll reach back out requesting the same info asked from the developer above you.

---

<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 29, 2025, 8:33am UTC](https://devforum.zoom.us/t/error-verifying-during-webhook-verification/102131/8 "2025-01-29T08:33:08Z")

</div>

Closed on January 29, 2025, 8:33am UTC

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