# \[Zoom to Servicenow\] webhook URL Link Validation

**URL:** <https://devforum.zoom.us/t/zoom-to-servicenow-webhook-url-link-validation/98126>\
**Category:** Authentication\
**Tags:** webhooks\
**Created:** [November 9, 2023, 12:25pm UTC](https://devforum.zoom.us/t/zoom-to-servicenow-webhook-url-link-validation/98126 "2023-11-09T12:25:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![joao.salvador](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@joao.salvador](https://devforum.zoom.us/u/joao.salvador)\
**Post date:** [November 9, 2023, 12:25pm UTC](https://devforum.zoom.us/t/zoom-to-servicenow-webhook-url-link-validation/98126/1 "2023-11-09T12:25:23Z")

</div>

I cannot pass the URL webhook validation while setting up the webhook events on the zoom app.

On my zoom app I have:

- **Feature** \> **Event Subscription** \> **Event notification endpoint URL** : [https://COMPANY.service-now.com/api/sn\_zoom\_spoke/zoom\_webhook\_endpoint/webhook](https://COMPANY.service-now.com/api/sn_zoom_spoke/zoom_webhook_endpoint/webhook)

- That is the link of the scripted rest API installed with the zoom spoke plugin on servicenow.

-Added the Zoom APP secret token on the all servicenow Zoom Webhook Registries

Everytime I click on validate I get same error “URL validation failed. Try again later” . There is no extra info about the origin of the error. On servicenow I can see the ping on the API analytics but I cannot add any logs because the scripted REST API is read-only and I cannot change the code.

Can someone from zoom help here? Is the servicenow zoom spoke outdated?

---

<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:** [November 14, 2023, 4:30pm UTC](https://devforum.zoom.us/t/zoom-to-servicenow-webhook-url-link-validation/98126/2 "2023-11-14T16:30:44Z")

</div>

Hi @joao.salvador  
Thanks for reaching out to us!  
Have you been able to troubleshoot this on your end?
