Import and convert Postman collection JSON to various formats (cURL, REST, YAML). Part of the DevTools Surf developer suite. Browse more tools in the API / Config collection.
Use Cases
Convert a Postman collection to cURL commands for use in shell scripts or CI pipelines.
Extract all endpoints from a shared Postman collection to seed API documentation.
Convert collection requests to YAML for import into Insomnia or Bruno.
Generate a request inventory from a legacy collection before migrating to a new API client.
Tips
Import the Postman v2.1 collection format — it contains more metadata than v2.0 and converts more faithfully to other formats.
After converting to cURL, verify that Authorization headers are preserved, especially for OAuth2 flows that Postman stores as pre-request scripts.
Use the YAML output to seed an OpenAPI spec — it captures endpoints and request bodies that you can augment with response schemas.
Fun Facts
Postman was founded in 2014 by Abhinav Asthana as a Chrome extension. By 2022 it had over 20 million registered users, making it one of the most widely adopted developer tools in history.
The Postman Collection format (JSON) has gone through three major versions: v1 (2012), v2.0 (2016), and v2.1 (2017). The v1 format is now deprecated.
Postman processes over 1.13 billion API requests per month through its testing platform as of 2023.
FAQ
Which Postman collection versions are supported?
v2.0 and v2.1 JSON formats. The older v1 format has a different schema and may require manual cleanup before import.
Are pre-request scripts and tests preserved?
Conversion targets request structure (URL, method, headers, body). JavaScript pre-request scripts and test assertions are not portable to non-Postman formats.
Can I convert to OpenAPI from a Postman collection?
The converter produces YAML with endpoint structure. It does not infer response schemas automatically — you will need to add those manually for a complete OpenAPI spec.
