Postman Collection
Collection parsing · Request extraction
Postman
Ready
ABOUT
About Postman Collection
Import Postman Collection JSON and quickly browse request methods and URL structure within the collection.
Postman Collection is a key team API asset, but the JSON is large and deeply nested—hard to read raw. A structured summary gives you the full picture in minutes and saves time on docs and migration planning.
DEEP DIVE
Learn more about Postman Collection
Postman is one of the most popular API collaboration tools; exported Collection JSON can be consumed by many tools. JSONSort's Postman parser extracts request lists, HTTP methods, URLs, and header structure so you can browse quickly without opening each request in the Postman client.
Great for team API docs, Collection migration assessment, and intermediate steps when converting Postman exports to other formats (e.g. OpenAPI). Fully local parsing—environment variable names and URLs in the Collection never upload.
Collection v2.1 includes rich metadata: item, request, response, auth, and more. The parser focuses on core fields like request method and URL for API inventories; use the formatter for full raw JSON details.
FEATURES
Core capabilities
Collection parsing
Parse Postman Collection v2 JSON format.
Request list extraction
List Method, URL, and Name for every request.
Folder structure
Preserve folder hierarchy inside the Collection.
Body preview
Show a summary of each request's raw body.
Local parsing
Collections may contain internal URLs and token names—local is safer.
Formatted output
Results output as JSON for downstream processing.
Folder hierarchy
Preserve directory structure—output matches Postman's left-side tree.
Variable placeholders preserved
{{baseUrl}} and similar variables stay as-is, marking environment dependencies.
HOW TO USE
How to use
-
1
Paste Postman Collection JSON
-
2
View parsed request summary
-
3
Copy or continue editing
-
4
On failure, check the error, fix source syntax, and retry
-
5
Pretty-print with the formatter or export for downstream scripts
WORKFLOW
Typical workflow
End-to-end flow from import to export so teams use Postman Collection consistently.
Export Collection
Postman → Export → Collection v2.1 JSON.
Paste & parse
Import into JSONSort and view the structured request list.
Browse & filter
Use the formatted tree view to inspect individual request details.
Document
Copy summaries to Wiki or OpenAPI migration scripts.
USE CASES
Use cases
Backend developers
Review structure of team-shared Postman Collections.
Technical writing
Extract API lists from Collections to write interface docs.
QA engineers
Assess Collection coverage and list all endpoints.
Frontend developers
Understand backend API inventory and plan Mock endpoints.
Architect
Assess Collection size and duplicate endpoints to drive API governance.
New hire onboarding
Browse the team's full API set without opening each Postman tab.
TIPS
Tips
- Export Collection v2.1 JSON from Postman and paste into the input.
- After parsing, copy JSON results to the formatter tree view to browse hierarchy.
- {{variable}} in Collections stays as-is so you can spot environment dependencies.
- For large Collections, split by folder and export separately before parsing.
- Use the Query tool to analyze URL parameter structure for a single request.
- Before migrating to Insomnia/Bruno, use this tool to gauge Collection size.
- Export Collection v2.1—not v1 or curl format.
- Sensitive headers (Authorization) may still show key names in summaries—redact before sharing.
- Split huge Collections by folder on export for faster parsing.
- Pipe parse results to the SQL tool to generate endpoint inventory tables.
LOCAL VS ONLINE
Local vs online tools
JSONSort stays purely frontend—this comparison shows why local tools fit dev data better.
TROUBLESHOOTING
Common pitfalls & fixes
Issues you may hit in practice and how to handle them—save time on trial and error.
Parse failed
Tip:Confirm it's Collection JSON—not Environment or a single request.
Incomplete URL
Tip:Unresolved variables are normal—resolve manually with Environment.
Hierarchy too deep
Tip:Split the Collection by folder and parse each part.
Wrong format version
Tip:For v1 Collections, Convert to v2 in Postman before export.
FAQ
FAQ
Does it support Postman v1?
Mainly Collection v2 / v2.1. Convert v1 in Postman before export.
Are Environment variables parsed?
Currently parses the Collection itself. Use the JSON formatter for Environment JSON.
Can it convert to OpenAPI?
Outputs structured JSON summary today. OpenAPI conversion is a follow-up step you can handle separately.
Are Pre-request Scripts executed?
No. Static JSON parsing only—scripts are not run.
Are response examples extracted?
Focuses on request definitions; see response examples in the raw JSON.
Is data uploaded to a server?
No. All JSONSort tools run locally in your browser—your input is never sent to any backend.
Do I need to sign up or install anything?
No. Open the page and go—no account, no client download, PWA offline cache supported.
How large can files be?
Depends on browser memory; multi-MB data usually runs smoothly. Split very large files or use merge & clean first.