Signed webhooks
Configure delivery, verify signatures, process at-least-once events, and recover failed deliveries safely.
Receiver checklist
- Expose an HTTPS endpoint with a bounded raw-body limit.
- Read the timestamp and signature headers and verify the exact raw bytes before parsing JSON.
- Enforce the released timestamp tolerance and current/overlap secret rules.
- Deduplicate stable delivery and event identities in your durable queue.
- Return success quickly after durable acceptance; perform business work asynchronously.
Delivery semantics
Webhook delivery is at-least-once. V Chat retries bounded eligible failures with backoff and keeps operator-visible delivery state. Consumers must be idempotent and must not depend on arrival order across unrelated channels.
Secret rotation
Store webhook secrets outside source control. During an approved rotation overlap, verify against the released current/previous secret contract, monitor failures, and remove the old secret after the overlap window. Never log the signature secret or raw content payload.