HookspotOpen the app
Menu

Get webhooks on your laptop in four steps.

Hookspot gives you a webhook URL. While the CLI runs, each webhook reaches the app on your laptop, and you can see what arrived, what your app answered, and send it again.

Create a free accountSee the four steps

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

One webhook: its headers and body, and where Hookspot forwarded it.
Hookspot request panel for an order.created request: its timeline shows it received, routed to two paths and delivered to both, above the JSON body.

Set up in four steps

  1. Sign up

    Use GitHub or Google, or an email address you confirm. Then name your organization.

  2. Create a route

    Name a source and pick the path in your app, like /webhooks/orders. You get a webhook URL to paste into the service that sends webhooks.

  3. Run the CLI

    Install it, approve the login in your browser, then start forwarding to your app.

    npm install -g @hookspot/clihookspot loginhookspot listen --forward-to http://localhost:3000

  4. Send a test webhook

    Click Send test request in the app. The webhook shows up there and in your terminal.

When something goes wrong.

Hookspot stores each webhook, so you can send it again if your app answers with an error or the CLI is off.

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 its deliveries wait as CLI offline.The CLI is back. You click Retry, and the waiting webhooks reach your app.

Webhooks wait while the CLI is off.

Hookspot stores each one and marks its delivery CLI offline. Start hookspot listen, then click Retry.

Retry an offline delivery
A delivery skipped as CLI offline, selected under a banner that reads 1 delivery skipped: no CLI was listening, with its Fix it steps.

Failed deliveries try again.

If your app answers with a server error or can't be reached, Hookspot tries again, up to five attempts. The Attempts tab lists each one.

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

One webhook, several paths.

Route one source to more than one path, like /webhooks and /webhooks/audit. Each path gets its own delivery.

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

Press r to replay.

Changed your handler? Select the request in hookspot listen and press r. The CLI sends it to your app again and shows what changed.

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

Start on the Free plan.

Pro costs $19 a month and raises the limit to 250,000 requests a month.

Compare plans

Questions before you sign up

What do I install?

Only the Hookspot CLI.

Does it work with any service that sends webhooks?

Yes, if it sends webhooks to a URL you give it. The service gets Hookspot's reply, not your app's, so a service that needs your app's answer to confirm the URL won't work.

What happens while my laptop is off?

Hookspot keeps receiving and storing webhooks, and their deliveries wait as CLI offline. Run hookspot listen again, then click Retry in the app.

How long are webhooks kept?

14 days on the Free plan and 60 days on Pro.

Send your first webhook to your laptop.

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

Create a free account