Send That Webhook Again
When a delivery fails or a bug eats an event, the provider usually isn't going to resend it for you. Hookbase keeps the original payload, so you can replay a single delivery or thousands of them — as-is, edited, or pointed at a different destination entirely.
Replay Isn't Just "Try Again"
A plain retry sends the same thing to the same place and hopes for a different answer. Replay in Hookbase lets you change what gets sent and where it goes, using a payload that really happened. See how the webhook relay works for how those payloads get stored in the first place.
Replay a Single Delivery
Open any delivery in the history and send it again exactly as it was. The original event and its stored payload are reused, so what your endpoint receives is the real traffic, not a hand-written imitation of it.
Edit the Payload First
Change the body before it goes back out. Handy when you want to reproduce a variant of a real event — a different amount, a missing field, an unexpected status — without waiting for the provider to send one.
Override the Destination
Point the replay at a different destination in the same organization. Send production traffic at a staging endpoint, or redirect to a replacement destination while the original one is still being fixed.
One-Shot Transform Override
Apply a transform just for this replay. It is not saved back to the route, so you can test a new mapping against a real payload without changing what normal live traffic does.
Recover a Backlog, Not One Delivery
Outages don't break one webhook, they break every webhook that arrived while you were down. Bulk replay handles the batch in a single action, at whichever level makes sense for the mess you're cleaning up.
Replay Up to 100 Deliveries
Select deliveries from the history and resend them in one action, up to 100 at a time. This is the usual move after a destination outage: filter the failures, select them, replay.
Replay Up to 50 Events
Work at the event level instead. Replaying up to 50 events resends every delivery tied to those events, so a fan-out that hit several destinations gets reprocessed as a unit.
When You'll Actually Reach For It
Replay tends to earn its keep in three situations — and they all come down to having the original payload on hand.
Recover From a Downstream Outage
Your destination was down, deliveries failed, and retries ran out. Once the endpoint is healthy again, replay the affected deliveries in bulk instead of asking every provider to resend — most of them won't.
Debug a Filter or Transform Change
Changed a route's filter or transform and want to know what it does to real traffic? Replay historical payloads through it — with a one-shot transform override if you're still iterating — and inspect the result.
Re-Test After a Fix
Whatever made the delivery fail — a bad signature check, a 500, a schema mismatch — replay the exact same payload after the fix and confirm the endpoint now handles it, using the request that actually broke.
How Far Back You Can Replay
Replay depends on the stored payload, so it is bounded by how long that payload is retained — and that depends on your plan. Once the retention window passes, the payload is gone and there is nothing left to replay.
Free
7 days
of payload retention
Starter
30 days
of payload retention
Pro
90 days
of payload retention
Business
365 days
of payload retention
Need a longer window? Compare the tiers on the pricing page.
One Real Limitation: Transient Mode
Events processed in transient mode are never stored as payloads — only their metadata is kept. That is the point of the mode, and it is genuinely useful when the data is sensitive or the volume is enormous, but it means those events cannot be replayed at all. There is no body to resend. If replay matters for a given source, don't run it transient.
Why This Matters
Without stored payloads, a failed webhook is just a line in a log telling you something went missing.
Without replay
Hookbase
Stop Losing Webhooks You Already Received
Every delivery Hookbase handles is one you can look at, understand, and send again. Get started free — no credit card required.