> For the complete documentation index, see [llms.txt](https://docs.apono.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apono.io/docs/webhook-integrations/troubleshoot-a-webhook.md).

# Troubleshoot a webhook

Learn how to troubleshoot a webhook

If there are issues with the webhook URL or the body template, your webhook test will return an errors. The following sections explain how to troubleshoot these errors.

### Invalid host

This error occurs when the webhook URL has been entered into the Apono UI incorrectly with additional or missing characters.

Use the following steps to correct this error:

1. Examine the webhook URL entered in the **URL** field.
2. Correct the URL.
3. Click **Test** to test the webhook again.

***

### Invalid body template

This error occurs when the payload body for your webhook has been entered into the Apono UI with an incorrect syntax.

Use the following steps to correct this error:

1. In the **Body Template** field, check the syntax of the JSON body and the syntax of Handlebars expressions.
2. Make any corrections.
3. Click **Test** to test the webhook again.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apono.io/docs/webhook-integrations/troubleshoot-a-webhook.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 `build a script that syncs our docs to a CMS` 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.