Skip to main content
Token operations publish typed token.* webhook events alongside the existing transaction.* lifecycle events. Both streams are useful: token.* carries token-specific context (token ID, amount, recipient, role, contract address); transaction.* carries low-level transaction lifecycle.

Delivery semantics

  • HMAC-SHA256 signed with the per-endpoint secret. See Webhooks.
  • At-least-once delivery; treat your handler as idempotent (event.id is unique).
  • Retried with exponential backoff on non-2xx responses.

Event envelope

Event catalog

Naming convention

Event names follow the existing Qustody convention entity.verb_past. The token.* events match the same shape as transaction.created, deposit.detected, etc.

Sample payloads

token.deployed

token.role_granted

token.operation_failed

Subscribing

Register a webhook endpoint with a filter: