Webhooks & Events
Consume versioned Torq state changes through signed webhooks, resumable streams, and polling.
Torq emits public Developer Preview events only after the canonical state transaction commits. You can receive them through signed webhooks, authenticated WebSocket streams, or retained event polling.
Delivery model
- Webhook delivery is at least once. Deduplicate by
deliveryIdandeventId. - Ordering is preserved per entity key, not across unrelated entities.
- Retry exhaustion moves a delivery to a dead-letter path; replay is retained for 30 days where the governed event plane is available.
- A stream cursor resumes retained events. Poll
GET /v1/eventswith a server-side secret key when a stream is unavailable.
Verify before acting
Verify the Torq-Signature against the exact raw request bytes before JSON parsing changes the
body. Reject an old timestamp, use a constant-time comparison, and store the event ID before any
side effect. Return a 2xx response only after the message has been accepted durably.
Read Webhooks and WebSockets for the signing input, headers, and stream behavior. The catalog below is generated from the active capability registry and lists only the event types in this Developer Preview.