# Webhook always invalid

**URL:** <https://devforum.zoom.us/t/webhook-always-invalid/83315>\
**Category:** API and Webhooks\
**Tags:** webhooks\
**Created:** [February 17, 2023, 11:49am UTC](https://devforum.zoom.us/t/webhook-always-invalid/83315 "2023-02-17T11:49:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![francisco.lopezsanch](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/francisco.lopezsanch/32/45602_2.png) [@francisco.lopezsanch](https://devforum.zoom.us/u/francisco.lopezsanch)\
**Post date:** [February 17, 2023, 11:49am UTC](https://devforum.zoom.us/t/webhook-always-invalid/83315/1 "2023-02-17T11:49:51Z")

</div>

Hi,

I hope you are well.

**API Endpoint(s) and/or Zoom API Event(s)**  
_[Link the API endpoint(s) and/orZoom API Event(s) you’re working with to help give context.](https://marketplace.zoom.us/docs/api-reference/webhook-reference/#webhook-endpoint-requirements)_

**Description**  
_I’m installing an endpoint that meets the requirements above but still I’m getting an unsuccessful validation when using the Zoom Marketplace_

**Error?**  
_Invalid_

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1. Install an agent with [elastic.co](http://elastic.co) fleet in GKE. Create a Service and an Ingress to expose the endpoint wit TLS_  
_2. curl that endpoint from outside the cluster and get back `{"message": "success"}` with 200 OK_  
\*3. Try to validate with Zoom Marketplace and fail \*

I can provide the actual endpoint if necessary but not publicly.

Question: From what I understand the requirement posted above don’t compel my endpoint to give back any specific payload. A 200 OK should suffice. Although in section “Create the response JSON object” of the same page implies the endpoint needs to respond with a specific payload.  
Could you tell me which one is the correct one, please?

Kind regards,

* * *

Fran

---

<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:** [February 17, 2023, 10:04pm UTC](https://devforum.zoom.us/t/webhook-always-invalid/83315/2 "2023-02-17T22:04:37Z")

</div>

Hi @francisco.lopezsanch  
Thanks for reaching out to the Zoom Developer Forum and welcome to our community!

When implementing webhooks, you will need to Validate your endpoint URL before you start receiving events, here is the link to our Docs:

[https://marketplace.zoom.us/docs/api-reference/webhook-reference/#validate-your-webhook-endpoint](https://marketplace.zoom.us/docs/api-reference/webhook-reference/#validate-your-webhook-endpoint)

Sending a 200 ok is not enough, as you will see in the documentation, you need to respond with a JSON object with a key of `"plainToken"` with a value of the `plainToken` from the request body, and a key of `"encryptedToken"` with a value of the hashed `plainToken`.

Here is a link to a sample app that will help you in case you need some reference:

> **[GitHub - zoom/webhook-sample-node.js: Receive Zoom Webhooks](https://github.com/zoom/webhook-sample-node.js)**
>
> Receive Zoom Webhooks. Contribute to zoom/webhook-sample-node.js development by creating an account on GitHub.

Hope this helps,  
Elisa

---

<div class="post-metadata">

**Author:** ![francisco.lopezsanch](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/francisco.lopezsanch/32/45602_2.png) [@francisco.lopezsanch](https://devforum.zoom.us/u/francisco.lopezsanch)\
**Post date:** [February 18, 2023, 10:51am UTC](https://devforum.zoom.us/t/webhook-always-invalid/83315/3 "2023-02-18T10:51:28Z")

</div>

This helps a lot, Elisa. Much appreciated.

---

<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:** [February 22, 2024, 2:28am UTC](https://devforum.zoom.us/t/webhook-always-invalid/83315/4 "2024-02-22T02:28:27Z")

</div>

Closed on February 22, 2024, 2:28am UTC

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