How to Use WebhookForge

1. Go to https://webhookforge.vercel.app.
2. Paste your input into the text area — a raw JSON body, a captured request, or the endpoint you want to work with.
3. Read the output panel. Copy the result with the copy button, or edit the input and it re-runs as you type.

That's the whole flow. There is no signup step, no API key, and nothing to configure before your first run.

If you don't have a payload handy, grab one from the source:

• Stripe: Dashboard → Developers → Webhooks → click an event → *Event data* (JSON).
• GitHub: Repo → Settings → Webhooks → your hook → *Recent Deliveries* → Request body.
• Shopify: Notifications → webhook → check the delivery log, or send a test notification.
• Your own app: log the raw body before parsing, e.g. in Express with app.use(express.raw({ type: '*/*' })) and console.log(req.body.toString()).

Paste the raw body, not the pretty-printed version from a terminal — escaped quotes and truncated logs are the two most common reasons a payload won't parse.

• "Unexpected token" / invalid JSON: you probably copied a log line with a timestamp prefix, or the body is form-encoded (a=1&b=2) rather than JSON. Strip the prefix and re-paste.
• Trailing commas: valid in JavaScript object literals, invalid in JSON. Remove them.
• Escaped payload: if your input looks like "{\"id\":1}", it's a JSON string containing JSON. Unescape it once before pasting.
• Huge payloads: very large bodies can be slow to render in any browser tool. Trim to the section you care about.
• Secrets: payloads often contain emails, customer IDs, or tokens. Redact anything you wouldn't paste into a shared doc — even though processing happens client-side, that's a good habit for any online tool.

WebhookForge is for the inspect-and-iterate part of webhook work: understanding an unfamiliar payload, checking a shape before you write a parser, or sanity-checking what a provider actually sent.

It is not a replacement for:

• receiving live traffic on localhost — use a tunnel like ngrok http 3000 or cloudflared tunnel;
• signature verification against a real secret — do that server-side with your provider's SDK (e.g. stripe.webhooks.constructEvent);
• retry and delivery monitoring — that lives in your provider's dashboard.

Use the browser for the fast loop, your server for anything involving secrets or production traffic.