Skip to main content
Webhooks are in beta. Event types and payload shapes may still change. We’ll email orgs with active endpoints before any breaking change.
When a sequencer event happens, Origami POSTs a signed JSON envelope to a URL you configure in Settings → Developers → Webhooks.

​
v1 events

Subscribe to specific event types, the sequence.* wildcard, the sequence.connection.* sub-wildcard, or * (everything, including future event types).

​
Delivery guarantees

  • At-least-once delivery. A single event can produce more than one POST under partial failure. Receivers must dedupe on the webhook-id header.
  • Up to 10 attempts following the Standard Webhooks spec retry table — initial + 9 retries with ±15% jitter spanning roughly 75 hours.
  • 410 Gone auto-disables the endpoint per the spec. Re-enable manually from the dashboard.
  • webhook-id is stable across retries. webhook-timestamp is recomputed per attempt — use it for replay protection (±5 min).

​
Signing

Every request carries three headers: Signed string is {webhook-id}.{webhook-timestamp}.{raw-body}, keyed by the base64-decoded bytes of your whsec_… secret (after stripping the whsec_ prefix). This is the canonical Standard Webhooks scheme — verify with Svix’s standardwebhooks SDK or the copy-paste snippets in signature verification (Node, Python, Go, Ruby, Rust, curl + openssl).

​
Next steps