Signed webhooks
Verify receivers, authenticate event bodies, and safely handle retries.
Workspace administrators manage webhooks. Add a public HTTPS receiver, choose events, and copy the signing secret shown once.
New endpoints remain disabled until a signed test receives HTTP 2xx. The sender currently requires a publicly resolvable IPv4 receiver on standard HTTPS. Redirects, local addresses, and unsafe DNS answers are rejected.
Verify signatures
Verify the signature against the exact raw request body before parsing it. Use the delivery's event identifier and timestamp. The signature input is eventId.timestamp.rawBody, authenticated with HMAC-SHA256 and the endpoint signing secret. Read the event identifier from X-Listaro-Event-ID and the signature from X-Listaro-Signature. The signature header carries t=timestamp,v1=hexSignature.
Use a constant-time comparison and a bounded timestamp tolerance. Deduplicate by the stable event ID before applying side effects. An event can arrive more than once.
Retries and replay
Failed deliveries retain their error and attempt history. Exponential retry delays are bounded; exhausted deliveries become dead. An authorized replay keeps the same event ID, so the receiver must remain idempotent.
The console can dispatch due events. Automatic delivery requires a configured maintenance schedule; its configuration is visible in the deployment's operating record.
Secret rotation disables the endpoint and clears verification until a test using the new secret succeeds. Pause an endpoint when you need to stop deliveries.