Notifications

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

notifications

Full steps, failures, and recovery live on the workflow page. This page lists tools and API references.

Why agents use it

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

Example: subscribe (HTTP)

A representative invocation. Drop this into an MCP-capable agent (Claude Desktop, Claude Code, Cursor, Windsurf) after the Tatum MCP server is configured.

subscribe (HTTP)

// Webhook subscription via Tatum HTTP API
POST https://api.tatum.io/v4/subscription
x-api-key: $TATUM_API_KEY
{
  "type": "ADDRESS_EVENT",
  "attr": { "chain": "ethereum-mainnet",
            "address": "0xab58...c9b",
            "url": "https://your-app.example/webhook" }
}

OpenAPI references

https://docs.tatum.io/openapi/notifications-1.json (Subscriptions)

Notes

Canonical recipe

No MCP tools for subscriptions today. Use the HTTP procedure in 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.