Receive anything
Inspect methods, headers, query parameters, source IPs, JSON, text, forms, and binary bodies in one live view.
openwebhook.co
your unique url
⌁
Your webhooks will appear here
Requests are never stored on the server. Keep this tab open to receive them.
built for developers
Free webhook tester and inspector. Zero setup.
Test webhooks online and use OpenWebhook as a private request bin in seconds. No signup, no install, no configuration, and no credit card. Copy the URL above and send your first request.
free to useno accountno server-side history
Debug in real time
Requests appear instantly over a live SSE connection. Copy a reproducible cURL command or download the full event as JSON.
Local by design
Payloads are not kept on our server unless you opt in to a 24-hour encrypted share. Your browser keeps the latest 200 events locally and you control when they are deleted.
one-command test
From endpoint to payload in one request
Use your generated URL directly or append a path to organize providers such as GitHub, Stripe, or your local application.
curl -X POST \
'https://hooks.openwebhook.co/YOUR_UUID/github' \
-H 'content-type: application/json' \
--data '{"event":"push"}'Public CLI and MCP
Listen on localhost. No signup.
The first listen --port or mcp run prints a temporary URL and forwards it to 127.0.0.1. No account, token, or tunnel.
npm install --global openwebhook
openwebhook listen --port 3001OpenWebhook Pro
Permanent slugs, HTTPS forwarding, custom responses
Keep a stable URL, forward one webhook to many HTTPS destinations, choose the status returned to senders, and replay a body. The CLI already works; Pro is persistence.
developer guides
Payloads people actually look up
The exact request for checkout.session.completed, a GitHub push, Shopify orders/create, and a Twilio status callback. Then Zapier, Make, and n8n.
frequently asked
Before you send a request
Is OpenWebhook free?
Yes. The browser inspector, CLI, and MCP start without an account or payment details. A Pro plan is only for permanent slugs, HTTPS forwarding, and custom HTTP responses.
Do I need to install anything?
No. Open the page, copy your generated URL, and send an HTTP request. The optional CLI also starts without signup: npm install --global openwebhook && openwebhook listen --port 3001.
Does the CLI or MCP need an account?
No. openwebhook listen --port and openwebhook mcp print a temporary URL and pull events to your machine. Register only if you need a stable slug. The MCP server is on Smithery: https://smithery.ai/servers/openwebhook/openwebhook
Are webhook payloads stored on the server?
Not by default. Requests are relayed while your browser is connected, and history stays in IndexedDB on your device. If you choose Share, an encrypted copy is stored in Redis for 24 hours. We never receive the decryption key, which lives in the URL fragment.
Can I share a captured request?
Yes. Share uploads ciphertext only. Anyone with the complete link can decrypt it in the browser. The key never leaves the URL fragment, and the copy expires after 24 hours.
Which HTTP methods and payloads are supported?
You can send GET, POST, PUT, PATCH, DELETE, and other HTTP methods with JSON, text, form data, or binary payloads up to 1 MB.
