WebhookForge: free online, no signup

1. Open the tool at webhookforge.vercel.app.
2. Paste your input — a raw JSON payload, headers, or a webhook URL you want to inspect.
3. Read the result below the box. Copy it out with the copy button.

That's the whole flow. There is no "create project" step and no dashboard to configure first.

• No signup: no email, no OAuth, no password.
• No paywalled result: the output you see is the full output, not a truncated preview.
• No rate-limit tricks: normal interactive use is fine; if you plan to hit it in a loop, run your own copy instead.

If you need guaranteed uptime or private hosting, treat the public instance as a convenience, not infrastructure.

Webhook debugging usually breaks on the boring stuff. A few things worth checking before you blame the tool:

• Content-Type. Most providers send application/json, but Stripe-style signed payloads and form-encoded senders (application/x-www-form-urlencoded) look different once parsed.
• Raw body vs parsed body. If you verify signatures, you need the *raw* bytes exactly as sent — re-serialising JSON changes whitespace and breaks the HMAC.
• Escaped JSON. Payloads copied out of a log viewer often arrive as a single escaped string. Unescape first, then paste.
• Timestamps. Providers mix Unix seconds, Unix milliseconds and ISO 8601. Check the provider's docs rather than guessing from the digit count.

For provider-specific header names and signature schemes, read that provider's webhook docs — those details change and are not worth memorising.

The tool is built to do its work in the browser wherever possible, so your input generally doesn't need to leave the page. Still, apply normal judgement:

• Don't paste live API keys, bearer tokens or signing secrets.
• Redact customer emails and payment identifiers if you're sharing a screenshot.
• For anything under a strict compliance rule, run the tool locally or use a sanitised sample payload.

If you need a formal guarantee about data handling, self-host rather than rely on a public instance.

WebhookForge is good for a quick paste-and-inspect loop. Reach for other tools when:

• You need a live receiving endpoint to capture deliveries over hours or days.
• You need replay of a provider's past events — most providers (GitHub, Stripe, Shopify) have a redelivery button in their own dashboard, which is more accurate than any third party.
• You want this in CI — script it with curl and jq instead of a browser tool.