Postman Collection to cURL
Paste an exported Postman Collection and get a curl command for each request, with folders as comments, headers, bodies, query strings and common auth types included.
Use the tool
Why this tool exists
Postman collections are great while you are inside Postman, but a teammate in a terminal, a CI job or a bug report wants plain curl. Re-typing each request by hand loses headers and quoting details, and copying them one at a time through the app is slow.
This converter reads the collection JSON and walks through nested folders. It writes curl with the method, URL, headers, raw, URL-encoded, form-data and GraphQL bodies, and bearer, basic and API key auth. Collection variables such as {{host}} can be replaced with their values. Pre-request scripts, tests, environment-level variables and OAuth flows are not run, so check any request that depends on them.
How to use it
- Export your collection as JSON (v2.0 or v2.1) and paste it into the input.
- Choose whether to substitute collection variables and add request names as comments.
- Copy the curl commands into your terminal or script.
Frequently asked questions
Which auth types are converted?
Bearer tokens, basic auth and API keys in a header or the query string. Other types, such as OAuth 2 or AWS signatures, are not converted and need to be added by hand.
What about environment variables?
Only variables stored in the collection itself are substituted. Variables from a Postman environment file stay as {{name}} so that you can fill them in or export them into the shell.
Are scripts and tests included?
No. Pre-request and test scripts are ignored because curl has no equivalent. A request that sets a header in a script needs that header added manually.
Is my collection uploaded?
No. It is parsed in your browser. Even so, collections often contain tokens, so remove real secrets before sharing the output.