HookspotDashboard
Menu

Test Webhooks Locally.

Receive webhooks on your laptop and see exactly what your app returned. Hookspot keeps each request for 14 days, ready to inspect and retry.

Free for 25,000 deliveries a month. No card needed.

See where each webhook goes, with a delivery status for every path.
Hookspot routes board: five sources wired to their local paths, with orders sent to two paths, a paused inventory route and a failing shipments route.

Start receiving webhooks locally

  1. Sign up

    Use GitHub, Google or email address.

  2. Create a route

    Name your webhook source and specify destination path. Copy source URL into the service that sends your webhooks.

  3. Run the CLI

    hookspot listen --forward-to http://localhost:3000
  4. Receive a webhook

    See the request and your app's response in Hookspot and your terminal.

    Follow the quickstart

Test your fix with the webhook that failed.

A failed webhook gives you a test case. Keep its payload, inspect the response and send it to your app again as you work on the fix.

Incoming webhooks1,284 stored

  • Delivered
  • Retried
  • Waiting

Webhook URLStores each webhook

Your laptop

hookspot listenconnected
/webhooks/orders200 OK
/webhooks/audit200 OK
The CLI is running. Hookspot stores each webhook, then forwards it to both paths.Your app answered 500 on /webhooks/orders, so Hookspot tries again.The third attempt worked.The CLI stopped. Hookspot still stores each webhook and marks its deliveries Skipped.The CLI is back. You click Retry, and the waiting webhooks reach your app.

Retry the webhooks you missed.

A webhook arrives while your laptop is off. Hookspot saves it and marks its delivery Skipped. Start hookspot listen when you're back, then click Retry to send it to your app.

Retry an offline delivery
A delivery skipped with No listener, selected under a banner that reads 1 delivery skipped: no listener received it, with its Fix it steps.

See why a delivery failed.

Open Attempts to see the response from each try. If your app returns a server error or can't be reached, Hookspot retries automatically, up to five attempts.

Automatic retries
Two attempts on one delivery: an Initial attempt that failed with 502 and a later System retry delivered with 200.

Test several paths with one webhook.

Send the same request to /webhooks and /webhooks/audit. Each path gets its own delivery and response, so you can see which one failed.

Send one webhook to several paths
Routes board with the Docs demo source routed to both /webhooks and /webhooks/audit, each with a last delivery of 200.
r

Fix your code. Press r.

Select the request in hookspot listen and press r to replay it. Compare your app's new response with the previous one, using the same webhook.

Replay a request
#2 ↻ #1  422 → 200  4ms → 1ms  orders · POST /webhooks/orders   20:35:15.890  -   "error": "missing customer_id"  +   "received": true

Every feature is included on Free.

Get 25,000 deliveries a month, 14 days of history and up to 3 members. Pro raises the limits for $19 a month.

Compare plans

Questions before you sign up

Can I try it before my app is ready?

Yes. Create a route, run hookspot listen and click Send test request in Hookspot. You'll see the request in your terminal. Add --forward-to when your app is ready to receive it.

Try it with a test webhook
Will it work with my webhook provider?

Yes, if your provider sends webhooks to a URL you choose and accepts Hookspot's reply. Providers that need your app's own response to confirm the URL are not supported. Slack is the exception, because Hookspot answers its URL check for a Slack source.

Slack's URL check
Will waiting webhooks arrive automatically?

Start hookspot listen, then click Retry in Hookspot. For several skipped deliveries, use Retry N skipped. Restarting the CLI alone does not resend them.

Can I debug webhooks with someone else?

Yes. Free includes up to 3 members in one organization, and Pro includes 25. Invite another developer to inspect the same requests, responses and delivery attempts.

Invite a member

See your first webhook arrive.

Install the CLI with npm (Node.js 18 or newer) or Homebrew.

Create a free account