Replay

Replay resends a captured request without needing the original client to make it again. Two ways to do it, depending on how much control you need.

Replay Request (edit then send)

Right-click any transaction → Replay Request opens an editable request window (Compose): method, URL, headers, cookies, body. Edit anything before sending, then ⌘Return to send it. Useful for testing a variant of a real request — a different parameter, an expired token, a malformed body.

Batch Replay

For sending many requests at once — a load-test-lite or a multi-step flow:

• Queue up multiple captured requests
• Set a repeat count to run the whole batch N times
• Set a delay between items (ms) to pace requests instead of firing them all at once
• Optionally rewrite the host for every item in the batch — useful for replaying a whole recorded flow against staging instead of production without editing each request individually

Each attempt’s result (status, timing) is tracked so you can see which requests succeeded or failed across the run.