Box (Saved Requests)

Box is your personal collection of saved requests. Unlike History (which automatically records every request), Box lets you intentionally save requests you want to keep for future use. Think of it as your request library.

Permanent Storage

Unlike History which auto-deletes old entries, Box items are permanent. They stay until you explicitly delete them.

What Gets Saved

When you save a request to Box, the following data is stored:

Method & URL
HTTP method and full URL
Headers
All custom headers
Params
Query parameters
Vars
Request variables
Body
Body content and type
Auth
Authentication settings
Assertions
Response validation rules
Custom Schema
Contract validation schema

What's NOT Saved

Response data is not saved in Box. Box stores request templates, not complete request/response pairs. For response history, use the History feature instead.

Saving a Request

There are two scenarios when saving to Box:

New Request (First Save)

  1. Configure your request (URL, method, headers, body, auth, etc.)
  2. Click the Save button in the request toolbar
  3. A new item appears in the Box section with an auto-generated name
  4. The tab is now "linked" to this Box item

Existing Request (Update)

  1. Open a saved request from Box
  2. Make your changes
  3. Click Save again
  4. The existing Box item is updated (no duplicate created)

Auto-Generated Names

When saving without a custom name, Tigrister generates a name in the format METHOD hostname/path. For example: GET api.example.com/users

Accessing Box

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

Box(5)
Sorted: A-Z
GETapi.example.com/users
POSTCreate New User
Authentication Test

Auto-named items show the method prefix (e.g., "GET api.example.com/users")

Custom-named items show only the name (e.g., "Authentication Test")

Sorting Options

Click the "Sorted:" button to toggle between sorting modes.

Sort ModeDescriptionUse Case
A-ZAlphabetical by name (default)Finding requests by name
RecentMost recently modified firstFinding recently used requests

Opening Saved Requests

Click any item in the Box section to open it.

1

Click the Item

Click any saved request in the Box list.

2

New Tab Opens

A new tab is created with all saved request data (URL, method, headers, body, auth, etc.).

3

Tab is Linked

The tab is automatically linked to the Box item. Future saves will update this item.

Duplicate Tab Prevention

If you click a Box item that's already open in a tab, Tigrister switches to that existing tab instead of creating a duplicate.

Context Menu

Hover over a Box item to reveal the three-dot menu (⋮). Click it to access these actions:

Rename

Change the item's display name. The item becomes editable inline. Press Enter to save or Escape to cancel.

Duplicate

Create a copy of the request. The new item is named Original Name (copy). Useful for creating variations of the same request.

Delete

Permanently delete the request from Box. A confirmation dialog appears (can be disabled with "Don't ask again").

Rename
Duplicate
Delete

Tab Linking

When you open a Box item or save a new request, the tab becomes "linked" to that Box item.

How Linking Works

  • Opening a Box item creates a linked tab
  • Saving a new request links the current tab to the new Box item
  • Clicking Save on a linked tab updates the Box item
  • Renaming a Box item updates the linked tab's name

Dirty State Detection

Tigrister tracks changes to linked tabs. If you modify a request after opening it from Box, the system knows there are unsaved changes. This helps prevent accidental data loss.

Empty State

If you haven't saved any requests yet, you'll see this:

No saved requests

Click Save to add requests here

Tips

💡Descriptive Names

Use descriptive names like "Create User" or "Login with OAuth" instead of auto-generated names. It makes finding requests much easier.

💡Duplicate for Variations

Use Duplicate to create variations of the same request. For example: "Create User (Admin)" and "Create User (Guest)".

💡Use Environment Variables

Store URLs with environment variables like {{baseUrl}}/users. This makes your saved requests work across different environments.

💡Box vs Projects

For team collaboration or API documentation, consider using Projects instead of Box. Projects support OpenAPI specs and structured organization.

Box vs History

Box and History serve different purposes:

FeatureBoxHistory
SavingManual (click Save)Automatic (every request)
Response DataNot savedFull response stored
LimitUnlimited100 entries (FIFO)
PersistencePermanentAuto-deleted when limit reached
NamingCustomizableAuto-generated
OrganizationSort by name or dateSort by date or URL
PurposeRequest templates for reuseRequest/response audit trail