The best webhook testing tools in 2026 (free and paid, compared)

We make webhooks.sh, so weigh our opinion accordingly; below we say plainly where other tools win. Every competitor fact here was checked against the vendor's own site, docs or repository when this page was last updated.

Quick picks

• One-off inspection, no signup: webhook.site. You get a URL as soon as the page loads, it lasts 7 days, and you can set the response status and body for free. Runner-up: Svix Play, whose persistent URL has no published request cap.
• Local development: Hookdeck Console with the Hookdeck CLI. No account, requests land on localhost, and you can replay them. Reach for ngrok when you need a general-purpose tunnel, smee.io for GitHub apps, and the Stripe CLI if Stripe is all you test.
• Custom mock responses: Beeceptor. Rules return the status, headers and body you define, including dynamic and conditional responses; the free plan allows 3 rules per endpoint.
• CI, scripts and AI agents: webhooks.sh (ours). One POST with no API key returns JSON with an ingest URL, a secret view URL and an expiry time, and the bin expires after 48 hours. Svix Play, webhook.site, PostBin and the Webhook Relay bin also offer keyless APIs.
• Self-hosted: tarampampam/webhook-tester: MIT licensed, one Docker container, custom responses per session. Runner-up: webhook.site's open-source edition, also MIT.
• Production reliability: Hookdeck, a webhook gateway with retries included in the event price and a free plan of 10,000 events a month. A request bin is a debugging tool, not a production receiver.

Comparison table (as of October 2026)

Free-tier limits and the cheapest paid plan, from each vendor's pricing page and docs. Limits change often; check before you commit.

The tools, one by one

webhook.site

The default online webhook tester: open the page and you have a unique URL and email address, with every request shown live.

Where it wins: custom responses are free (status 200 to 599, body, content type, and a delay of up to 30 seconds), the public API is free (POST https://webhook.site/token creates a URL), bodies can be up to 10 MB, and an MIT-licensed edition runs on your own server with Docker. Paid plans add Custom Actions, a workflow builder that transforms and forwards requests.

Where it falls short: a free URL stops collecting after 50 requests and is deleted after 7 days, and free URLs are public: the docs say the data "is accessible to anyone who knows the ID of the URL". The MIT-licensed whcli CLI forwards requests to localhost, but webhook.site's docs list localhost forwarding as a Basic and Pro feature. Paid plans: Basic $9/month, Pro $27, Enterprise $69. More in webhook.site alternatives.

Beeceptor

A mock-server tool that doubles as a request bin: pick a name and you get name.free.beeceptor.com, no signup.

Where it wins: mock responses. Rules match incoming requests and return the status, headers and body you define, with dynamic and conditional responses on the free plan (3 rules per endpoint). The beeceptor-cli tunnel sends traffic to a local port for free, on an ephemeral URL.

Where it falls short: 50 requests per day per endpoint, 1 MB bodies, and free inspection is live only: request history starts on the Team plan ($25/month), as does CI/CD integration. Free endpoints are public, and unclaimed ones are cleaned up 30 days after creation. Paid plans start at $10/month (Individual).

Svix Play

Svix's free webhook tester at play.svix.com, with no signup for the web UI or the forwarding CLI.

Where it wins: the URL persists across sessions, Svix says the free tier puts no limits on the URL or dashboard, and svix listen forwards requests to a local URL without an account. A keyless API at api.play.svix.com creates tokens and returns captured history as JSON, which suits test suites. Query parameters can force a status code, echo the body or fail a share of requests at random, useful for testing a sender's retries.

Where it falls short: no custom response body and no published retention window. Play has no paid tier; Svix's paid plans, from $20/month, are for its production webhook platform.

Hookdeck Console and CLI

Hookdeck sells a webhook gateway; its Console is a free request inspector that needs no account.

Where it wins: local development. The Console gives you a URL and a CLI key; npx hookdeck-cli listen 3000 <source> --cli-key <key> then forwards requests to your machine, and you can retry any event from the CLI to replay it. Custom responses work with a query parameter such as ?x-hookdeck-response[text]=ok. For production, its gateway includes retries in the event price; Team starts at $39/month.

Where it falls short: Console sources are public to anyone with the source ID, guest sources are remembered only in the browser that created them (for up to 90 days), and the events list shows the latest 250 requests. More in Hookdeck alternatives.

ngrok

A general-purpose tunnel: it gives your local server a public HTTPS URL, and its inspector at localhost:4040 shows each request with a Replay button.

Where it wins: your real code handles real requests, so you test signature checks and business logic, not just payloads. Replay, including replay with edits, is free, and the local agent API lists and replays captured requests from scripts.

Where it falls short: you need an account and authtoken, and your app must be running; if it is down, the sender gets an error instead of a clean 200. The free plan allows 20,000 HTTP requests and 1 GB a month on one auto-assigned domain, and shows an interstitial page to browser traffic (programmatic requests such as webhooks are unaffected). The agent is closed source. Hobbyist costs $10/month. More in ngrok alternatives.

smee.io

A small forwarding service from the Probot project. Start a channel at smee.io, install the client with npm install --global smee-client, then run smee --url <channel URL> --path /webhook --port 3000.

Where it wins: it is free, needs no account, and GitHub's own webhook testing docs use it, so it is the path of least resistance for GitHub apps. The server is MIT licensed and self-hostable with Docker.

Where it falls short: payloads are never stored on the server (only in your browser), so events that arrive while the client is disconnected never reach your app. It always answers 200, channels are not authenticated, and the README says it is "intended for use in development, not for production".

Webhook Relay

A webhook forwarding service with a free, no-signup webhook bin on the side.

Where it wins: the bin accepts bodies up to 500 KB, lets you set its response status, body and delay, has a keyless API (POST https://bin.webhookrelay.com/v1/bins), and runs a small JavaScript function on every request that can reshape the payload or compute the response. A free account adds replay to localhost, and the main service forwards webhooks to a local server with relay forward --bucket my-app http://localhost:3000/webhooks.

Where it falls short: bins are public and expire after 48 hours, the free account covers 150 webhooks a month, and the relay CLI is closed source. Basic costs $8.99/month billed yearly.

UseWebhook

A minimal free tester at usewebhook.com, with no account and no API key.

Where it wins: the MIT-licensed CLI forwards to localhost (usewebhook $URL --forward-to http://localhost:3000/hook) and can replay any stored request by ID, and there is an official MCP server for AI coding tools.

Where it falls short: it keeps only the 20 most recent requests per URL and caps bodies at 10 kB. Custom responses and the HTTP API are not documented, and there is no paid plan.

tarampampam/webhook-tester (self-hosted)

An MIT-licensed Go app with a live web UI that runs from one command: docker run --rm -t -p "8080:8080/tcp" ghcr.io/tarampampam/webhook-tester:2.

Where it wins: captured payloads stay on your own infrastructure. Each session can return a custom status code, content type, body and delay, and you choose storage (memory, Redis or filesystem) and limits (defaults: 128 requests per session, 7-day sessions, no body size limit). It has a REST API (OpenAPI spec) and can open an ngrok tunnel itself for a public URL.

Where it falls short: you run, secure and update it yourself, and it does not forward requests to your app. The latest release, v2.3.0, shipped in April 2026.

webhooks.sh

Our tool: free, disposable webhook bins. Open view.webhooks.page for a bin in the browser, or create one with curl -X POST https://webhooks.sh/v1/bins, with no API key and no signup.

Where it wins: scripts, CI and AI agents. The create call returns JSON with an ingest_url, a view_url that carries a secret view key, a claim_url a person can use to keep the bin, and expires_at. The ingest URL accepts any method and path, and knowing it does not let anyone read the captured requests: reads need the view key in an x-view-key header, and Authorization and cookie headers are redacted. Unclaimed bins expire after 48 hours, so there is nothing to clean up after a test run. Our free HMAC signature verifier and webhook payload generator run entirely in your browser.

Where it falls short: no custom responses, and free bins neither forward nor replay. The paid Solo plan ($12/month) adds persistent endpoints, 90 days of history, replay, the wsh CLI that relays deliveries to localhost, and signed forwarding to up to 3 HTTPS URLs per endpoint. The anonymous viewer shows the latest 10 requests, bodies are capped at 100 KB, each bin takes 100 requests a day, and requests appear within about a second. Claiming a bin with a free Google sign-in stops the timer and keeps a rolling 30 days of new requests. Details in the API docs and on pricing.

Other request bins you'll run into

• RequestCatcher: pick a subdomain and watch requests arrive live. Nothing is stored (close the tab and they are gone) and the response is fixed. No signup; good for a ten-second "is anything arriving?" check.
• PostBin: an API-first bin; the old Toptal PostBin address redirects here. POST https://www.postb.in/api/bin creates a bin with no signup, and bins expire after 30 minutes.
• webhook.cool: a free, minimal inspector from the maker of the LocalCan app. Webhooks are deleted after 7 days of inactivity; other limits are not documented.
• requestbin.net: an independent service that uses the RequestBin name. The free plan has 3 bins, 500 requests per bin per day and keeps the latest 100 requests per bin; Pro is $12/month.
• Pipedream RequestBin: gone. requestbin.com and pipedream.com/requestbin now redirect to Pipedream's homepage. Our RequestBin alternatives page covers replacements.

How to choose

• "What exactly does this provider send?" Any no-signup bin will do. Trigger the event, read the headers and body, then check the signature with the HMAC verifier. Our guides for Stripe, GitHub, Shopify, Slack, Twilio and Discord cover each provider's specifics.
• "Does my handler work?" You need forwarding, not a bin; the FAQ below lists the tools. See how to test webhooks locally and how to test webhooks without ngrok.
• "What happens when my endpoint fails?" Pick a tool that can return errors or delays: webhook.site, Beeceptor, the Webhook Relay bin, a self-hosted webhook-tester, or Svix Play with force_status_code and random_failure_rate.
• "This runs in CI or an AI agent." Pick a keyless JSON API that cleans up after itself: webhooks.sh (48-hour bins) or PostBin (30-minute bins); Svix Play and webhook.site also work.
• "The payload contains customer data." Most free bins are readable by anyone with the URL or ID. Use test-mode data, self-host webhook-tester, or pick a tool that separates the ingest URL from read access.
• "This is production." Use a gateway with retries and alerting, such as Hookdeck, or Webhook Relay if the receiving server is not publicly reachable. If events go missing, start with why a webhook is not received.

FAQ

What is a webhook tester?

A webhook tester, also called a request bin, gives you a public URL that records every HTTP request sent to it. Point a provider such as Stripe or GitHub at the URL, trigger an event, and read the exact method, headers and body it sent. More in our guide to getting a free webhook URL.

What is the best free webhook tester?

For a quick look in the browser, webhook.site (no signup, free custom responses, 50 requests per URL for 7 days). To run your own code, the Hookdeck Console and CLI forward to localhost without an account. For automated tests and AI agents, a keyless API such as webhooks.sh or Svix Play.

What is the best webhook tester without signup?

webhook.site, Svix Play, Beeceptor, Hookdeck Console, smee.io, UseWebhook, RequestCatcher, PostBin, the Webhook Relay bin and webhooks.sh all work without an account. ngrok is the exception: even its free plan needs an account and authtoken.

Is webhook.site free?

Yes. Free URLs need no account, accept 50 requests and are deleted after 7 days, and anyone who knows a URL's ID can read what it captured. Paid plans remove the 50-request cap and add permanent, private URLs, starting at $9/month for Basic ($90/year).

What happened to RequestBin?

The original open-source RequestBin from Runscope is gone (its GitHub repository returns 404), and Pipedream's hosted requestbin.com now redirects to Pipedream's homepage. requestbin.net is a separate, independent service with the same name. For a no-signup replacement, use webhook.site, Svix Play or webhooks.sh; see RequestBin alternatives.

Is PostBin still available?

Yes, at postb.in; the old Toptal PostBin address redirects there. You create bins in the browser or with POST https://www.postb.in/api/bin, no signup, and each bin expires after 30 minutes, so it suits quick scripted checks.

How do I test webhooks on localhost?

Use a forwarding tool that gives you a public URL and relays requests to your machine: the Hookdeck CLI, ngrok, smee.io, svix listen, the UseWebhook CLI, Beeceptor's tunnel or webhook.site's whcli (a paid feature). For Stripe alone, run stripe login, then stripe listen --forward-to localhost:4242/webhook. Step by step: test webhooks locally.

Are free webhook testers safe for real data?

Treat them as public. On webhook.site, Beeceptor's free plan, Hookdeck Console, smee.io and the Webhook Relay bin, anyone with the URL or ID can see captured requests. Use test-mode data, rotate any secret that lands in a bin, or self-host. webhooks.sh keeps reads behind a separate view key and redacts Authorization and cookie headers, but it is still a debugging tool, not a vault.

Which webhook testers have an API for CI or AI agents?

webhooks.sh (POST https://webhooks.sh/v1/bins, then read with an x-view-key header), Svix Play (api.play.svix.com), webhook.site (POST https://webhook.site/token), PostBin, the Webhook Relay bin and the Hookdeck Console API all work without an API key. Beeceptor's CI/CD integration starts on the Team plan, and UseWebhook offers an MCP server.