Collections & Folders

A Collection is a named group of saved requests. Collections are how you keep your work organized in HTTPBot — group the endpoints for one API, one project, or one feature together so they're easy to find and re-run.

Within a Collection you can nest folders to add more structure and attach shared settings like Collection-level variables and authentication. Collections and their requests can also carry descriptions — typically brought in from an imported spec — that travel with the requests.

What a Collection can hold

Requests — the saved HTTP (and WebSocket) requests that make up your API workspace.
Folders — optional sub-groups for organizing requests inside a Collection. Folders can be nested.
Collection variables — key/value pairs scoped to the requests in this Collection. They're resolved as {{variables}} and sit between Global Variables and the active Environment in precedence. See Environments & Variables.
Collection-level authentication — a default auth configuration for the whole Collection. Individual requests can set their auth type to Inherit to use it, so you configure credentials once and every request in the Collection picks them up. See Authentication.
A description / documentation — descriptive notes shown for the Collection and its requests. These are read-only in HTTPBot and usually come from an imported spec (such as an OpenAPI or Postman collection).

The Collections list showing several collections.

Creating a Collection

Open the Collections tab.
Tap the + floating action button in the bottom corner.
Choose New Collection.
Give it a name and save.

The same + menu is also where you import existing API definitions — Postman collections, OpenAPI/Swagger specs, and HAR files. See Importing for those formats.

The collection editor is also where you attach a Collection's shared settings — its name, Collection variables, and Collection-level authentication.

The collection editor showing the name, Collection variables, and auth.

Adding requests and folders

Add a request to a Collection by saving a request into it.
Add a folder to group related requests within the Collection. Folders can contain both requests and other folders.

A Collection opened to show its folders and the requests inside them

Renaming, organizing, and deleting

Rename a Collection or folder to keep your structure tidy as a project grows.
Organize by creating folders to break up a large flat list, then saving new requests directly into the folder where you want them.
Delete a Collection, folder, or request when you no longer need it. Deleting a Collection removes the requests and folders it contains.

Searching

Use the search field at the top of the Collections list to search across your Collections. This is the quickest way to jump to a specific endpoint when you have many Collections.

Collection-level authentication & Inherit

Set authentication once on the Collection, then leave each request's auth type as Inherit. At send time, an inheriting request uses the Collection's auth configuration — so rotating a token or changing the auth type in one place updates every request that inherits it. You can still override auth on any individual request when an endpoint needs something different. Full details are in Authentication.

Request Documentation

Every request can show its own documentation: the URL, description, and a summary of its headers, parameters, and body. Open it from the request's … menu → View Documentation. This is a convenient, read-only view to remind yourself how an endpoint is configured. Any description text shown here typically comes from an imported spec.

Collections themselves can also carry a description, so when one is present the Collection and its requests together form lightweight reference docs.

A request's View Documentation screen.

Two Collection areas: yours and Postman

HTTPBot keeps two separate areas for Collections:

Collections — your own Collections, created in HTTPBot or imported from a file. You have full control to edit, organize, and run them.
Postman — Collections synced live from a connected Postman account, organized by workspace. These mirror what's in your Postman cloud account.

Browsing and importing Postman (and other) collections is free. Sending a request that lives in an imported or synced Collection requires HTTPBot Pro. PRO

Requires HTTPBot Pro. Browsing imported/synced Collections is free; firing a request from one is a Pro feature.

See Importing to import files, or Postman Sync to connect a Postman account.

Building a Request — creating and editing the requests inside a Collection
Authentication — Collection-level auth and Inherit
Environments & Variables — Collection variables and precedence
Importing — bringing in external Collections from files
Postman Sync — connecting a live Postman account
Request Settings — request settings and cookies