Hooklistener is a webhook debugger that captures every request to an HTTPS endpoint so you can inspect payloads, troubleshoot silent failures, and replay requests to any environment. Your coding agent can do the same over MCP. Fix broken integrations before they hit production. Just need to send a test event? Try our webhook tester tool.
Step 1 · Incoming webhook
Step 2 · Stored & inspected
The payload is preserved based on your plan's retention window, signature-checked, and streamed into the live inspector so you can replay or diff it later.
{
"event": "payment_intent.succeeded",
"customer": "cus_9J4Z",
"amount": 2400
}
Step 3 · Replay anywhere
Production API
200 OK
Response 127ms
Local tunnel
Replay queued
Awaiting ngrok
Provisioning a live anonymous endpoint for this browser tab
Most failing webhooks come down to a payload you did not expect, a signature that does not match, or a handler that errors. Work through them in this order.
Point the provider at the URL from the tool above, or send a test event yourself. Anonymous URLs last up to 24 hours and keep up to 500 requests. Claim one into a free account to carry its captured requests over.
curl -X POST "YOUR_WEBHOOK_URL" \
-H "Content-Type: application/json" \
-d '{"id": "evt_test_123", "type": "payment_intent.succeeded"}'Check the Content-Type, the signature header (Stripe-Signature, X-Hub-Signature-256) and the event id, then compare the JSON body field by field with what your handler parses.
Signature verification is built in for Stripe, GitHub and Slack once you store the signing secret (paid plans). For other providers, recompute the HMAC over the raw body in your handler. See webhook signing and HMAC verification.
Run your handler locally and open a tunnel to it with a free account, then re-trigger the event from the provider or replay a failed webhook you already captured. Replay is on Pro and above.
hooklistener login
hooklistener tunnel --port 3000Just need an address that receives webhooks? Use the free webhook listener; testing a new integration? Try the webhook tester.
Move from one-off bins to a production-grade webhook platform with replay, forwarding, and monitoring built in. Compare features side-by-side and migrate in minutes.
Persist webhook history for 14+ days, search instantly, and replay to any environment.
Tunnel captured webhooks to your local server with the CLI.
Invite collaborators, mask secrets, and stay audit-ready—no public bins or shared tokens.
Can Hooklistener replay captured payloads?
Yes. Captured webhooks stay in your history (1 day on Free, up to 90 days on Scale) and can be replayed to any environment with an edited body. Replay is on Pro and above.
How does Hooklistener stack up to webhook.site?
Webhook.site's free URLs need no signup, expire after 7 days and accept a capped number of requests (50 on its pricing page, 100 in its docs); forwarding through Custom Actions and localhost forwarding with its CLI are paid-plan features (webhook.site/pricing and docs.webhook.site, checked November 2026). Hooklistener's CLI tunnel to localhost works on the Free plan, and it adds replay with edited bodies (Pro), a hosted MCP server, and up to 90-day retention on Scale (webhook.site keeps paid-plan data for up to 365 days).
Is there a cost to start debugging?
No. The Free plan includes one Debug Endpoint with an HTTPS URL, live header and body inspection, one day of history, MCP server access and the CLI tunnel, with no credit card. The anonymous debugger on this page needs no signup at all. Upgrade to Pro for 14-day retention, a static tunnel subdomain and replay.
Trusted by engineers at
Create a new endpoint with just a few clicks to start receiving webhooks.
Webhook URL
Forward webhooks to your local environment or analyze them directly in Hooklistener.
Add a monitor that alerts you by email, Slack, or a signed webhook when expected webhooks stop arriving.
A repeatable process for diagnosing and fixing webhook issues — whether you're dealing with a silent failure, a signature error, or a schema change from a third-party provider.
Point your webhook source at a HookListener endpoint. The next delivery lands in your history with full headers, body, status code, and latency — no guesswork about what was actually sent.
Open the request and check the JSON body against the schema you expect. Mismatched field names, wrong types, or missing nested keys show up immediately with syntax highlighting.
Check the raw headers tab for HMAC signatures (e.g. X-Hub-Signature-256, Stripe-Signature) and compare against your secret. A signature mismatch here means the payload was altered in transit or the wrong secret is configured.
Once you've identified the issue, hit Replay to forward the exact original request to your localhost URL. No need to retrigger the source event — iterate on your handler until the response is correct. Replay is on Pro and above.
After deploying a fix, replay the same payload to production and compare the response side-by-side. Confirm the status code changed from 500 to 200 before closing the incident.
Hooklistener is a webhook debugger for developers and their AI coding agents. A Debug Endpoint captures every incoming request with headers, body, query, IP, and TLS details so you can inspect it live, replay it to any environment, and share a read-only link with a teammate. An MCP server lets Claude Code, Cursor, or Codex do the same work from the terminal, Monitors alert you when webhooks stop arriving, Email Inboxes capture test emails and (on paid plans) turn incoming email into webhooks, and the CLI tunnels live traffic to localhost.
Yes. The Free plan includes one Debug Endpoint with one day of request history, one Email Inbox, one Monitor, and full MCP server access, with no credit card required. You can also use the anonymous debugger on this page without signing up. Try Hooklistener for free or compare plans.
Yes. Hooklistener ships an MCP server with 67 tools, so Claude Code, Cursor, or Codex can create endpoints, wait for the next webhook, read the captured payload, replay it, and diagnose why your handler failed, all from the terminal. Set up the MCP server.
Hooklistener, ngrok, Webhook.site, and RequestBin can all receive webhook payloads from SMS APIs such as Twilio. Hooklistener captures the full headers and body at a hosted URL, forwards them to localhost with its CLI, and can replay a captured request (Pro).
Use Hooklistener to capture the Twilio payload, then forward it live to localhost with the CLI tunnel or replay it to your localhost URL (Pro). You can inspect the X-Twilio-Signature header and check it against your auth token in your own handler; built-in signature verification covers Stripe, GitHub and Slack. Twilio webhook debugging guide.
Yes. Hooklistener generates a free public HTTPS URL that captures any request, letting you test without deploying. Custom responses let the endpoint return the status, headers, body, and latency you choose, so you can exercise retry logic on purpose.
The Free plan covers sporadic debugging and personal projects. Pro adds 25,000 requests a month, 10 endpoints, 14-day retention, a static CLI tunnel subdomain, and replay for day-to-day integration work. Production adds 250,000 requests a month, 30-day retention, shared workspaces, and 5 seats for teams that debug the same integrations together, and Scale covers high-volume senders with 2,000,000 requests a month and 90-day retention. See pricing.
Pick by the job: a hosted capture URL to see exactly what the SMS provider sent, or a tunnel when the request has to reach code running on your machine.
Start for free and scale as your needs grow. No credit card required.
Get started for free