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.
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:
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.
Form-data fields, URL-encoded data, and binary file attachments are also not saved. Only text-based request bodies (JSON, XML, text, etc.) are preserved.
Auth Security
For security, auth secrets (tokens, passwords, client secrets) are not stored. Only the auth configuration structure is saved. You'll need to re-enter credentials after opening a saved request.
Saving a Request
There are two scenarios when saving to Box:
New Request (First Save)
- Configure your request (URL, method, headers, body, auth, etc.)
- Click the Save button in the request toolbar
- A new item appears in the Box section with an auto-generated name
- The tab is now "linked" to this Box item
Existing Request (Update)
- Open a saved request from Box
- Make your changes
- Click Save again
- The existing Box item is updated (no duplicate created)
Auto-Generated Names
When you save a tab without first giving it a custom name, Atrahasis uses the tab's current auto-generated name, which is simply the HTTP method followed by a space and the full URL exactly as you typed it. For example: GET https://api.example.com/users. The scheme (https://, http://, {{baseUrl}}) is preserved — it is not stripped down to host + path.
Accessing Box
Box lives in the left sidebar, but the sidebar uses an icon rail pattern: click the Box icon in the narrow icon rail on the far left to switch the active panel to Box. Only one sidebar section (Box, Projects, Flows, Mocks, Load Tests, History) is visible at a time, and switching is done exclusively from the icon rail. The panel title is a plain label — there is no collapse chevron, no count badge next to it, and the title itself is not clickable.
Atrahasis looks at the start of each Box item's name and, if it begins with an HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS) followed by a space, it pulls that prefix out and renders it as a dedicated method badge. The remainder of the name is shown next to the badge.
Items whose names do not start with an HTTP method — such as Authentication Test — render as plain text with no method badge. This detection is purely based on the name's prefix, not on whether the name was auto-generated or set by the user: a custom name like POST Create User (Admin) will still show a POST badge.
Sorting Options
Click the "Sorted:" button to toggle between sorting modes.
| Sort Mode | Description | Use Case |
|---|---|---|
| A-Z | Alphabetical by name (default) | Finding requests by name |
| Recent | Most recently modified first | Finding recently used requests |
Opening Saved Requests
Click any item in the Box section to open it.
Click the Item
Click any saved request in the Box list.
New Tab Opens
A new tab is created with all saved request data (URL, method, headers, body, auth, etc.).
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, Atrahasis 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").
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
Atrahasis 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
Use descriptive names like "Create User" or "Login with OAuth" instead of auto-generated names. It makes finding requests much easier.
Use Duplicate to create variations of the same request. For example: "Create User (Admin)" and "Create User (Guest)".
Store URLs with environment variables like {{baseUrl}}/users. This makes your saved requests work across different environments.
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:
| Feature | Box | History |
|---|---|---|
| Saving | Manual (click Save) | Automatic (every request) |
| Response Data | Not saved | Full response stored |
| Limit | Unlimited | 100 entries / 100MB total (FIFO) |
| Persistence | Permanent | Auto-deleted when limit reached |
| Naming | Customizable | Auto-generated |
| Organization | Sort by name or date | Sort by date or URL |
| Purpose | Request templates for reuse | Request/response audit trail |