Docs
Build on HookWatch
Everything the dashboard does is available over HTTP, and every route is also an MCP tool. Reference docs for both, with worked examples.
HTTP API The HookWatch HTTP API: workspace-key auth, JSON envelopes and error codes, endpoints, deliveries and attempts, replay/retry/analyze, and webhook ingest with HMAC signing. Read →MCP server Drive HookWatch from an AI assistant over MCP: ~48 tools across deliveries, endpoints, incidents and recovery, via local stdio (hookwatch mcp) or remote HTTP, authenticated by a workspace key. Read →CLI The hookwatch CLI: terminal dashboard (hookwatch), local-dev tunnel (hookwatch tunnel), and MCP server (hookwatch mcp), authenticated by a workspace key. Install via curl; configure via flags, env, or config.toml. Read →
Get started
Point an endpoint at HookWatch.
Capture a failed webhook, inspect it, and replay it once it’s fixed — then automate it over the API. Free during beta.