> For the complete documentation index, see [llms.txt](https://guide.xs2a.com/xs2a/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.xs2a.com/xs2a/integration-cs/additional-guides/webhooks.md).

# Webhooks

Our system differentiates between different events that occur within the use of our interfaces and system. A common example of such an event is the successful creation of a transaction via the corresponding interface within the respective provider account. The available events can be queried as a list filtered using the interface. A detailed query for a special event is also possible. Further information on the individual information requests and the scope can be found in the interface documentation. Further details regarding the transmitted information, signature and error handling can also be found in the interface documentation.

{% embed url="<https://docs.xs2a.com/swagger/#tag/Events-and-Webhook>" %}

Similarly, events are transmitted via Webhook. For this, the necessary URLs can be managed via the customer cockpit. Details can be found in the chapter "Customer Cockpit / Creating Webhooks".


---

# 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://guide.xs2a.com/xs2a/integration-cs/additional-guides/webhooks.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.