Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Tool · Web DevelopmentFree

Webhook.site

A free tool that gives you a unique URL and email address and shows every request sent to them, with headers, body and query string. It is the quickest way to see exactly what an app sends in a webhook before you build the workflow that receives it.

Format

Tool

Topic

Web Development

Provider

Webhook.site

Level

All

Access

Free

What it does

Open Webhook.site and it immediately gives you a random, unique URL and email address. Anything sent to that URL, whether a webhook from a form tool, a payment provider test event or a request you send from Postman, appears in the page in real time. You see the method, headers, query parameters and the raw body, and you can copy the payload for later.

Why it matters for automation work

Building a trigger blind is slow. Before you wire an app's webhook into n8n, Make or Zapier, point it at a Webhook.site URL and look at what actually arrives: which fields are present, whether numbers come as text, how dates are formatted, whether there is a signature header, and whether the same event arrives more than once. That tells you how to map fields, what to validate and whether you can verify the sender. It is also useful for checking that your own workflow sends the request you think it does.

Free versus paid

As of 2026-09, the official documentation says free URLs accept up to 100 requests or emails and expire after 7 days, after which the data is deleted. Paid subscriptions remove those limits, keep URLs permanently and add features such as custom actions, schedules and databases, which turn it into a small automation tool of its own. For learning and debugging, the free tier is enough. Check the official pricing page for current plan prices before recommending it to a client.

Privacy and safety

Anything you send to a free URL is visible to whoever has that URL, so never send real customer data, API keys or production payloads there. Use test events from the app's sandbox or test mode. Treat it as a debugging aid, not a place to store anything.

How to use it well

  • Create a fresh URL for each app you are investigating.
  • Trigger a test event and save the payload as your sample data.
  • Send the same event twice to see whether the app retries or duplicates.
  • Compare the headers with the app's documentation on webhook signatures.

Common questions

Is it safe? For test data, yes. For personal or payment data, no.

Do I need an account? Not for the basic free URL.

Is there an alternative? Most automation tools have their own test webhook listeners, and request bin tools exist too, but Webhook.site works with any sender and needs no setup, which is why it is so widely used.

apitestingbackendproductivity

Ready to start?

Opens on Webhook.site in a new tab.

Open resource
Link broken or out of date?

Report a problem

With "Webhook.site". Only Tauseef reads this.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.