What is Postman Collection v2.1?

It is the current JSON format Postman uses to store a group of saved requests. The schema lives at the v2.1 URL and is recognized by the Import dialog in any modern Postman version.

How do I import the output?

Copy the JSON, save it to a file ending in .json, then open Postman and choose Import, File, and select it. Every endpoint you listed appears as a request inside the collection.

How does the Bearer auth work?

Choosing Bearer adds a collection-level auth block holding a token variable. Each request inherits it, so Postman sends an Authorization header with your token without per-request setup.

Can I include a request body?

Yes. Put a JSON object on the line right after a POST, PUT, or PATCH endpoint and it is attached as a raw JSON body with the matching Content-Type header.

Are variables supported?

The base URL is stored as a baseUrl collection variable and every request URL uses the double-brace baseUrl reference, so you can repoint the whole collection by editing one value.

Postman Collection Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Build a Postman collection in seconds

A Postman collection is just a JSON document describing a set of saved HTTP requests. Writing one by hand is error-prone because the v2.1 schema nests request, url, header, and body objects in a specific shape. This builder takes a base URL, an auth choice, and a plain list of endpoints, and emits a clean, importable collection.

How it works

The output follows the Postman Collection v2.1 schema. The collection has an info block with a generated UUID and the schema URL, a variable array holding your baseUrl, and an item array with one entry per endpoint. Each line you enter is parsed as METHOD path; the path is appended to the {{baseUrl}} variable and split into host and path segments as the schema requires. When the next line is a JSON object, it is attached as a raw body with a application/json Content-Type header. Selecting Bearer or Basic adds a collection-level auth block so every request inherits credentials.

Tips and example

List endpoints one per line, for example GET /users then POST /users followed by {"name":"Ada"} on its own line. Methods are case-insensitive. Use a {{baseUrl}} style placeholder mentally — you only type the path, the builder prefixes the variable. After importing, set the token variable in the collection to authenticate live calls.