History tracks every API request you execute, storing the request configuration and response details for future reference.

Quick Start

Execute Requests

Send requests as you normally would - they're automatically saved to history.

Open History

Click the History tab in the sidebar.

Browse Past Requests

View all executed requests in reverse chronological order (newest first).

Re-run or Inspect

Click on a history entry to view details or re-run the request.

Viewing History

History List

The history panel shows:

Method badge: HTTP method with color coding
Request URL: Full request URL
Status code: Response status (200, 404, 500, etc.)
Response time: How long the request took (in milliseconds)
Timestamp: When the request was executed

Display format:

GET  https://api.example.com/users/123
200 OK • 245ms • 2 minutes ago

Sorting

History entries are sorted by execution time:

Newest requests appear at the top
Scroll down to load older entries (50 items per page, loads more on scroll)
Search to find specific requests quickly

Using History Entries

View Details

Click Entry

Click on any history entry to view full details.

Inspect Request

View the exact request configuration:

URL and method
Headers sent
Query parameters
Request body
Authentication used

Inspect Response

View the response:

Status code and message
Response headers
Response body
Response time and size

Re-run a Request

Open Entry

Click on the history entry.

Click Re-run

Click the Re-run or Send button.

View New Response

The request executes again and a new history entry is created.

Dynamic Variables

Re-running a request uses current variable values, not the values from when it was originally executed.

Move to Collection

Right-click a history entry and select Move to Collection to save it as a permanent request in a collection.

Managing History

Delete Single Entry

Hover over the history entry
Click the trash icon
Entry is removed from history

Clear All History

Click Clear All button
Confirm the action
All history entries for the current workspace are deleted

Cannot Undo

Deleting history entries is permanent and cannot be undone.

Search History

Use the search box to filter history:

Search by URL
Search by HTTP method
Results update as you type

History Details

What's Saved

Request Information:

HTTP method
Complete URL as it was sent
All headers sent
Query parameters
Request body
Authentication used
Resolved variable values (the actual values used at execution time)

Response Information:

Status code and message
Response headers
Response body
Response time
Response size
Timestamp

Scripts:

Script source code is stored in the history snapshot

Script Results Not Stored

Only the script source code is saved in history. Console output and test results from script execution are not stored — re-run the request to see test results again.

What's Not Saved

Draft changes (only committed requests)
Cancelled requests
Failed requests (no response received, e.g. network errors)

History Retention

Storage Limits

History entries are subject to retention limits per workspace:

Setting	Default
Maximum entries	500 per workspace
Maximum age	30 days

When either limit is exceeded, the oldest entries are automatically removed.

Local Storage

History is stored locally on your device
Persists after app restart
Independent per workspace
Does not sync across devices

Right-click a history entry for these options:

Action	Description
Open	Open the history entry in a read-only tab
Move to Collection	Save as a permanent request in a collection
Delete	Remove the history entry

Use Cases

Debugging

View past requests to:

See what was actually sent (including resolved variables)
Compare responses over time
Identify when an API started failing
Reproduce errors

Testing

Use history to:

Re-run tests without reconfiguring
Compare responses between environments
Verify consistent API behavior
Track response times

Tips

Review before re-running: Check the request details before re-running to ensure variables have correct values
Clear periodically: Remove old history to keep the list manageable
Use search: Quickly find specific requests instead of scrolling
Save important requests: Move history entries to a collection if you want to keep them permanently
Check timestamps: Verify when errors started occurring

Edge Cases

Deleted Requests

If the original request has been deleted:

History entry still exists
You can view the details
Re-running sends the request without saving to a collection

Offline Execution

Requests executed offline:

Not saved to history until they complete
Failed requests (no connection) not saved

History