The fastest way to
test webhooks

Run whk tunnel 3000. The CLI creates a public endpoint and forwards every incoming webhook to your local port — method, headers, and body intact. No port forwarding or ngrok needed.

A tunnel streams HTTP requests from a public URL to your local machine. webhooks.cc creates the endpoint, receives the webhook, and replays it to localhost over SSE. Your local server handles it as if the sender called it directly.

Install @webhooks-cc/sdk, create an endpoint, and call client.requests.waitFor() with composable matchers. Assert on method, headers, or body fields. Works with Vitest, Jest, and any Node.js test runner.

Yes. Use the Send button in the dashboard and select a provider template. webhooks.cc generates realistic payloads and signature headers for 30+ providers so you can test your verification code end-to-end.

Send a webhook to your endpoint URL and open the dashboard. Each request shows method, headers, body (auto-formatted JSON and XML), query parameters, IP, and timestamp. Export as JSON or CSV.

Yes. The free plan gives you 50 requests per day, 7-day retention, unlimited endpoints, and full CLI, SDK, and MCP access. Every feature works on both tiers — the only exception is Teams (invite members, share endpoints), which requires Pro. Pro ($8/month) also raises the limit to 100,000 requests per month with 30-day retention.

The endpoint owner's. When you share an endpoint with your team, incoming webhooks count against your request limit. Every team member needs their own Pro plan to access shared endpoints, but usage is always tracked on the owner's account.

Install the MCP server with npx @webhooks-cc/mcp and add it to Claude Code, Cursor, VS Code, Codex, or Windsurf. Your agent creates endpoints, sends test webhooks, inspects requests, and replays them — through natural language.