> For the complete documentation index, see [llms.txt](https://docs.useglade.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useglade.org/agents/live-events.md).

# Live events

Whenever a payment touches your account or one of its agents, you hear about it straight away. Dashboards, parent apps and monitoring tools can stay current from the moment money moves, without polling and without a delay.

## Subscribing to events

You can create a subscription under **Dashboard → Developer → Webhooks** or through the API. Either way, the steps are the same:

1. Give Glade an HTTPS endpoint that accepts `POST` requests.
2. Choose which event types should be sent to it.
3. Save the signing secret. Glade signs every payload with an HMAC using this secret, and you will only see it once, at the moment the subscription is created.

Before your code acts on a request body, check the `X-Glade-Signature` header against that secret.

## Events you can receive

| Event                                | Sent when                                                  |
| ------------------------------------ | ---------------------------------------------------------- |
| `transfer.initiated`                 | A payment has been submitted and is awaiting confirmation. |
| `transfer.confirmed`                 | A payment has settled on-chain.                            |
| `transfer.failed`                    | A payment did not settle.                                  |
| `agent.transaction.pending_approval` | An agent's payment exceeded its approval threshold.        |
| `agent.transaction.approved`         | Someone approved a held agent payment.                     |
| `agent.transaction.rejected`         | Someone declined a held agent payment.                     |
| `agent.policy.updated`               | The spend policy on one of your agents changed.            |

## What a payload looks like


---

# 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.useglade.org/agents/live-events.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.