TOML stores structured settings and values. These tools support simple repeated record tables with text values, not arbitrary configuration documents.
TOML records to Postman v2.1 API collection (restricted) Converter.
TOML records to Postman v2.1 API collection (restricted) for small API request collections. Convert compatible Postman, Insomnia and spreadsheet inventories privately in your browser.
Convert your file
Up to 2 MiB · 1–500 simple HTTP requests · Local conversion
Preview text output
STEP BY STEP
How to convert TOML records to Postman v2.1 API collection (restricted)
- Choose a source file. Select a real TOML records file from your device.
- Run the local converter. The converter checks the input and processes it locally using the appropriate browser engine.
- Download the result. Save the generated Postman v2.1 API collection (restricted) file. Your original file is unchanged.
FORMAT GUIDE
Why convert TOML records to Postman v2.1 API collection (restricted)?
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
TOML records vs. Postman v2.1 API collection (restricted): what changes?
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
TOML records to Postman v2.1 API collection (restricted) 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.
