Replay запросов — Тестирование Edge-Case сценариев
Мгновенная отладка веб-хуков без туннелей
Replay lets you re-send any captured webhook request to your local server with a single click — preserving the original payload, headers, and HTTP method. It's the fastest way to verify how your endpoint handles retries, malformed bodies, unexpected content types, and idempotency keys without touching the source system.
Error Handling
Simulate 5xx Failures
Crash your server intentionally, then hit Replay to confirm your code returns a proper 500 with a JSON error body. Hookly logs the response status, duration, and full response headers so you can audit your error path line by line.
Retry Logic
Validate Exponential Backoff
Replay the same Stripe checkout.session.completed event three times with increasing delays to verify your retry queue respects idempotency keys. Watch Hookly's timeline show each attempt's timestamp, latency, and status code side by side.
Edge Cases
Test Malformed Payloads
Edit the replayed request body to inject truncated JSON, missing required fields, or an unexpected Content-Type header. Confirm your validator rejects the payload gracefully before it reaches production.
How to Use Replay
Every captured request in Hookly's feed carries a Replay button. Click it, choose your target environment, and the request fires immediately — or schedule it for a future window to simulate delayed webhook deliveries.
Step 1
Select a Captured Request
Open the request detail drawer from the feed. The full payload, all headers (including X-Stripe-Signature or X-Hub-Signature-256), and the original timestamp are displayed in read-only panels.
Step 2
Configure Replay Options
Choose the target URL (localhost:3000/webhooks, your staging endpoint, or a custom address). Optionally edit the body, swap headers, or change the HTTP method. Set a delay of 0 s for instant replay or up to 300 s for deferred delivery.
Step 3
Fire and Inspect
Hit the Replay button. Hookly forwards the request, captures the response, and logs it as a new entry tagged "replay" so you can distinguish it from organic traffic. Drill into response metrics — status, body, duration, and cookies.
UI Showcase
The Replay button lives inside each request's detail drawer, right next to the raw payload viewer. One click opens the replay configuration panel where you can adjust the target, delay, and request body before firing.
The replay panel preserves the original request's Content-Type, signature headers, and method. You can override any field inline — for example, changing application/json to text/plain to test your parser's fallback branch — then send without leaving the drawer.
Replay запросов — Тестирование Edge-Case сценариев
Мгновенная отладка веб-хуков без туннелей
Replay lets you re-send any captured webhook request to your local server with a single click — preserving the original payload, headers, and HTTP method. It's the fastest way to verify how your endpoint handles retries, malformed bodies, unexpected content types, and idempotency keys without touching the source system.
Error Handling
Simulate 5xx Failures
Crash your server intentionally, then hit Replay to confirm your code returns a proper 500 with a JSON error body. Hookly logs the response status, duration, and full response headers so you can audit your error path line by line.
Retry Logic
Validate Exponential Backoff
Replay the same Stripe checkout.session.completed event three times with increasing delays to verify your retry queue respects idempotency keys. Watch Hookly's timeline show each attempt's timestamp, latency, and status code side by side.
Edge Cases
Test Malformed Payloads
Edit the replayed request body to inject truncated JSON, missing required fields, or an unexpected Content-Type header. Confirm your validator rejects the payload gracefully before it reaches production.
How to Use Replay
Every captured request in Hookly's feed carries a Replay button. Click it, choose your target environment, and the request fires immediately — or schedule it for a future window to simulate delayed webhook deliveries.
Step 1
Select a Captured Request
Open the request detail drawer from the feed. The full payload, all headers (including X-Stripe-Signature or X-Hub-Signature-256), and the original timestamp are displayed in read-only panels.
Step 2
Configure Replay Options
Choose the target URL (localhost:3000/webhooks, your staging endpoint, or a custom address). Optionally edit the body, swap headers, or change the HTTP method. Set a delay of 0 s for instant replay or up to 300 s for deferred delivery.
Step 3
Fire and Inspect
Hit the Replay button. Hookly forwards the request, captures the response, and logs it as a new entry tagged "replay" so you can distinguish it from organic traffic. Drill into response metrics — status, body, duration, and cookies.
UI Showcase
The Replay button lives inside each request's detail drawer, right next to the raw payload viewer. One click opens the replay configuration panel where you can adjust the target, delay, and request body before firing.
The replay panel preserves the original request's Content-Type, signature headers, and method. You can override any field inline — for example, changing application/json to text/plain to test your parser's fallback branch — then send without leaving the drawer.