How to tell a retry from a new event
A webhook arrives twice and your handler runs twice — or the payload changed between the two copies and you no longer know which one is true. The fix is a field-by-field comparison plus the event ID. When you paste two deliveries here, your browser:
- Parses both bodies and diffs them field by field — added fields, removed fields, changed values, and type changes (a string where a number used to be), each with a plain-English explanation of why it matters to a handler. Key order and whitespace never count as changes.
- Diffs the headers separately, flagging signature headers — a re-signed delivery looks identical except for its signature, so signature changes are called out on their own instead of being mistaken for a changed payload. Status and response time are compared too: a 500 on the first attempt is the usual reason a provider retries.
- Reads the event ID and gives a verdict — the same ID on both sides means the same event; different IDs mean different events. Combined with whether the bodies match, that produces one of five plain verdicts, from “duplicate delivery” to “same event, different payload — treat with care”.
What makes this viewer different
The pages that top the results for webhook comparison are mostly hosted webhook services — their delivery-comparison view lives inside an account, behind a signup, and only compares deliveries that service itself captured. Generic JSON diff tools will diff two payloads, but they know nothing about webhooks: they cannot read an event ID, they treat a re-signed signature as just another changed string, and they say nothing about whether the two deliveries are the same event. This page is the only free, fully client-side viewer we found that compares two webhook deliveries with webhook semantics — event-ID verdicts, signature-header handling, status and timing comparison, and downloadable Markdown and JSON reports — with no account, no upload, and a live network-request counter so you can verify the privacy claim yourself.
When is comparing the right choice — and when is it the wrong one?
Comparing is right the moment a delivery arrives twice, a retry behaves differently from the first attempt, or a customer reports an event your logs show differently. It is the wrong choice as a substitute for your own logs — this tool only knows the two copies you paste, so if your handler stored a third version, check that record directly. It is also the wrong choice for verifying a signature: pasting a signature here never proves the payload came from the provider; only checking it against your shared secret, on your server, does that.
Honest limitations
It compares what you paste
If your server received something else, or the provider sent a third copy you did not paste, this diff cannot know about it. Check your own logs for the full picture.
No ID, no retry verdict
Without an event or delivery ID in the body or headers, the tool says it cannot tell a retry from a new event. It never guesses — add the ID to your logs and compare again.
Duplicate here is not proof
Matching payloads mean the two copies you pasted are the same. They do not prove your handler processed the event only once — check your idempotency keys and logs for that.
It never verifies signatures
A signature header is compared as text, not checked against your secret. Only your server, holding the shared secret, can verify a delivery really came from the provider.
Non-JSON bodies get a line diff
Form-encoded, XML or plain-text bodies are compared line by line, which is coarser than the field-by-field JSON diff. Whole lines added or removed is all it can report there.
500,000 characters per side
Very large payloads are refused rather than silently truncated. Paste the relevant excerpt, or split the body and compare the part that changed.