> For the complete documentation index, see [llms.txt](https://docs.conscent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.conscent.ai/old-webhooks/how-to-validate-webhooks.md).

# How to validate Webhooks?

When your webhook `secret` is set, Conscent uses it to create a hash signature with each payload. This hash signature is passed with each request under the `X-Conscent-Signature` header that you need to validate at your end.

{% tabs %}
{% tab title="Nodejs" %}

```javascript
var crypto = require('crypto');

var hmac = crypto.createHmac('sha256', '<WEBHOOK_SECRET>');

//passing the data to be hashed
rawBody = '<RAW_BODY_OF_REQUEST>';
signature = hmac.update(req.body).digest('hex');

//Printing the output on the console
console.log('hmac : ' + signature);

// NOTE: try matching `signature` with request header `x-conscent-signature`
```

{% endtab %}
{% endtabs %}

> ```
> Do Not Parse or Cast the Webhook Request Body
>
> While generating the signature at your end, ensure that the webhook body passed as an argument is the raw webhook request body. Do not parse or cast the webhook request body.
> ```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.conscent.ai/old-webhooks/how-to-validate-webhooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.