# Webhook URL validation is not working. Please help

**URL:** <https://devforum.zoom.us/t/webhook-url-validation-is-not-working-please-help/132158>\
**Category:** Meetings\
**Tags:** webhooks\
**Created:** [April 30, 2025, 5:44am UTC](https://devforum.zoom.us/t/webhook-url-validation-is-not-working-please-help/132158 "2025-04-30T05:44:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![user65](https://avatars.discourse-cdn.com/v4/letter/u/ea5d25/32.png) [@user65](https://devforum.zoom.us/u/user65)\
**Post date:** [April 30, 2025, 5:44am UTC](https://devforum.zoom.us/t/webhook-url-validation-is-not-working-please-help/132158/1 "2025-04-30T05:44:45Z")

</div>

I checked the connection using `curl` and asked ChatGPT about the result. Here’s the response I received:

Why on earth isn’t it working? Please help me.

The Zoom Webhook URL is registered with the correct domain and path.

- Confirmed that the URL includes `https://`
- Ensured there is no unnecessary trailing slash `/` at the end of the domain
- Verified that the Webhook URL actually exists on the server and returns a 200 OK response
- Added to the domain whitelist if necessary"

| Item | Status | Description |
| --- | --- | --- |
| ✅ Server Reach | Zoom can connect to a public IP accessible server successfully | |
| ✅ HTTPS Cert | TLS handshake succeeded, SSL certificate applied correctly | |
| ✅ HTTP Response | Received HTTP/1.1 200 OK | |
| ✅ Response Format | The structure is correct: { “plainToken”: “…”, “encryptedToken”: “…” } | |
| ✅ Content-Type | Confirmed as application/json | " |

Please help me.

---

<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:** [May 1, 2025, 1:10pm UTC](https://devforum.zoom.us/t/webhook-url-validation-is-not-working-please-help/132158/2 "2025-05-01T13:10:38Z")

</div>

Hi @user65  
Thanks for reaching ou to us, I am happy to help here!  
Are you receiving the “endpoint.url\_validation” event when triggering the validation in the Web portal??