outgoing_webhook blocks, and monitor notifications) carries a Sixtyfour-Signature header. Without a secret, deliveries are unsigned.
Manage the secret
Manage the secret on the Signing Secret card under Webhooks in Settings. Every member can see whether a secret exists and when it was created; only organization admins and owners can create, roll or revoke it.Signature format
The body is compact JSON. Compute the HMAC over the exact bytes you received, before any JSON parsing or re-serialization.
Verify signatures
- Read the raw request body.
- Parse
Sixtyfour-Signatureintotand everyv1. - Reject the request if
tis more than 5 minutes from your clock. - Compute
HMAC-SHA256(secret, f"{t}." + raw_body)as hex. - Accept if it matches any
v1with a constant-time comparison.
rawBody must be the unparsed request body, for example from express.raw({ type: "application/json" }).
Behavior
- While a signing secret is active, Sixtyfour never sends an unsigned delivery; a delivery it cannot sign fails.
- The timestamp is inside the signed payload, so an old delivery cannot be replayed with a fresh
t. Dedupe deliveries as the receiver checklist describes.