openwebhook.coOpen inspector →
developer guide

Replay a Webhook and Resend It to HTTPS Forwards

Edit a captured webhook body and resend it to your OpenWebhook Pro forwarding destinations without asking the provider to fire the event again.

By David Lorenzo García··5 min read

Once you have a real payload, you often need to send it again: a destination was down, a mapping was wrong, or you changed handler code. Asking Stripe or GitHub to recreate the event is slow and not always possible.

OpenWebhook Pro can resend a captured request to the HTTPS destinations you already configured. You can edit the JSON body first. The destination list is never taken from the browser; only the owner’s saved forwards are used.

Capture, then forward

  1. Create a custom slug and add one or more https:// destinations on the endpoint page.
  2. Keep the live view open (or use the CLI if the destination is local).
  3. Let the provider send the event, or POST a fixture yourself.
  4. Select the event, choose Edit body, change the JSON, then Resend to forwards.

The replay uses the original method, path, headers and query. A x-openwebhook-source: replay header marks the delivery. The edited body is not stored on the server.

Binary / base64 bodies cannot be edited or replayed. Add at least one destination or the resend button stays disabled.

A fixture you can replay

curl -X POST \
  'https://hooks.openwebhook.co/YOUR_SLUG/orders' \
  -H 'content-type: application/json' \
  -H 'x-example-event: order.paid' \
  --data '{"id":"ord_1","paid":true,"total":1990}'

Edit paid to false in the inspector and resend. Each destination should receive the new body. Delivery is best-effort: there is no durable retry queue on OpenWebhook’s side.

What replay is not

  • It does not let a client supply arbitrary destination URLs.
  • It does not persist the payload in MySQL.
  • It does not replace the provider’s own “resend” button when you need their signature recomputed against a new timestamp.

Use provider resend when you must re-test signature verification with a fresh Stripe-Signature or X-Hub-Signature-256. Use OpenWebhook replay when the body and headers you already captured are the input your forwards should see.

Related guides