Postman to cURL

Runs in your browser; nothing is uploaded

Convert between OpenAPI 3, Swagger 2.0, Postman collections, cURL commands, HAR recordings and .http files. Anything the target format can't hold is listed, never dropped silently. Nothing is uploaded.

Source

Result

Nothing yet

Paste an API description on the left, or pick an example, then choose what to convert it to.
Ready
Ln 1, Col 1

Moving an API description between formats

The same API is often described in several places: an OpenAPI or Swagger spec for documentation and code generation, a Postman collection for manual testing, cURL commands in a README, a HAR recording from the browser. This converter reads any of them and writes any other, so you don't keep them in step by hand.

Swagger 2.0 to OpenAPI 3.1 is the most common upgrade. Body and form parameters become a request body, host, basePath and schemes become servers, definitions move to components/schemas and every $ref is rewritten to match. Going the other way, from Postman or cURL to OpenAPI, folders become tags, URLs are split into a server and paths, and JSON bodies are turned into schemas.

Formats don't all hold the same things. A Postman collection has no response schemas; Swagger 2.0 has no oneOf; a cURL command has no description. Whenever something can't be carried across, the converter lists it above the result instead of dropping it silently, so you know what to check.

How to use this tool

  1. 1Paste the source: an OpenAPI or Swagger spec (JSON or YAML), a Postman collection, one or more cURL commands, or a HAR file. The format is detected.
  2. 2Choose what to convert it to in the result pane.
  3. 3Read the notes above the result, if there are any: they say what the target format couldn't hold.
  4. 4Copy the result or download it as a file.

Troubleshooting

This isn't an API description this tool reads
Check that it's complete JSON or YAML. A Postman export must be the collection, not an environment or a data file.
A WSDL or other XML
Open it in the API Map, which turns SOAP services described by a WSDL into OpenAPI.
Paths still contain {id}
That's the path parameter as the spec declares it; fill in a real value before sending a cURL command.

Frequently asked questions

Is my spec uploaded?

No. Everything is converted in your browser, so private and internal APIs are safe to paste.

Does it keep my schemas and examples?

Yes, when the target format can hold them. When it can't, the note says what was left out.

Can I see the API as a diagram or test it?

Yes: the API Map draws any of these formats as an interactive map, and API tests generates and runs tests from a spec.