History

History

Getman records every request you send, automatically. History lives in the HISTORY tab of the side menu.

How it works

• Automatic: every send (success or failure) is recorded — there's no "save to history" button.
• Newest first: the most recent request is at the top.
• De-duplicated: entries are deduped by method + URL + body. Sending the same request again moves it to the top rather than creating a duplicate. (Header-only differences don't dedupe.)
• Templated: history stores the un-resolved request ({{variables}} intact), so you can re-send a past request under a different Environments and Variables.
• Bounded: the list is capped by the history limit Settings (default 100). Lowering the limit trims older entries.

Using history

• Open an entry: tap a row to open it in a new unlinked tab (a scratch copy — editing it won't change anything saved).
• Each row shows the URL, a colour-coded method badge, and (if captured) the status code.

Saving responses in history

A Settings, SAVE RESPONSE, controls whether response bodies are stored alongside history entries (off by default — only request metadata is kept). Very large bodies are capped on disk regardless.

Clearing history

History can be cleared from the app's data controls. (Writes to history happen only through the send pipeline — the list is read-only in the UI otherwise.)

Related

• Keep requests permanently in Collections.
• Re-running under different setups: Environments and Variables.