HTTP collections
Folders of saved requests with nested folders, soft-delete + 30-day undo on Pro+, cross-Space sharing, folder-level auth inheritance with override hint.
Collections are folders of saved requests with nested-folder support.
Tier behavior
- Free — capped at 1 collection / 25 requests, no nested folders.
- Pro and above — unlimited collections, soft-delete + 30-day undo, drag-reorder, bulk export, cross-Space sharing.
Hierarchy
Collection → Folder → Folder → … → Request. Folders can nest arbitrarily deep. Drag-reorder works between siblings; drag-into-folder works to re-parent.
Auth inheritance
Auth set on a collection cascades to every folder and request beneath. Folders can override; requests can override both. The request row shows an inherits from
Right-click any folder for Edit inherited auth — opens an AuthEditor bound to the folder so a single OAuth config can cover every request beneath it. See Auth presets for the full preset list.
Soft-delete + undo
Delete a request, folder, or collection on Pro+ and it disappears from the UI but lives in a deleted_at column for 30 days. Recover via Trash → Restore within the window. After 30 days the row is hard-deleted on the next reconcile.
Cross-Space sharing
A member of one Space can grant another Space read-only access to a collection (http_collection_shares table). The receiving Space sees the collection in a separate “Shared with this Space” group; mutations are blocked.
Operations
Right-click a collection or folder for rename / duplicate / delete (soft) / bulk-export / share. Bulk-export writes a Postman v2.1 file.