Webhook.site and Friends: Inspecting Incoming Data Before You Build
Short answer: A webhook inspector gives you a temporary web address that records every request sent to it. Point a test payment or form at that address, trigger one event, and read the headers and body that arrived. Use those real examples to map fields in your automation, instead of guessing from the provider's documentation. When you finish, delete the captured requests, use test data only, and never paste live keys or customer details into a public inspector.
Why guess when you can look
Most payment, booking and form tools describe their webhook payloads in documentation. The descriptions are useful, but they can be out of date, they often show only the fields the vendor thinks matter, and they rarely show how a particular plan or setting changes the output. A field called customer_email in the docs may arrive as email in your account, or sit inside a nested object you did not expect.
Building an automation against a guess means rework later. Each wrong field name shows up as an empty value in the next step, and the cause can take an afternoon to find. Ten minutes of inspection at the start avoids that.
Step 1: Create a temporary endpoint
Open a webhook inspector in your browser. Several free services offer a temporary address that displays incoming requests. The one you choose matters less than how you use it. Each service generates a unique URL, and anything sent to that URL is visible to anyone who has the link.
Copy the address. It usually looks like a long random string on the service's domain. Treat it as a private test address and do not share it on forums or in support tickets.
Step 2: Point a test event at it
Most tools let you register a webhook URL in a settings page, usually under "developers", "integrations" or "webhooks". Paste the test address there and choose the events you want to see. Begin with one event type, such as a completed test payment or a new form submission, so the output stays easy to read.
Put the provider into test mode first. Payment tools provide test cards and sandbox data, and form tools let you submit with a dummy name. For example, a booking tool might let you create a booking for "Test Customer" at a fake address with a test email. The request that arrives will look just like a real one, without any real customer behind it.
Trigger the event once. Then return to the inspector.
Step 3: Read the headers
The headers tell you how the data is packaged. Look for these:
- Content-Type. A value of
application/jsonmeans the body is structured JSON. Form-encoded data looks different, and your automation tool needs to parse it accordingly. - A signature header. Many providers add a header containing a signature so you can confirm that a request really came from them. Note its name, because your automation or your server may need to verify it.
- Event identifiers. Some providers include an event ID or delivery ID. Keep it, because it helps detect duplicates when a provider retries a delivery.
If you are not sure what a header means, the HTTP headers reference on MDN Web Docs describes the common ones in plain language.
Step 4: Map the body
The body is where the fields are. Expand the JSON and write down the path to each value you need. A typical path looks like data.object.customer.email, which means the email sits inside the object called customer, inside object, inside data. Your automation tool probably lets you pick the value from a list once one test event has arrived, which is faster than typing paths by hand.
Create a simple mapping table in a document:
| Your field | Path in the payload | Example value | Notes |
|---|---|---|---|
| Customer email | data.object.customer.email | test@example.com | Use lowercase when matching |
| Amount | data.object.amount_total | 4500 | Stored in the smallest currency unit |
| Booking reference | data.object.metadata.ref | BK-1042 | Empty if not set at checkout |
The "Notes" column is where most of the value sits. An amount that arrives in cents, or a field that is empty unless you set it at checkout, will cause errors in a sheet or CRM if you miss it.
Step 5: Test edge cases
One successful event does not show everything. Trigger two or three more: a refund, a cancellation, and a payment with a missing optional field. Check that the fields you rely on still arrive. Many automations break on the second or third event type, not the first.
Privacy and safe habits
Public inspectors are convenient, but they are not private storage. Follow these habits:
- Use test mode and dummy data only. Never send live card details, real customer records or live API keys through a public inspector.
- Do not paste a signing secret or an access token into the inspector's settings, even for testing.
- Delete the captured requests when you finish. Most inspectors have a delete or clear option, and some expire captured data automatically.
- Remove the test webhook registration from the provider's settings once you have built the real one. A forgotten test endpoint keeps receiving copies of events.
- Keep a note of what you tested, so the next person does not have to repeat the exercise.
For a production automation, use a proper endpoint that you control, with signature checks and logs, rather than the inspector.
A quick checklist
- Create a temporary endpoint.
- Register it for one event in test mode.
- Trigger the event with dummy data.
- Record the headers, especially content type and signature.
- Map each needed field to its path.
- Trigger a refund or cancellation and check again.
- Delete the captured data and remove the test registration.
FAQ
Is a webhook inspector safe to use?
It is safe for test data and test events. It is not a place for live customer data or secrets, because anyone with the address can view what it captured.
Do I need to write code to use one?
No. The inspector shows the request, and most automation tools let you pick fields from a test event. Code becomes necessary only for custom endpoints.
What if the test event never arrives?
Check the URL you registered, confirm the event type matches the one you triggered, and make sure the provider is in the mode where it sends webhooks. Some tools also show a delivery log with the reason for any failure.
How do I remove the captured data?
Use the clear or delete option in the inspector, and check whether it expires captured requests on its own. Also remove the test URL from the provider's settings so nothing else arrives there.
If you would like us to map the webhooks for your payment or booking tool and build the automation that uses them, tell us which tools are involved and we will look at the test data with you: contact us.