History

Tigrister automatically saves every HTTP request you send. The History system allows you to easily access, review, and restore your past requests along with their responses.

Automatic Recording

When you send a request, both request and response data are automatically added to history. No manual saving required.

What Gets Saved

Each history entry contains the following information:

Request Data

  • Method & URL - The request target
  • Headers - Default and custom headers (raw)
  • Body - Raw body, body type, form-data
  • Params - Query parameters
  • Auth - Authentication settings
  • Binary File - Uploaded file info
  • Custom Schema - Contract validation schema

Response Data

  • Status - HTTP status code and text
  • Headers - Response headers
  • Body - Response content
  • Timing - DNS, TLS, TTFB durations
  • Size - Request/response sizes
  • Connection - IP, port, TLS info
  • Cookies - Set-Cookie headers

Raw vs Processed Data

History stores both raw (environment variables unprocessed) and processed (env vars replaced) request data. This means when you restore a request, variables are preserved and you can resend with current environment values.

Accessing History

The History section is located in the left sidebar. Click the section header to expand or collapse it.

History(42)
ClearSorted: Recent
GET/api/users/profile200
POST/api/auth/login401
PUT/api/users/123-
Method
HTTP method (GET, POST, etc.)
URL
Request URL (path portion)
Status
Response status code or "-" (on error)

Sorting Options

You can sort the history list in two ways. Click the "Sorted:" button to toggle between sorting modes.

Sort ModeDescriptionUse Case
RecentNewest request first (default)Finding your most recent requests
URLAlphabetical by URLGrouping requests to the same endpoint

Opening History Items

When you click a history item, it opens in a new tab with all request and response data loaded.

1

Click the Item

Click any row in the history list.

2

New Tab Opens

The request data is automatically loaded into a new tab. The tab name is "METHOD URL".

3

Response is Displayed

The saved response is automatically loaded. Timing, headers, cookies, and all details are visible in the Response panel.

Duplicate Tab Prevention

If you click the same history item again, a new tab won't be created. Instead, the existing tab is activated. This prevents multiple copies of the same request.

Deleting Items

Delete Single Item

Hover over a history item to reveal the X button on the right side. Click it to delete only that item.

GET/api/users200

Clear All

Click the "Clear" button to delete all history items. This action cannot be undone.

Confirmation Dialogs

Both delete actions show a confirmation dialog. If you check "Don't ask again", future deletions won't require confirmation. This setting can be reset in Settings.

Empty State

If you haven't sent any requests yet or if history has been cleared, you'll see this:

No requests yet

Send a request to see history

Tips

💡Quick Debugging

When an API call doesn't work as expected, open a previous successful request from history to compare.

💡Response Comparison

Compare responses from requests to the same endpoint with different parameters by opening multiple history items.

💡URL Sorting

Use "URL" sorting to see all requests to a specific endpoint grouped together.

💡Save to Box

For frequently used requests, save them to Box instead of relying on history. Box items are permanent and won't be auto-deleted.

History vs Box

History and Box serve different purposes:

FeatureHistoryBox
SavingAutomatic (every request)Manual (user saves)
Limit100 entries (FIFO)Unlimited
PersistenceAuto-deleted when limit reachedPermanent
ResponseSavedNot saved
Use CaseReview past requestsStore frequently used requests