Operate
Contract designedWebhooks
Signed, replay-resistant, retryable domain and lifecycle events.
Pre-alpha documentation boundary
Examples describe accepted contracts unless explicitly marked implemented. They do not imply a deployed API, SDK, signer, or production environment.
Examples
Delivery contract#
Every delivery includes a unique event ID, timestamp, key ID, and signature over the exact timestamped body. Consumers reject stale timestamps and deduplicate event IDs.
- Exponential backoff
- Dead-letter handling
- Secret overlap during rotation
- Test delivery and payload inspection
Initial event families#
User, identity, wallet, transaction, policy, session, application, and security events use versioned names such as transaction.confirmed and policy.denied.
Implementation status
Engineering status Review the engineering-readiness snapshot for current service boundaries. Contact the team before integrating a capability that remains gated.