About Swagger to Collection JSON

Convert an OpenAPI / Swagger spec into a Collection JSON v2.1 payload. Part of the DevTools Surf developer suite. Browse more tools in the API / Config collection.

Use Cases

• Import API specs into Postman for interactive testing
• Generate API test collections from Swagger documentation
• Share runnable API collections with QA teams
• Convert OpenAPI specs for use in automated API testing pipelines

Tips

• Upload a Swagger/OpenAPI spec to get Collection JSON output
• Use the collection to import endpoints into API testing tools
• Verify all endpoints are included after conversion

Fun Facts

• Collection JSON v2.1, used by Postman, can represent complex request chains including pre-request scripts and test assertions.
• Postman was created by Abhinav Asthana in 2012 as a Chrome extension and grew to over 30 million users by 2023.
• The OpenAPI-to-Postman converter must handle parameter serialization styles (matrix, label, form) that differ between the two formats.

FAQ

Which Swagger versions?

OpenAPI 2 (formerly Swagger 2.0) and OpenAPI 3.x. The tool auto-detects and converts appropriately.

What's in the generated Collection?

One request per endpoint, with method, URL, headers, and example body from the spec. Variables for the base URL and auth.

Does it preserve examples?

Yes — if the OpenAPI has `examples` sections, they become the default request body. Multiple examples become multiple requests in the collection.

Can I edit after conversion?

Yes — the output is plain JSON you can import into REST Handler, Postman, Insomnia, or Bruno. Edit before or after import.