See the event that really arrives.
Use a temporary public endpoint for real delivery testing, or paste a sample locally when you already have one.
Free tool · Webhook Tester + Payload Mapper
Catch the event. Map the handoff.
Create a temporary webhook URL, inspect the real request, turn the payload into a schema and map it to the shape another system expects. No signup.
Live request binTemporary HTTPS endpoint · no signup
Files you can keepJSON Schema · TypeScript · payload download
Map the handoffSource paths → target paths → checks to verify
Integration debugging
Start with the request that actually arrives.
Use a live endpoint to catch what a service really sends, or paste a sample you already have. Paste mode stays in your browser, and the mapping review only needs field paths and types rather than the captured values.
Your temporary endpoint.
Create an unguessable test URL, paste it into Stripe, GitHub, Shopify, your app or any webhook sender, then watch requests arrive here.
—Waiting
Privacy note: live capture has to reach a server. Test requests expire with the temporary session (default: one hour), and you can delete the session immediately. Common credential, cookie and signature header values are redacted before storage. Payload bodies can still contain customer data or secrets, so use test data where possible. Paste mode stays in your browser.
Captured requests.
Newest request first. Select one to inspect the body, query parameters, headers, schema and implementation risks.
No events yet.Create a URL, point a webhook at it, or send the sample event.
Paste a real sample.
JSON and form-encoded bodies are parsed locally. Your payload values stay in the browser; the optional mapping review receives field paths, types, header names and a redacted version of any workflow goal you type.
What we inspect locally.
Shape + field types
Nested paths, arrays, depth and a reusable schema.
Event identity + timestamps
Candidate fields worth verifying for duplicate/retry handling.
Personal-data field names
Flags likely email, phone or address fields without sending their values.
Target mapping gaps
Compare the source contract with a sample payload another system expects.
Captured contract
Request inspected.
Generated schema and TypeScript are conservative sample contracts. One request cannot prove which fields are always required or every variant the provider may send.
What matters before production
Map it to a target.
Paste one example of the JSON shape the receiving system expects. Target values stay local. The review receives source and target field paths/types, header names and a redacted version of the optional workflow goal.
Mapping review.
Candidate source-to-target mappings and the checks to complete before you rely on the integration in production.
Inspect a payload first. Add a target sample if you want field-to-field mapping.
See what you get
Most request bins stop at capture. This helps you map what comes next.
Turn one sample into something buildable.
Generate conservative schema paths, JSON Schema and TypeScript from the observed payload, then flag what still needs verification for retries, identity, signatures and optional fields.
Design the next system handoff.
Compare the captured source shape with the target shape. Candidate mappings are limited to fields that really exist in the two samples.
Need to turn this payload into a reliable integration?
ZappFlow can build the production handoff.
We build API integrations, webhook receivers, workflow automation, data transformations and the custom software around them. The test tells you what is arriving; the build makes it reliable.
ZappFlowSoftware, automation, integrations, data and AI built around the way your business actually works.Start a project →
Questions
Before you point production webhooks at a test URL.
How long are captured requests stored?
Live capture requires temporary server storage. The default deployment expires a webhook session after one hour, and you can delete the session immediately from the page. Use test data where possible because real webhook payloads can contain sensitive information.
Can I use it without sending a payload to ZappFlow?
Yes. Paste mode parses and inspects the request body entirely in your browser. Live capture necessarily reaches the temporary endpoint because an external webhook sender needs a public URL.
Does the mapping review see customer values?
No. The review is built from field paths, types, header names and deterministic evidence signals. Captured payload values are not sent to the review. If you add an optional workflow goal, obvious URLs, emails, tokens and identifiers are redacted before that note is sent.
Does a signature header mean the webhook is secure?
No. A signature-looking header is only a signal that verification may be available. You still need the provider's documented algorithm, signing secret or public key, canonicalisation rules and replay guidance.
Can it prove a field mapping is correct?
No. Mapping suggestions are candidates to verify. A matching field name does not prove identical semantics, units, identifiers or required formats in the receiving system.