> For the complete documentation index, see [llms.txt](https://developers.gurupay.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.gurupay.eu/webhooks/webhook-statuses.md).

# Webhook statuses

Available statuses for sent webhooks.

Every webhook sent by the Guru Pay system has an associated delivery status that reflects the current state of the delivery attempt. These statuses help developers monitor and debug webhook itnegrations directly from the Developer Dashboard.

<figure><img src="https://1845395637-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGiXLfB5h7Eg5qqGCM2QR%2Fuploads%2FdoVxjPggI9uyEpVc56W8%2Fimage.png?alt=media&amp;token=7afeb328-f783-4456-bef0-c7c90e910e12" alt=""><figcaption><p>Flow of webhook statuses</p></figcaption></figure>

## Statuses Explained

| Status     | Description                                                                                                                                   |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| processing | The wehook has ben generated and is currently being processed for delivery.                                                                   |
| retry      | The previous delivery attempt failed (e.g., network issue or non-2xx response). The system will automatically retry.                          |
| delivered  | The webhook has successfully delivered and acknowledged by your server with a `2xx` HTTP response.                                            |
| error      | All retry attempts failed. The webhook is marked as failed and will not be retried automatically. You should contact us in order to retry it. |


---

# 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://developers.gurupay.eu/webhooks/webhook-statuses.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.