Webhook.site review

Webhook.site creates a unique URL and email address for capturing incoming HTTP requests and emails, with no signup required. It also supports DNS lookups through DNSHook. Requests and messages appear in real time, so you can inspect headers, query strings, bodies and, for emails, attachments.

The free, no-signup URLs expire after one week and retain up to 50 requests. An account removes those limits and adds tools such as workflows and custom domains. For more capacity, paid plans start at $9 per month, or $90 per year ($7.50 per month equivalent), according to the pricing page.

This is for debugging and handling incoming traffic, not just viewing a payload. You can filter, transform, forward or respond to requests and emails with visual workflows, or add logic with WebhookScript or JavaScript. A CLI can forward captured requests to localhost or a private network.

Webhook.site covers several common debugging jobs in one place: inspect an HTTP request, capture an email sent by a system under development, or see a DNS lookup. The no-signup option makes it quick to get a temporary endpoint, while account and paid options give teams more control over URLs and retained history.

The workflow tools are more useful than a passive request log when you need to do something with captured traffic. You can filter, transform, forward and respond to requests or emails. For logic that outgrows those steps, WebhookScript and JavaScript provide a scripting route. CLI forwarding also lets developers send captured traffic to localhost or a private network.

Plan limits are stated plainly. Basic is $9 monthly or $90 annually and includes one URL, unlimited requests, 1,000-request history, one schedule and one database. Pro is $19 monthly or $190 annually, with 50 URLs and 10,000-request history. Enterprise is $69 monthly or $699 annually, with unlimited URLs and 100,000-request history. All three list unlimited requests; the stored-history cap is the more relevant limit for reviewing older traffic.

The free endpoint is temporary: it expires after one week and holds up to 50 requests. That is fine for a short debugging session, but not a dependable archive. Paid plans remove the free endpoint limits, but they still cap retained history: 1,000 requests on Basic, 10,000 on Pro and 100,000 on Enterprise. “Unlimited requests” does not mean unlimited history.

There is also a meaningful jump between plans. Basic gives you one URL and one schedule; Pro costs $19 monthly ($15.83 per month when billed annually) for 50 URLs and five schedules. Shared access appears only on Enterprise, which lists 10 included users and costs $69 monthly or $699 annually. The pricing details do not list add-ons.

If hosting the capture service yourself is a requirement, Reddit users point to an open-source Webhook.site version, but one commenter reports that it did not show multipart/form-data. Another describes trouble running its container image on Azure Web App for Containers. Those are individual reports, not a complete compatibility picture, but they are reasons to check the self-hosted option against your setup before switching.

Webhook.site has a free option, but free URLs expire after one week and store up to 50 requests. Paid plans remove those free-tier limits and add features such as workflows and custom domains.

Basic is $9 month to month or $90 annually ($7.50 per month equivalent). It includes one URL, unlimited requests, 1,000 request history, one schedule and one database. Pro costs $19 monthly or $190 annually ($15.83 per month equivalent): 50 URLs and 10,000 request history. Enterprise is $69 monthly or $699 annually ($58.25 per month equivalent), with unlimited URLs and 100,000 request history. It also includes 10 users.

The tier jumps are $10 and then $50 per month on monthly billing. All plans list unlimited requests, but stored history is capped, so that is not the same as an unlimited archive. The pricing information lists no add-ons. Annual billing is paid as a yearly amount; the monthly equivalents are comparisons, not the monthly-billing price.

Getting started is straightforward if you can point a sender at a new capture URL: Webhook.site creates a unique URL without requiring signup. But the available information does not describe an import tool, data-export format or migration service, so don’t assume existing request history or workflow settings can be moved in or out. Data export details are not published here.

Before switching, check how many URLs and how much request history you need. Paid plans cap history at 1,000, 10,000 or 100,000 requests, depending on tier; the free option keeps up to 50 requests and expires after a week. If leaving, preserve anything you need before it disappears, but the available information does not say how to export it.

We don’t have Reddit posts or comments in the published published material, so we can’t attribute reasons for leaving to Reddit users. Support commitments and self-hosting trade-offs are also not specified here. Treat both as questions to resolve before moving production workflows.