features
Replay
Replay captured webhook requests to any target URL for debugging and testing.
Replay re-sends a captured webhook to any target URL. The killer use case: a customer reports a bug, you grab the exact failing payload from production, and replay it locally as many times as you need until your handler stops crashing — without waiting for the real provider to send another event.
How It Works
- Open the request you want to replay in the inspector
- Click Replay in the request detail panel
- Confirm or edit the target URL, method, headers, and body
- HookSense sends the request from its servers and shows you the response status, body, and latency
SSRF protection is active on all replays — internal IP ranges (RFC 1918, link-local, loopback, metadata services) are blocked. To target localhost, use the CLI instead, which forwards to your machine over the existing HookSense connection.
Edit Before Sending
Replay opens an editor pre-filled with the captured request. Tweak any field before firing:
- Target URL — your local server, staging, or a different production endpoint
- HTTP method — switch GET → POST or any verb
- Headers — add, remove, or rename keys (handy for impersonating different content types or auth)
- Body — JSON, form-encoded, or raw text; the editor preserves whitespace
Edits don't modify the original captured request — replay is non-destructive.
Repeat Mode
Need to load-test or check idempotency? Toggle Repeat in the replay dialog:
- Up to 50 repetitions per replay
- Configurable delay between sends (0–10s)
- Per-iteration response status, body, and latency
- Stop early at any time
Use cases: testing your handler's idempotency key, simulating duplicate-delivery scenarios, warming up caches before a load run.
Replay From the API
curl -X POST https://hooksense.com/api/endpoints/YOUR_SLUG/replay/REQUEST_ID \
-H "Content-Type: application/json" \
--cookie "hs_session=..." \
-d '{"targetUrl":"https://staging.example.com/webhooks","method":"POST"}'
See the API reference for full request/response schema.
Replay History
Every replay (one-shot or repeat-mode) is logged on the request's detail panel: target URL, response status, latency, and timestamp. The 10 most recent target URLs are remembered locally for autocomplete.
Plan Limits
| Plan | Replays |
|---|---|
| Catch (Free) | 5 per month |
| Hook | Unlimited |
| Sense | Unlimited |
Repeat-mode iterations each count as a single replay against your monthly quota.