Send any HTTP request to the URL above and it will appear here in real-time.
A webhook tester gives you a temporary public HTTPS URL that captures every incoming HTTP request. When a third-party service fires a webhook, the tester records the method, headers, query parameters, and body so you can examine them in a structured view. It holds every request sent to that URL until you are ready to inspect it.
Webhooks power most event-driven integrations. Stripe notifies on successful payments, GitHub on new commits, Shopify when an order ships. The catch: these services need a publicly routable URL, and during development your code runs on localhost. A webhook tester bridges that gap. Paste its URL into the provider's settings, trigger an event, and watch the payload land in real time. Check the Content-Type, verify the JSON structure matches what the docs promise, confirm HMAC signatures are present -- all before writing a single line of handler code.
Hook0 Play is a webhook tester built for speed. No signup, no email confirmation, no paywall. The URL is ready the instant the page loads. Read more about webhook architecture in the Hook0 documentation.
With Hook0 Play, it takes under a minute.
No DNS setup, no port forwarding, no tunnel configuration. For local development workflows, pair the web tester with the Hook0 CLI to forward requests to your machine.
Most webhook testing services lock useful features behind a paywall. Hook0 Play is completely free, open source, and self-hostable.
| Feature | Hook0 Play | webhook.site | RequestBin |
|---|---|---|---|
| Instant URL, no signup | Yes | Yes | Yes |
| Real-time feed (WebSocket) | Yes | Yes | Polling |
| Max stored webhooks (free) | 1,000 | 50 | 20 |
| Local tunnel (CLI) | Free | Paid | N/A |
| Open source | Yes (SSPL) | No | No |
| Self-hostable | Yes | No | No |
| Client-side tracking | None | Yes | Yes |
| Custom response (free) | Via CLI | Paid | Paid |
Hook0 Play stores up to 1,000 webhooks per URL for 24 hours. No captchas, no cookie banners, zero JavaScript analytics. Your webhook payloads stay between your browser and the server. The project is open source -- audit the code, contribute fixes, or run the entire stack on your own infrastructure with a single Docker Compose command.
If you have been looking for a webhook.site alternative or a RequestBin alternative that does not track you or paywall basic features, this is it. Compare features in detail on the comparisons page.
The web UI captures webhooks on a public URL, but during development those payloads need to reach the server on your laptop. Tools like ngrok require signup and an auth token. The Hook0 CLI is purpose-built for webhook forwarding and does not require registration.
hook0 play listen --forward http://localhost:3000/webhooks
This connects to your Hook0 Play session and relays every incoming request to the specified local address. The request arrives at your local server with the original method, headers, and body intact. It shows up in your terminal, in the web UI, and your breakpoints fire in your IDE.
The CLI also lets you control the status code and body returned to the webhook sender. Handy for testing retry logic: return a 500, watch how Stripe or GitHub retries, then switch to 200 and confirm the happy path.
Install the CLI from the Hook0 documentation. It runs on macOS, Linux, and Windows.
Hook0 Play works with anything that sends HTTP requests to a URL -- payment processors, version control platforms, e-commerce systems, messaging tools, monitoring services.
Services people commonly test with Hook0 Play: Stripe, GitHub, Shopify, Slack, Twilio, Discord, Mailchimp, PayPal, Jira, Trello, SendGrid, PagerDuty, and Salesforce.
Any HTTP method works -- POST, PUT, PATCH, DELETE, whatever. If you are building your own service and need to test the webhooks you send, the full Hook0 platform handles event types, subscriptions, and delivery management.
A webhook tester gives you a unique HTTPS URL that captures incoming HTTP requests so you can inspect headers, body, method, and query parameters in real-time. It lets you verify that Stripe, GitHub, Shopify, or any other service sends the correct payload format before you write your production handler.
Yes. No signup, no limits. Open the page, get a URL, start receiving webhooks. The CLI tunnel for local forwarding is free too.
Webhooks are stored for up to 24 hours. Each URL keeps up to 1,000 webhooks; the oldest are evicted first when the limit is reached.
Yes. There is no account, so no identity is tied to your webhook URL. Data is stored server-side and automatically deleted after 24 hours. The page loads zero client-side analytics.
Yes. Install the Hook0 CLI and run hook0 play listen --forward http://localhost:3000/webhooks. Every request hitting your Hook0 Play URL gets relayed to your local server in real-time. See the CLI documentation to get started.
All HTTP methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, and TRACE. Any request sent to your URL is captured regardless of method.
Yes. Hook0 is open source (SSPL license). You can run the entire stack including Hook0 Play on your own infrastructure with Docker or Kubernetes. See the self-hosting documentation.
Hook0 Play is the receive side of webhooks. When you need to send webhooks from your own application, the full Hook0 platform handles routing, retries, event types, and delivery guarantees -- so you can skip building that infrastructure yourself.