Webhook.site review

Webhook.site is a hosted SaaS application that creates unique HTTP URLs, email addresses and DNS names for capturing inbound traffic. It sits between a client or service that sends a request and the application you are debugging: point the sender at a Webhook.site endpoint, then inspect the captured headers, query string and body in a browser.

The free endpoint needs no signup, but expires after one week and stores up to 50 requests. An account removes those restrictions and adds workflows, custom domains and other features. The service also offers a CLI to forward captured requests to localhost or a private network, which helps when a webhook sender cannot reach a development machine directly. For ongoing processing, visual workflows can filter, transform, forward or respond to requests and emails. Schedules, databases and a REST API extend it beyond a temporary request bin into a hosted automation service.

The main integration surface is an HTTP endpoint: Webhook.site captures any HTTP method and sub-path sent to its unique URL. The homepage also links to a REST API for managing the service programmatically, plus documentation, an API reference and guides for Custom Actions and the CLI. It does not name SDK languages, so confirm SDK support in the vendor’s docs before choosing a client library.

The Webhook.site CLI forwards captured requests to localhost or a private network; the homepage shows whcli forward --target=https://localhost and lists Mac, Windows and Linux installation. For automation, Custom Actions provide visual steps, while WebhookScript and JavaScript handle logic outside those steps. Named integrations include Google Sheets, Excel, Slack, S3, Dropbox, SFTP, databases and push notifications. The service also captures email and DNS traffic, so the integration surface includes more than HTTP webhooks.

The no-signup free tier costs nothing, but each URL expires after one week and stores up to 50 requests. Paid plans list unlimited incoming requests, while request history, URLs, schedules and users vary by tier. Basic costs $9 monthly or $90 annually ($7.50/month equivalent) and includes one URL, 1,000 request history, one schedule and one database. Pro costs $19 monthly or $190 annually ($15.83/month equivalent); it includes 50 URLs, 10,000 request history, five schedules and one database.

Enterprise costs $69 monthly or $699 annually ($58.25/month equivalent), with unlimited URLs, 100,000 request history, unlimited schedules and 10 users included. These tiers make the bill depend on the plan’s history, URL, schedule and seat allowances rather than a published per-request charge. The pricing lists no add-ons. Before production use, check whether your retention and team requirements fit the included caps; the vendor does not publish overage pricing.

A Reddit commenter points to an open-source version of Webhook.site on GitHub and says it can be hosted yourself. The license is not published in the homepage text, so check the repository’s current license and deployment requirements before using it. Do not assume the self-hosted version includes every hosted feature: commenters report missing multipart/form-data display and container deployment trouble in particular environments.

For the hosted service, captured endpoints are unique URLs, email addresses and DNS names; moving senders to another service means changing those destinations. The homepage shows CSV Export and describes a REST API for managing the service, which may help with data handling and migration. Confirm what each export includes and whether it covers attachments, workflow configuration and request history before relying on it. The vendor does not publish a migration guide in the homepage text.

Treat a free URL as a temporary debugging endpoint, not a durable production destination: it expires after one week and stops at 50 requests. The homepage says account URLs are protected and managed, while its free URL notice says an unassociated URL is not protected by login. Paid plans allow unlimited incoming requests, but request history remains capped at 1,000, 10,000 or 100,000 depending on the tier. The vendor does not publish an SLA in the homepage text; ask about uptime, retention, data residency and compliance before routing sensitive production traffic.

Reddit users report limitations in the open-source version, including a missing multipart/form-data display, and one commenter had trouble running its container image on Azure Web App for Containers. Those are reports about self-hosting, not evidence of hosted-service reliability. Test your payload types and deployment environment, and verify how retries, workflow errors and access controls behave for your use case.