Skip to converter

Postman v2.1 API collection (restricted) to JSON Converter.

Postman v2.1 API collection (restricted) to JSON for small API request collections. Convert compatible Postman, Insomnia and spreadsheet inventories privately in your browser.

Convert your file

INPUTPostman v2.1 API collection (restricted)
OUTPUTJSON
Files stay on your device

Up to 2 MiB · 1–500 simple HTTP requests · Local conversion

Choose a compatible source file to begin.
Private processingYour source file stays in your browser
Original stays intactDownload a new output file
Real formatsUnsupported conversions show an error

STEP BY STEP

How to convert Postman v2.1 API collection (restricted) to JSON

  1. Choose a source file. Select a real Postman v2.1 API collection (restricted) file from your device.
  2. Run the local converter. The converter checks the input and processes it locally using the appropriate browser engine.
  3. Download the result. Save the generated JSON file. Your original file is unchanged.

FORMAT GUIDE

Why convert Postman v2.1 API collection (restricted) to JSON?

Inventory simple API endpoints in CSV or Excel and exchange basic request lists between compatible Postman and Insomnia versions.

  • Documenting a simple API endpoint inventory in a spreadsheet.
  • Moving basic HTTP request definitions between Postman v2.1 and Insomnia v4.
  • Reviewing endpoint names, HTTP methods and URLs without running requests.

UNDERSTAND YOUR FILES

Postman v2.1 API collection (restricted) vs. JSON: what changes?

Input · Postman v2.1 API collection (restricted)

Output · JSON

Structured text for arrays and objects. This hub handles flat table-shaped collections rather than arbitrary nested schemas.

Inventory simple API endpoints in CSV or Excel and exchange basic request lists between compatible Postman and Insomnia versions. Choosing an output format changes how another app reads the file; it does not restore detail missing from your source.

Check the formatting

Basic paragraphs, text, and common markup can be converted, but complex layouts, scripts, custom Markdown extensions and styling may not round-trip.

Your files and privacy

Your selected file is converted on your device. You can download the new file while keeping the original unchanged.

Some formats work differently across browsers and devices. Check the converted result before using it for important work. Advertising and other optional website services may have separate privacy practices.

Format compatibility and limitations

Supports flat Postman Collection v2.1 and legacy Insomnia v4 JSON exports, not full API clients. Required spreadsheet columns in order: collection_name, request_name, method, url, description. One collection and 1–500 requests; JSON inputs and outputs up to 2 MiB. Only literal absolute HTTP(S) URLs and methods GET, HEAD, OPTIONS, POST, PUT, PATCH and DELETE. Credentials, headers, query parameter objects, bodies, authentication, environment variables, nested folders, cookies, tests, scripts, responses, GraphQL and gRPC are rejected rather than dropped. Plain URL query strings are preserved. No HTTP requests are issued. Keep your original file and review the result before importing into API tools.

Actual output behavior depends on the input file, your browser, device resources and the converter engine. Check important files before sharing or replacing them.

HELP & ANSWERS

Postman v2.1 API collection (restricted) to JSON questions

Does this send API requests or upload files?

No. File parsing and export happen on your device; requests are never executed.

Does it copy passwords or authentication?

No. Files containing credentials, authorization headers or other unsupported request metadata are rejected.

Can I import any Postman or Insomnia export?

No. This is a restricted, flat, no-authentication, no-body request subset. Supports flat Postman Collection v2.1 and legacy Insomnia v4 JSON exports, not full API clients. Required spreadsheet columns in order: collection_name, request_name, method, url, description. One collection and 1–500 requests; JSON inputs and outputs up to 2 MiB. Only literal absolute HTTP(S) URLs and methods GET, HEAD, OPTIONS, POST, PUT, PATCH and DELETE. Credentials, headers, query parameter objects, bodies, authentication, environment variables, nested folders, cookies, tests, scripts, responses, GraphQL and gRPC are rejected rather than dropped. Plain URL query strings are preserved. No HTTP requests are issued. Keep your original file and review the result before importing into API tools.