Collections

Collections let you organize and save your API requests into a structured hierarchy of folders and sub-requests — making it easy to manage complex APIs.

Structure

Workspace
└── Collection: "User Service API"
    ├── Folder: "Authentication"
    │   ├── POST /auth/login
    │   └── POST /auth/refresh
    ├── Folder: "Users"
    │   ├── GET  /users
    │   ├── POST /users
    │   └── Folder: "Admin"
    │       └── DELETE /users/:id
    └── GET /health

Creating a Collection

  1. In the sidebar, click the + icon next to “Collections”
  2. Enter a name (e.g., User Service API)
  3. Press Enter or click Create

Adding Folders

Inside a collection:

  1. Right-click the collection → New Folder
  2. Enter a folder name
  3. Folders can be nested inside other folders

Adding Requests

  1. Right-click a collection or folder → New Request (or New WebSocket)
  2. A new tab opens with an untitled request
  3. Configure the request and it’s automatically associated with the collection

Saving Requests

When you modify a request that belongs to a collection, a dirty indicator (•) appears on the tab. Press Cmd+S / Ctrl+S to save.

Renaming

Right-click any collection, folder, or request → Rename. Or double-click the name in the sidebar.

Cloning a Collection

Right-click a collection → Clone. Enter a new name and a full copy is created, including all folders and requests.

Deleting

Right-click → Delete. Deleting a folder removes all requests inside it. Deleting a collection removes all its contents. This action cannot be undone.

Multi-tab Workflow

Each request opens in its own tab. You can have multiple requests from different collections open simultaneously and switch between them freely. Unsaved changes are tracked per tab.

Tips

  • Organize by service at the collection level, and by resource at the folder level.
  • Clone a collection before experimenting with breaking changes.
  • Use descriptive request names like GET All Users rather than just Get Users.