← Back to Overview

COLLECTIONS

Folders & Organization

Organize requests into nested folder trees with drag-and-drop reordering, deep search, and inheritance of auth, scripts, and certificates.

Nested folders with child and grandchild structure

Creating Folders

Folders group related requests within a collection. Create them from the sidebar context menu.

Right-click a collection or folder → select 'New Folder'
Name the folder and press Enter
Folders can contain both requests and sub-folders
Each folder gets a unique UUID v4 identifier
Folders support auth, scripts, and certificate inheritance
Tip: Click a folder name in the sidebar to open its editor tab where you can configure auth and scripts that child requests inherit.

Unlimited Nesting

Folders can be nested to any depth using a recursive CollectionFolder structure. There is no artificial limit on nesting levels.

Array index = display order (no explicit rank field needed)
Each folder has requests[] and folders[] arrays

Common organization patterns:

By Resource

/users, /posts, /auth

By Flow

auth → create → verify

By Environment

dev, staging, production

Drag & Drop

Move requests and folders between parents with drag-and-drop. Works in both the webview sidebar and the VS Code native tree view.

Reparent requests — drag a request from one folder to another
Reparent folders — drag a folder under a different parent folder
Reorder — drag to reorder within the same parent
Visual drop indicator shows the insertion point
Scope restriction: Cross-scope drops are not allowed — you cannot drag a Local item into a Global collection or vice versa.

Reordering

Item display order is determined by array position in the collection JSON — no manual rank numbers to manage.

Drag items up or down to reorder within their parent
Supported in both the webview sidebar and VS Code native tree view
The reorderCollectionItem message handles all move operations internally
How it works: When you drop an item, the extension splices it from its source array and inserts it at the target index. The updated collection is saved to disk immediately.

Best Practices

Recommended approaches for keeping your collections organized and maintainable.

Group by resource

Create folders per resource: /users, /posts, /auth

Group by workflow

Order requests by flow: Login → Get Token → Access Resource

Use collection variables

Set shared base URLs as collection variables so all requests use {{base_url}}

Set auth at collection level

Configure auth once at the collection or folder level and let all child requests inherit it

One collection per API

Keep one collection per API or microservice for clear boundaries and easy sharing

Next

Ko-fi