Skip to content

Collections

Thiago Miranda edited this page Jun 15, 2026 · 3 revisions

Collections

Collections are your saved requests, organized in a tree of folders and requests. They live in the COLLECTIONS tab of the side menu.

Saving a request

Edit a request, then press Cmd/Ctrl + S (or the save action):

  • If the tab is linked to a saved request, it updates that request ("REQUEST UPDATED!").
  • If it's unlinked, a SAVE TO COLLECTION prompt appears (default name NEW REQUEST). Name it and confirm — it's saved as a new request and the tab becomes linked to it.

The tree

  • Folders show a folder icon (a ★ if favorited) and a chevron to expand/collapse.
  • Requests show a colour-coded method badge and the name; a chevron appears if the request has saved #Saved examples; an example count badge shows on the right.
  • Tap a request to open it in a tab. Tap a folder to expand/collapse.
  • Expansion state is remembered across edits (it's keyed by node identity, so renaming a sibling won't collapse your tree).

Sort order

Within each level: favorites first, then folders, then requests, each group alphabetical (case-insensitive).

Node actions

Open a node's menu — right-click / three-dot menu on desktop, long-press on phone (a bottom sheet):

Action Applies to What it does
FAVORITE / UNFAVORITE folders Pin to the top of its group
RENAME all Rename (prompt, "SAVE")
EDIT DESCRIPTION all Free-text notes; multi-line; empty clears it
ADD SUBFOLDER folders Create a child folder ("ADD")
MOVE TO… all (phone) Pick a destination folder or ROOT (TOP LEVEL)
EXPORT TO POSTMAN all Save as a Postman v2.1 .json (see Import Export and Git Workspace)
DELETE all Confirmed delete ("Delete folder?" / "Delete request?")

Folders

Create a top-level folder with the NEW FOLDER button in the side-menu header, or ADD SUBFOLDER from a folder's menu. Deleting a folder deletes everything inside it (after a confirm).

Descriptions

Both folders and requests can carry free-text notes via EDIT DESCRIPTION (multi-line; saving an empty value clears it). Handy for documenting what a request does or noting required variables.

Drag-and-drop (desktop)

  • Drag a request or folder onto a folder to move it inside.
  • Drag onto empty space / the list background to move it to the root.
  • You can't drop a folder into its own descendant. After a move, the level re-sorts.
  • On phone, use MOVE TO… instead.

Saved examples

A saved example is a frozen request + its response, attached to a request node — great for documenting "here's what a 200 looks like" or keeping a known-good payload.

  • Capture: send a request that's linked to a collection node, then click Save as example (bookmark icon) in the Responses BODY actions. Name it (default like 200 · 14:32).
  • View: examples appear as indented rows under their request (expand via the request's chevron). The request shows an example-count badge.
  • Open: tap an example to open it in a new unlinked tab with its saved response already shown — so editing or re-sending never overwrites the original request.
  • Manage: each example's menu has RENAME EXAMPLE and DELETE ("Delete example?").

Examples are local-only: they're excluded from Postman export and from the git workspace mirror (they carry captured response data). See Import Export and Git Workspace.

Sharing collections

  • Postman: export/import via Postman v2.1 JSON.
  • Git: mirror a collection to a folder of readable JSON files you can commit.

Both are covered in Import Export and Git Workspace.

Clone this wiki locally