Developer tool
Webhook Tester and Inspector
Get a temporary URL that captures incoming webhooks and shows the method, headers, query and body live. Holds 100 requests for 48 hours. Free, no sign-up.
Free, no sign-up. Requests sent to your inbox are stored on our server for 48 hours, then deleted.
New inbox
You get a unique URL that stores the requests it receives for 48 hours (max 100, 256 KB each). Nothing is forwarded anywhere.
How to use the webhook tester and inspector
See exactly what a service sends you
Payment providers, form tools and chat apps all promise to "send a webhook", but the first time it arrives you want to read the real payload before writing code. This tool gives you an address that accepts anything and shows it back.
Use it
- Create an inbox. Give it a name and choose the status code it answers with. You receive a unique URL and a private inspector link.
- Paste the URL into the service's webhook settings, or try it yourself with the cURL example shown in the inspector.
- Trigger an event. The request appears within a few seconds.
- Inspect it. The left list shows method, path, time and size. The detail view shows headers, query parameters and the body, formatted when it is JSON or form data.
What to check first
- Content-Type. A body that looks like JSON but arrives as form data is a classic bug.
- Signature headers. Note the header name and format for verification code, such as a timestamp plus an HMAC.
- Retries. Choose a 500 response to see whether the sender tries again and how often.
- Size. Large payloads are cut at 256 KB here; real endpoints may need to accept more.
Good habits
- Use test mode data from the provider, never live customer records.
- Delete the inbox when you finish. It expires after 48 hours anyway.
- Do not leave the inspector link in screenshots: anyone with it can read the requests.
Limits
The inbox stores 100 requests, accepts bodies up to 256 KB and does not forward or replay anything. It is a read-only catcher, not a proxy.
Frequently asked questions
How long does an inbox last?
Forty-eight hours from creation, after which the inbox and every captured request are deleted automatically. You can also delete it yourself at any time from the inspector.
What gets stored?
The method, path, query string, headers and body of each request, with a size note. Bodies over 256 KB are cut. The sender's IP address is not stored. Do not send real customer data or secrets to a test inbox.
How many requests can it hold?
One hundred. After that the URL answers with an error until you clear the inbox. Each inbox is also rate limited to 60 requests a minute so a runaway sender cannot flood it.
Which methods are accepted?
GET, POST, PUT, PATCH and DELETE are captured, HEAD and OPTIONS get a simple answer for CORS checks. JSON and form bodies are pretty-printed; binary bodies are shown as base64.
Can I choose the response?
Yes, pick the status code the URL answers with (200, 201, 202, 204, 400, 404 or 500) to test how a sender retries or handles failures. The body is always a small JSON acknowledgement.
Is the inspector live?
It checks for new requests every three seconds while the tab is visible. Pause it any time. The inspector is private: only people with your link can read the requests.