> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developer.wamo.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developer.wamo.io/_mcp/server.

# Webhooks overview

Webhooks let your systems react to activity in your wamo account as it happens. Instead of polling for changes, you register an endpoint and wamo sends an HTTP `POST` request to it each time a subscribed event occurs.

## How it works

1. You create a webhook endpoint in the wamo web app and choose which events to subscribe to.
2. When a subscribed event occurs, wamo sends a JSON payload to your endpoint.
3. Your endpoint verifies the signature, processes the event, and responds with a `2xx` status code.

wamo webhooks follow the [Standard Webhooks](https://www.standardwebhooks.com) specification for the payload format, the request headers, and the signature scheme. You can verify requests with any [Standard Webhooks library](https://github.com/standard-webhooks/standard-webhooks/tree/main/libraries).

## Available events

| Event                        | Description                                    |
| ---------------------------- | ---------------------------------------------- |
| `transaction.status_changed` | Sent when the status of a transaction changes. |

See [Events and payloads](/webhooks/events) for the full payload reference.

## Next steps

#### [Manage endpoints](/webhooks/manage-endpoints)

Create endpoints, subscribe to events, and find your signing secret.

#### [Events and payloads](/webhooks/events)

See every event type and the data it contains.

#### [Verify and handle webhooks](/webhooks/verify-signatures)

Confirm requests come from wamo and handle retries safely.