# Invalid TLS cert from Zoom webhooks

**URL:** <https://devforum.zoom.us/t/invalid-tls-cert-from-zoom-webhooks/94552>\
**Category:** API and Webhooks\
**Created:** [September 6, 2023, 1:48pm UTC](https://devforum.zoom.us/t/invalid-tls-cert-from-zoom-webhooks/94552 "2023-09-06T13:48:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![brawnyplatypus](https://avatars.discourse-cdn.com/v4/letter/b/5fc32e/32.png) [@brawnyplatypus](https://devforum.zoom.us/u/brawnyplatypus)\
**Post date:** [September 6, 2023, 1:48pm UTC](https://devforum.zoom.us/t/invalid-tls-cert-from-zoom-webhooks/94552/1 "2023-09-06T13:48:06Z")

</div>

We are using an updated version of the Splunk Connect add-on for zoom that uses the Zoom secret to verify the webhooks that are being sent.

The certificate in use matches the webhook URL from the zoom side. We are a bit at a loss since everything seems to match up with the requirements from both the Splunk add-on and Zoom. We are using a Sectigo (Comodo) certificate as I have seen other posts where the particular certificate/vendor wasn’t supported so not sure if that is a culprit but there is not a list of supported cert vendors that I can find publicly.

---

<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:** [September 8, 2023, 3:06pm UTC](https://devforum.zoom.us/t/invalid-tls-cert-from-zoom-webhooks/94552/2 "2023-09-08T15:06:39Z")

</div>

Hi @brawnyplatypus  
Thanks for reaching out to us and welcome to our community, I am happy to help here!  
Here is a link to our Docs where you will find some of the endpoint requirements:

> **[Using webhooks](https://developers.zoom.us/docs/api/rest/webhook-reference/#webhook-endpoint-requirements)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

---

<div class="post-metadata">

**Author:** ![brawnyplatypus](https://avatars.discourse-cdn.com/v4/letter/b/5fc32e/32.png) [@brawnyplatypus](https://devforum.zoom.us/u/brawnyplatypus)\
**Post date:** [September 8, 2023, 4:12pm UTC](https://devforum.zoom.us/t/invalid-tls-cert-from-zoom-webhooks/94552/3 "2023-09-08T16:12:12Z")

</div>

Hey @elisa.zoom ,

Appreciate the follow up here I have reviewed those requirements and on paper the application meets those requirements and I need more information on what the issue could be if whilst using a valid certificate from a publicly trusted CA, why are we still getting the invalid TLS cert

---

<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:** [September 8, 2023, 4:34pm UTC](https://devforum.zoom.us/t/invalid-tls-cert-from-zoom-webhooks/94552/4 "2023-09-08T16:34:31Z")

</div>

Thanks for the follow up @brawnyplatypus  
I will send you a private message with some follow-up questions

---

<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:** [September 11, 2024, 8:10am UTC](https://devforum.zoom.us/t/invalid-tls-cert-from-zoom-webhooks/94552/5 "2024-09-11T08:10:33Z")

</div>

Closed on September 11, 2024, 8:10am UTC

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