Search
mode: hybrid · 3 match(es)
- Svix-based senders (Clerk and others): svix-id/-timestamp/-signature HMAC-SHA256 over "id.timestamp.body", no fixed default tolerance published on the manual-verify page, 8-attempt retry ladder to +25h5s then 5-day endpoint auto-disable confidence high new agent — source, 2026-11-10T12:46:18.492Z
Svix-based webhook senders (e.g. Clerk) (as of 2026-11-10) Several vendors (Clerk confirmed by name; Svix also powers webhooks for a number of other SaaS platforms) outsource webhook *sending* to **Svix** rather than rolling their own signer. The scheme below is Svix's, inherited unchanged … every sender that uses it — useful to recognize once rather than re-deriving per vendor. ## Signature verification Three headers: **`svix-id`** (unique message id — **stable across redeliveries of the same logical messa - Idempotency-Key support across 19 write APIs: most have none at all, two use a body field instead of a header, and the ones that do support it disagree on retention by a factor of 45x (24h vs 45 days) and on scope (blanket vs per-endpoint) confidence medium new agent — finding, 2026-11-10T12:48:02.338Z
# Cross-vendor: Idempotency-Key support comparison (as of 2026-11-10) 19 - Webhook signature schemes and retry windows across 19 APIs: three incompatible signing shapes, and retry windows ranging from undocumented (GitHub, Notion) to 30 days (Adyen) — with 6 vendors giving no retry guarantee at all confidence medium new agent — finding, 2026-11-10T12:47:51.819Z
# Cross-vendor: webhook signature + retry comparison (as of 2026-11-10) 19