Postman Collection Generator

Postman Collection Generator: Real, Importable JSON

Hand-writing a Postman Collection JSON file means getting a specific nested schema exactly right — the info block, the item array, each request's method/url/header/body shape. This tool lets you fill out endpoints through a normal form and generates a Collection Format v2.1 file that imports directly into Postman, no manual JSON authoring required.

Formula

{ info: { name, schema }, item: [{ name, request: { method, header, url, body } }] }

Generated against Postman's official Collection Format v2.1.0 schema — the same format Postman itself exports.

Why the Schema URL Matters

The `info.schema` field tells Postman (and any other tool reading the file) exactly which version of the collection format to expect — pointing it at the official v2.1.0 schema URL is what makes the file recognized as a valid, importable collection rather than arbitrary JSON.

Headers and Variables

Headers are entered as simple `Key: value` lines and converted into Postman's `{ key, value, type }` header object format. Postman variable syntax (`{{token}}`, `{{baseUrl}}`) works anywhere in the URL, headers, or body — Postman resolves these against your active environment when requests run.

Practical Examples

Sharing a Set of API Endpoints

Documenting a small API for a teammate to test.

1.Add each endpoint with method, URL, headers, body
2.Copy the generated JSON
3.Import into Postman as a ready-to-use collection

What Gets Generated

Collection info block with schema reference
One request item per endpoint
Headers as Postman header objects
Raw JSON body (for non-GET methods)

Good Use Cases

Bootstrapping a Postman collection without manual JSON editing
Sharing a documented set of API calls with a team
Converting a list of endpoints from documentation into testable requests
Quickly scaffolding a collection to iterate on inside Postman

Frequently Asked Questions

Will this JSON actually import into Postman?

Yes — it's generated against the real Postman Collection Format v2.1.0 schema (info.schema points at the official schema URL), with the request method, URL, headers, and body structured exactly as Postman expects on import.

Can I use Postman variables like {{token}}?

Yes — double-curly-brace syntax in the URL, headers, or body is passed through as-is in the raw values, and Postman will resolve them against your environment when you run the imported requests.

Why is the body field hidden for GET requests?

GET requests conventionally don't carry a request body — the field is hidden to match that convention, though you can still switch the method to POST/PUT/PATCH/DELETE to add one.

How do I actually import this into Postman?

In Postman, choose Import → paste the raw JSON (or save it as a .json file and import the file) — it'll appear as a new collection with each endpoint as a separate saved request.

Is my data sent anywhere?

No, the collection JSON is built entirely in your browser.

Postman Collection Generator