History
History stores local request snapshots so you can review previous runs and replay them.
What you do here
Section titled “What you do here”- browse previous request runs
- search history entries
- inspect request and response snapshots
- replay an earlier request
Most common keys
Section titled “Most common keys”History list
Section titled “History list”j/k: move through history entries/: open history searchr: replay the selected history entrye/Enter: open the selected history entryCtrl+P: open the command palette
History detail
Section titled “History detail”j/k: move between the request and response detail blocksh/l: switch betweenBodyandHeadersinside the selected blockCtrl+U/Ctrl+D: scroll the selected blocke: open the selected body viewerEsc: leave detail mode
Common commands
Section titled “Common commands”homeenvhistoryreplay
Quick examples
Section titled “Quick examples”Search history
Section titled “Search history”- Press
/. - Type part of the request name, path, method, status, or URL.
- Press
Enteron the matching entry.
Replay a request
Section titled “Replay a request”- Select the history entry.
- Press
r, or openCtrl+Pand runreplay.
Replays are created as temporary requests on Home. If history had redacted secrets, those secrets are omitted from the replayed request.
What detail mode shows
Section titled “What detail mode shows”History detail renders both sides of the exchange:
- a
Requestblock withBodyandHeaders - a
Responseblock withBodyandHeaders - summary metadata such as method, URL, auth type, status, duration, and size
Large bodies can be truncated in stored history, and sensitive headers are redacted before they are written.
For full command behavior, see Command Palette.