Docs
Learn WebhookHQ.
Capture your first webhook in five minutes, then learn endpoints, forwarding, signatures and replay. Reference for the whq CLI, the REST API and the MCP server.
Start here · 5 minutes
Get started
In about five minutes you'll have a webhook URL, see your first webhook arrive, read it in full, forward it to a server or your laptop, and send it again.
- 1Try it without an account
- 2Sign up and create an endpoint
- 3Send a test webhook
- 4Inspect it
- 5Forward it
Guides
How each part of WebhookHQ works.
-
Endpoints
An endpoint is a URL you give to Stripe, GitHub or any other service: every request it receives is captured, shown live, and kept for your plan's retention so you can search it, copy it and send it on.
-
Forwarding
Forwarding sends every webhook an endpoint captures on to your own servers, retries the ones that fail, and shows every attempt, so you can see exactly what your server received and answered.
-
Signatures
Add a provider's signing secret to an endpoint and every webhook shows whether its signature is valid, and if it isn't, why, so you can find the bug in your own verification code.
-
Replay
Send any captured webhook again, unchanged or edited, to your laptop, one of your destinations or any public URL, as often as you like, and see what your server answered each time.
-
Teams and access
Your organization holds the plan, the members and the workspaces; workspaces hold the endpoints. This page covers who can see and change what, how people join, and how to give the CLI, scripts and outsiders access.
-
Plans and limits
What each plan includes, what counts as an event, and what happens when you reach the monthly limit: in short, nothing is lost, but events past it are hidden until you upgrade.
Reference
Every command, request and tool.
-
CLI
whqdelivers an endpoint's webhooks to an app running on your machine, replays captured webhooks into it, and lets you (or your coding agent) find, inspect and wait for webhooks from the terminal. It's built only for webhooks: it isn't a general tool for putting websites on the internet. -
API
Manage endpoints and read events from your own code: CI pipelines, scripts, dashboards. Reading endpoints and events works on every plan (it's what the CLI uses); creating, renaming and deleting endpoints is on the Pro plan and above.
-
MCP
WebhookHQ's MCP server lets a coding agent find, inspect, replay and wait for your webhooks while you debug: "find the last failed Stripe event and replay it to localhost after my fix". It works with any client that speaks the Model Context Protocol over HTTP, on every plan.