# Not receiving webhooks from all webinars

**URL:** <https://devforum.zoom.us/t/not-receiving-webhooks-from-all-webinars/98319>\
**Category:** API and Webhooks\
**Created:** [November 13, 2023, 9:50pm UTC](https://devforum.zoom.us/t/not-receiving-webhooks-from-all-webinars/98319 "2023-11-13T21:50:54Z")\
**Posts on this page:** 1\
**Showing post:** 12

<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:** [December 7, 2023, 6:08pm UTC](https://devforum.zoom.us/t/not-receiving-webhooks-from-all-webinars/98319/12 "2023-12-07T18:08:42Z")

</div>

Developer was receiving timeouts and 401s for certain webhooks.

Developer shared in response that infrastructure team was doing maintenance on their test environment around that time which could be why there were timeouts. That should be resolved now.

As for the 401s, developer suspected that all webinars giving 401s in webhook response have special character in the title. They think that this special character (long dash) is causing our systems to generate different hashes, which is breaking the webhook verification.

Could be related:

> [@Unexpected hashing algorithm used in the recording checksum](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/7):
>
> Hi @franciscocastanheira , Upon further investigation, I learned that we use MD5 when the file needs to be uploaded in parts to the file server. A formal request has been made to use the same checksum formula (ZOOM-587214). Temp workaround: If the length of the token is equal to 32, please use the MD5 algorithm for verification. If the length of the token is equal to 64, please use the SHA256 algorithm for verification. Does this help?

---

_[View the full topic](https://devforum.zoom.us/t/not-receiving-webhooks-from-all-webinars/98319)._
