> For the complete documentation index, see [llms.txt](https://docs.aquanow.io/pay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquanow.io/pay/webhooks/subscribing-to-webhooks.md). # Subscribing to Webhooks Webhook callbacks for clients that want event-driven updates The Webhooks menu allows you to enter a webhook to use with our API.

You can add webhooks for Payments, Transactions, and Invoicing

To add your webhook, type in your webhook URL and use the check boxes to select what types of messages you would like to receive. Some selections are already set and not configurable.

Transactions Webhook Example

Once a webhook is added, several actions become available:

FAILED and UNCONFIRMED become available for selection

You may send a test message, edit the webhook's URL, or delete it entirely.

Send a test

Edit URL

Delete URL

--- # 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.aquanow.io/pay/webhooks/subscribing-to-webhooks.md?ask=&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.