Request History
Rostyman tracks every request you send in two places: a global history panel in the sidebar (all requests, across all collections) and a per-request History tab inside each saved request's builder (all runs of that specific request). Both surfaces share the same underlying data but offer different views and tools.
Global History Panel
Click the Clock icon in the left sidebar to open the global history panel.
Three Sub-tabs
| Tab | Contents |
|---|---|
| Requests | Every HTTP request sent from any tab in the workspace |
| Mock | Incoming requests received by the Mock Server |
| Jobs | Scheduler job runs (from all scheduled jobs) |
Requests Sub-tab
Search Bar
A search input at the top of the panel filters the list by URL or HTTP method as you type. Press the × button to clear the filter.
Entry Format
Each entry in the list shows:
- Method badge — color-accented (GET, POST, DELETE, etc.)
- Status code — color-coded green/amber/red
- Relative time — "5s ago", "3m ago", "2h ago", "1d ago"
- URL — truncated to fit, full URL visible on hover
- Response time and size — shown below the URL (e.g. "145ms · 2.3KB")
- Environment — name of the environment active when the request was sent (if any)
Opening a History Entry
Click any entry to open it in a new request tab. The tab is pre-populated with:
- The full request (method, URL, headers, params, body, auth, pre-request script, test script)
- The historical response (status, headers, body) displayed in the response panel
This lets you re-inspect a past response or re-send the request with modifications.
Deleting an Entry
Hover over an entry to reveal a trash icon. Click it to delete that single entry from history.
Clear All
Click Clear in the panel header to remove all request history for the current workspace. This action is immediate and cannot be undone from the panel (use a database backup if needed).
Per-Request History Tab
Inside any saved request, the History tab (next to Tests and Code tabs in the request builder) shows all historical runs for that specific request.
Toolbar
| Button | Action |
|---|---|
| Trends (TrendingUp icon) | Toggle the sparkline chart showing status codes over time |
| Filter (Filter icon) | Show/hide the status filter bar |
| Compare (GitCompare icon) | Enter diff mode — select two entries to compare them side by side |
| Export CSV (Download icon) | Download history as a CSV file with timestamp, method, URL, status, time, size, environment |
| Clear (Trash icon) | Delete all history for this request |
Status Filter Bar
When the filter bar is visible, filter buttons narrow the list:
| Filter | Shows |
|---|---|
| All | Every entry |
| 2xx | Successful responses (200–299) |
| 3xx | Redirects (300–399) |
| 4xx | Client errors (400–499) |
| 5xx | Server errors (500–599) |
| Error | Network failures (no status code) |
Entry Format
Each entry in the per-request history shows:
- Timestamp of the run
- HTTP status code (color-coded)
- Response time (ms)
- Response size
- Environment name used at the time
- Pin / Unpin icon
Pinning Entries
Click the Pin icon on any entry to pin it. Pinned entries:
- Appear at the top of the list, above all unpinned entries
- Are never auto-deleted (normal entries may be pruned)
- Persist across sessions (stored in the settings database)
Click the Unpin icon to move an entry back to chronological position.
Viewing a Historical Response
Click any entry to load that run's response into the response panel. The request builder is also populated with the exact URL, headers, body, and auth used in that run, so you can see exactly what was sent.
Response Diff Viewer
To compare any two historical responses side by side:
- Click the Compare (GitCompare) button to enter diff mode
- Click the first entry — it is highlighted as "A"
- Click a second entry — a full-page diff panel opens showing both responses
The diff panel shows both response bodies with additions highlighted in green and removals in red. Close the diff view with the × button to return to the list.
Trends Sparkline
Toggle Trends to see a small chart above the entry list showing the distribution of status codes across all runs. Use this to quickly spot when an API started returning errors.
Schema Change Detection
Whenever the JSON structure of a response changes between the two most recent runs, a Schema Changed banner appears at the top of the History tab with an orange warning icon. It lists:
- Added fields (green) — new keys that appeared in the response
- Removed fields (red) — keys that disappeared
- Changed types (amber) — fields whose type changed (e.g.
string → number)
The banner can be dismissed with the × button. It re-appears automatically if the schema changes again on the next send.
What Gets Saved Per Entry
| Field | Saved |
|---|---|
| Method, URL, params | Yes |
| Request headers | Yes |
| Request body + body mode | Yes |
| Auth configuration | Yes |
| Pre-request and test scripts | Yes |
| Response status + status text | Yes |
| Response headers | Yes |
| Response body | Yes |
| Response time (ms) | Yes |
| Response size (bytes) | Yes |
| Environment name | Yes |
| Timing breakdown | Yes |
| Timestamp | Yes |
History vs Auto-save
| Feature | Auto-save | History |
|---|---|---|
| Trigger | Every 30 seconds (in-progress changes) | When a request is actually sent |
| What it saves | Current tab state including unsaved edits | Request + response pair from the actual send |
| Scope | Per tab | Per saved request (or global for unsaved tabs) |
| Unsaved requests | Yes | Global history only (no per-request tab) |