> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/data-and-integrations/webhooks/configuring-the-webhook.md). # Configuring the Webhook The most important field you need to enter is the webhook URL - this is the remote server address you want to ping when the trigger entity/event condition is met. As well as the URL, you also have the option to set up any number of custom headers in the request. These would most often be used for authentication against the remote API, for example: `Authorization: Bearer 238ujdfnd8gudjfdnfg` ### Built-In Headers Note that Pakk, by default and without you having to specify them, will send a number of additional headers with the request: * `User-Agent: Pakk-Webhook-Tester` * `X-Pakk-WebhookID: xxxxxxxxxxxxxxxxxxxxxxxxx` (actually sends the unique ID of the webhook) * `X-Pakk-Webhook-TriggerEvent: Create/Edit` * `X-Pakk-Webhook-TriggerEntity: entityName` * `X-Pakk-Webhook-Signature: xxxxxxxxxxxxxxxxxxxxx` (sends the verification signature) You can use the `X-Pakk-WebhookID` as a simple method to secure the API endpoint on the remote server since the webhook unique identifier won't be known to any external systems and so functions as a quasi API key. If you ever need to 'revoke' the key, you can simple inactivate that webhook, duplicate it, and you'll have a new one with a different ID. We recommend, however, that you implement webhook signature verification on your server, if you have code control over the endpoint. --- # 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.pakk.io/data-and-integrations/webhooks/configuring-the-webhook.md?ask=&goal= ``` `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.