> 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/overview.md).

# Overview

Webhooks are sent to every receiving url that is specified in the "webhooks" key on the claim creation request - you can check the "create a new claim" request in these docs for an example of how to do this. It is completely optional, so you can specify no webhook receivers, one or as many as you like (for example, if you have multiple separate parts of your ecosystem which you would like to receive these webhooks).

Inside the webhooks array of the aforementioned create claim request, you can specify receivers inside json objects. Each object should have a "url" and "key" property. The URL property specifies the URL that the webhook will be sent to, and the key is any string you choose, which is used to create a signature for each webhook sent (to the URL specified in the same webhook object), which will allow you to verify the authenticity of the sender (ie. XClaim).

For example, consider this:

```
    {
      "url": "http://some.site",
      "key": "abc123"
    }
```

Webhooks will be sent to "<http://some.site">, and the signature created using the key "abc123".


---

# 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/overview.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.