> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/xclaim/webhooks/verifying-signatures.md).

# Verifying signatures

This is optional, but highly recommended.

Signatures are created using `HMAC` and the `sha256` hash, and passed in the `XClaim-Signature` header of the webhook request (ie. when sent to your system).

The signature string found inside the `XClaim-Signature` header should be:

`sha256=<signature>`

Suppose that the body of the incoming webhook request is `requestBody` and the signature key you specified is `key`, and there exists a function as this:

`HMAC_SHA256 ( data, signatureKey )`

The `<signature>` string can be generated using the following simple pseudocode algorithm;

`HMAC_SHA256(requestBody, key)`

Once you have generated the signature on your end, check that it matches the signature in the webhook received.


---

# 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://partner-docs.covergenius.com/xclaim/webhooks/verifying-signatures.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.