01
Inspect the capture
Review the available request, response, status, headers, body, and measured timing in the dashboard Traffic view.
Replay guide
Inspect. Edit. Send again.
Use captured HTTP traffic as a concrete debugging input while keeping the destination and possible side effects visible.
02
Choose and edit
Confirm the destination first, then deliberately change headers, query parameters, or the request body.
03
Send and compare
Replay the request and compare the resulting status, headers, body, and timing with the original capture.
A replay is another HTTP request.
Review the destination and payload before sending it—especially when the original request created, updated, charged, notified, or deleted something. Editing does not make a request idempotent.
Available destinations
- Your connected local route
- Another available project environment
- A deliberately selected custom target