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

# Verifying Callbacks from KORE

When your application receives a callback from KORE, you should verify the the events are coming from KORE.

When KORE responds to the URL you have configured, regardless of how you have configured it (API, UI, Event Streams), KORE signs every Webhook with a `kore-signature` header so you can validate that the sender is KORE and the contents haven't been modified.

KORE signs the Webhook using a secret that you generate through the [developer portal](https://build.korewireless.com/webhook). When you register for the first time, you will not have a Webhook secret for your account, so you need to[ generate your first secret](/developers/how-to/webhooks/validate-webhook-signatures.md#create-your-first-webhook-secret), if you would like to sign your events. You can refer to our [guide](/developers/how-to/webhooks/validate-webhook-signatures.md) for details on validating Webhook signatures.

{% hint style="warning" %}
If no secret is created for your account, KORE will respond with an empty value for the `kore-signature` header.

KORE strongly encourages you to generate a Webhook secret.
{% endhint %}

{% hint style="info" %}
If you generate a new Webhook secret, all new Webhook sent will be using the new secret. Refer to our [guide](/developers/how-to/webhooks/rotate-my-webhook-secret.md) on secret rotation for more details.
{% endhint %}


---

# 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.korewireless.com/developers/webhooks/verifying-callbacks-from-kore.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.