WebhookCat docs
Start with an anonymous URL or sign in to keep named inboxes across devices.
Your URL
Opening webhookcat.com gives you a URL like https://webhookcat.com/<id>. It accepts any method and content type, and any sub-path or query string after the id, so one URL can stand in for several endpoints: /<id>/stripe/events, /<id>/github.
Requests appear in the browser as they arrive. Only the browser that created the URL can read them, plus anyone you give the Share link to. Knowing the URL only lets someone send requests.
Account inboxes
Open My inboxes and sign in to create a named inbox. Give its fixed capture URL to your webhook provider. Only your signed-in account can read requests and edit settings. Sign in on another device to open the same inbox. Viewer-key sharing and CLI forwarding are available on anonymous inboxes.
Forward to localhost
The CLI receives each request as it arrives and sends a copy to your local server.
$ npx webhookcat listen 3000This creates a new URL, prints it together with a link to watch it in the browser, and forwards every request to http://localhost:3000. To forward the inbox you already have open, pass its Share link. Share in the web app shows the exact command.
$ npx webhookcat listen 3000 --inbox "https://webhookcat.com/#<id>/<key>"- Needs Node.js 22 or later. Nothing else is installed.
- The target can be a port, a host and port, or a full URL such as
http://localhost:8080/api. The sub-path and query are appended to it. - Method, headers and body are sent unchanged, apart from connection headers like
Host. Signature checks such asStripe-SignatureandX-Hub-Signature-256pass on your server. - The sender gets the response set in the web app (200 OK unless you change it), not your local server's response. Each forwarded request is printed with your server's status and timing.
- If the connection drops, the CLI reconnects and forwards anything that arrived in the meantime.
- Bodies are stored as text, so binary uploads such as images arrive altered.
Custom responses
Response in the web app sets what every request to your URL gets back. Use it to test how a sender retries after 429 or 500, or how it handles a slow endpoint.
- Status: any 2xx, 4xx or 5xx code. Redirects are refused.
- Content type: text, JSON or XML. HTML is refused, so a URL can never host a web page.
- Delay: up to 10 seconds.
- Headers: up to 10, limited to
X-*,Retry-After,Cache-Control,ETag,WWW-AuthenticateandRateLimit-*. - Body: up to 8 KB.
- CORS headers are on by default for browser testing. Turn them off to see how your app handles a blocked request.
- Slack's
url_verificationchallenge is always answered with the challenge, whatever response you set, so Slack accepts the URL as an Events API Request URL.
Signature checks
When a request carries a signature from Stripe, GitHub, GitLab, Slack, Shopify or Paddle, or from a sender that signs with Svix or Standard Webhooks such as Clerk and Resend, a Signature box appears under it. Paste the secret and WebhookCat says whether the signature matches. For signatures with a timestamp it also shows how long before arrival the request was signed, since most libraries reject requests older than five minutes, and Paddle's after five seconds.
- The check runs in your browser. The secret is never sent to WebhookCat or saved, and is forgotten when you close or reload the tab.
- Bodies over 64 KB are stored truncated, so their signatures can't be checked.
- Bodies are stored as text, so a body that isn't valid UTF-8 fails the check even with the right secret. Webhook payloads are JSON or form data, so this rarely matters.
Guides
Where to paste the URL, what each provider sends, and how to check its signature in your own code:
Limits
- The first 64 KB of each body is stored. Longer bodies are marked as truncated.
- The newest 100 requests per URL are kept. Older ones roll off, and the URL keeps working.
- Each URL accepts about 30 requests per 10 seconds. Requests over that get 429.
- Request history expires after 7 days of inactivity. Account inboxes keep their URL and response settings. Clear and Delete remove requests immediately.
Contact
Questions and privacy requests: support@webhookcat.com. Abuse reports: abuse@webhookcat.com, with the WebhookCat URL.