Engineering

How webhook delivery behaves when it stops behaving. Retries and their arithmetic, signatures over exact bytes, replay that does not replay the bug, and the failure modes you meet at 2am.

05 articles

Two diagrams on black, split by a vertical rule. Left: a provider cloud feeds a coral box labelled your handler, which splits into three white boxes, API, analytics and billing; a coral outline round all four reads one failure domain. Right: the same cloud feeds an indigo bucket that sends a short arrow marked 200 back to the provider, then splits into three rows, each in its own dashed outline with a queue, a clock and a circuit breaker. Under a dashed line: three destinations, three queues, three clocks.

Aug 26, 2026EngineeringFan out to three services, not three failure domainsOne webhook, three consumers, and a handler that quietly became a router. Moving the fan-out upstream of your code gives every destination its own queue, clock and breaker.

Quentin Mousset5 min read

A schema.repost box lists id String, amount Float and currency String, with currency circled as the field just added. Six dashed arrows fan out to six generated clients: typescript, go, java, kotlin and csharp each carry a check mark, while python carries a coral cross annotated still on the old shape. A brace gathers all six toward repost schema generate --check, where the note reads build fails here, not in production.

Aug 17, 2026EngineeringOne webhook schema. Six SDKs that never drift.Hand-maintained clients drift the week you ship. Generate all six from one schema file, and let CI fail the pull request that forgets one.

Quentin Mousset2 min read

An evolution chart headed Webhooks Progress Timeline, with five labelled boxes above it: PING 1999, TRACKBACK 2002, WEB HOOKS 2006, WEBSUB 2018, WEBHOOK 2026. The first two figures are a knuckle-walking ape and a stooped hominid, then the line stops evolving: the 2006, 2018 and 2026 figures are the same upright walker, repeated without a single change. An arrow curves back from 2026 to 2006, and the caption reads Same HTTP POST. Different stakes.

Aug 03, 2026EngineeringWho invented webhooks? Meet the HTTP POST that never grew upSeveral serious attempts to replace it, and a webhook is still an HTTP POST to a URL you chose. The protocol never moved. What it carries did.

Quentin Mousset15 min read

A retry timeline for a 30-second base, a ×3 multiplier and a 3-hour cap: attempts land at 0s, 30s, 2m, 6m30, 20m, 1h and 3h02, separated by gaps of 30s, 1m30, 4m30, 13m30, 40m30 and 2h02. Past attempt 7 the cap engages and every further attempt sits three hours after the last, so attempt 14 falls at 24 hours, where the schedule gives up.

Jul 27, 2026EngineeringWebhook retry storms and the arithmetic of backoffFixed-interval retries turn one slow consumer into a queue that never drains. What exponential backoff actually costs, and how to size the ceiling.

Felipe Schulz10 min read

The same JSON object in two serializations: the producer's 35-byte body and the 31-byte string that comes back from JSON.parse then JSON.stringify. Each one hashes to a different HMAC-SHA256 under the same signing secret, so only the producer's bytes match the webhook-signature header and the re-serialized copy is rejected.

Jul 13, 2026EngineeringWebhook signature verification, end to endA webhook signature covers the exact bytes on the wire, not the object you meant to send. Why re-serialization breaks verification, and how to test it.

Quentin Mousset11 min read