> 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/kore/developers/how-to/webhooks/test-and-troubleshoot.md).

# Test and Troubleshoot my Webhook Integration

You can test receiving callbacks from KORE by sending test data to your URL. 

{% hint style="info" %}
The same [Webhook secret](https://docs.korewireless.com/kore/developers/how-to/webhooks/pages/XWp2p7QxAVuAnaKMj34q#id-1.-securing-your-webhook-secret-generation) is used to sign events sent by KORE's event stream product.
{% endhint %}

## Create a Webhook Destination on KORE Event Streams

The first step is to create a webhook destination that defines where KORE should send events. 

{% hint style="success" %}
Even though you may not use the event stream product, you can leverage it to send test events.
{% endhint %}

## Send Test Events to the Webhook Destination

Once a Webhook destination has been set up, you can [send test events](/kore/developers/how-to/event-streams/test-my-destination.md#send-test-events-to-the-destination).

{% hint style="info" %}
There is no limit to how many test events you send. 
{% endhint %}

## Verify Test Events

If the test events are sent successfully, you can review the guide on [verifying the event](/kore/developers/how-to/event-streams/test-my-destination.md#verify-webhook-test-events).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.korewireless.com/kore/developers/how-to/webhooks/test-and-troubleshoot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.