What a collection holds#

A collection is a saved tree of API work that stays on your device between sessions. It holds requests, folders, and flows, arranged however suits the API you are testing. Collections live in the left sidebar, under the Collections tab, so you can reopen anything you save with one click.

The four kinds of node#

The tree is built from four kinds of node. A collection sits at the top, and everything else lives inside it.

• Collection. A named, top-level container. It is the thing you save into.
• Folder. A group inside a collection or another folder. Folders nest, so you can shape the tree around the API. See Folders.
• Request. A saved request, with its method, URL, parameters, headers, body, and auth. See Saving a request.
• Flow. A saved automation flow. See Flows overview.

Controls above the tree#

Three controls sit above the tree:

• Search box: filters the tree as you type.
• "+" button: starts a new collection.
• Import button: brings in a collection from a file.

Each collection is a section you can expand or collapse. When you have none, the tree shows the message No Collections.

Open, change, and filter rows#

Click a saved request or flow to load it into a tab. See Opening a saved request. Hover over any row to reveal a three-dot menu with rename, add, and delete actions. See Managing items. Type in the search box to filter the tree by name, path, or method. See Searching.

Where collections are stored#

API Client saves collections on your device, and they survive restarts. There is no cloud sync. To keep your requests in version control alongside your code, link a collection to a folder on disk. See Linking to a folder.