# Notifications

> Webhook-based subscriptions for incoming transactions, contract events, and chain activity.

- canonical: <https://ai.tatum.io/capabilities/notifications>
- category: `notifications`
- risk: `low`

## Canonical recipe

End-to-end procedure: [incoming-payment-monitor](https://ai.tatum.io/workflows/incoming-payment-monitor). This capability page is the hub (tools, OpenAPI, examples).

## Why agents use it

Push beats polling. Agents react to chain events without burning RPC quota.

## OpenAPI references

- `/openapi/notifications.json` (tag: `Subscriptions`)

## Docs

- <https://docs.tatum.io>

## Notes

## Canonical recipe

No MCP tools for subscriptions today. Use the HTTP procedure in [Incoming Payment Monitor](/workflows/incoming-payment-monitor). Create a webhook subscription, verify HMAC signatures, handle events idempotently.

## Risk

Public webhook endpoints must validate the HMAC signature. Idempotency is the agent's responsibility.