API Toolkit

Webhook Payload Simulator

All tools

Fire a realistic webhook at your handler without waiting for the provider to send one.

How it works

Four simple steps

1

Pick a provider

GitHub, Stripe, Slack or Custom JSON.

2

Set the event

Type the event or type name you want to simulate.

3

Override if needed

Paste your own payload to replace the sample.

4

Replay with curl

Save payload.json and run the snippet against your endpoint.

Webhook Payload Simulator

About Webhook Payload Simulator

You are building a Stripe webhook handler on your laptop and do not want to trigger real payments just to receive an event. A sample payload and a curl command that posts it to localhost let you exercise the handler as often as you like.

Choose GitHub, Stripe, Slack or Custom JSON and the simulator fills in a starter payload: a push with one commit for GitHub, an event wrapping a payment intent for Stripe, an event_callback around an app_mention for Slack, and a minimal event object for Custom. The Event / type field changes the type inside the Stripe, Slack and Custom payloads, and for GitHub it sets the X-GitHub-Event header instead. Paste your own JSON into the override box to replace the sample entirely.

Below the payload, a replay snippet posts to $WEBHOOK_URL with a JSON content type, an X-Webhook-Provider header and provider extras: X-GitHub-Event for GitHub and a placeholder Stripe-Signature for Stripe. It sends the body with -d @payload.json, so save just the JSON part as payload.json and set WEBHOOK_URL in your shell. The Download button saves the payload and the snippet together, which is not valid JSON, so copy the payload section on its own. If your handler verifies signatures, compute a real one with the webhook signature signer and swap it in, or disable verification for local runs. The webhook verification walkthrough covers the receiving side.

Payloads are built in the page and nothing is posted anywhere; you run the curl command yourself.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

No. They contain a handful of representative fields so handlers can be exercised. Real events carry many more fields, so capture one from the provider dashboard or CLI when you need full fidelity.

The Stripe-Signature header in the snippet is a placeholder with no real digest. Sign the exact payload with your endpoint secret and replace the header, or bypass signature checks in local development only.

Nowhere from this page. The snippet uses a $WEBHOOK_URL shell variable, so export it, for example pointing at your local server, before running the command.

View more FAQs

Related tools

View all

Webhook HMAC Signer

Sign and verify GitHub, Stripe, and Slack webhook signatures locally.

Open

Webhook Replay Diff Lab

Compare webhook payload timelines, re-check HMAC digests, and spot idempotency gaps locally.

Open

JSONPath Playground

Query JSON with JSONPath and JMESPath-style paths side by side.

Open

GraphQL Studio

Format, validate, and cost-estimate GraphQL documents with cURL export.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools