Forum Discussion

chewbika's avatar
chewbika
Occasional Contributor
2 years ago
Solved

Mass import Postman collection/requests into Swagger Explore API/operation

I inherited an old code base that doesn't have any API documentations and I want to use Swagger Hub for it. We fortunately have a collection in Postman for most of the endpoints. I am following th...
postman
  • frankkilcommins's avatar
    frankkilcommins
    6 months ago

    We’ve released 0.8.0 of π—˜π˜…π—½π—Ήπ—Όπ—Ώπ—².𝗖𝗹𝗢 which now has support for nested Postman Collections as part of it’s import.


    Root level requests are now added to an Explore API folder with same name as Explore Space (e.g. Postman collection 'foo' with requests will create Explore Space 'foo' with API folder 'foo' which will contain the request connections).

    Nested folders within a collection, will have a name format of Parent - Child (e.g. foo/bar will create API folder called foo - bar, foo/bar/baz will create API folder called foo - bar - baz)

    Also, in case you missed it, we also support  an`πš’πš–πš™πš˜πš›πš-πš™πšŠπšŒπš-πšπš’πš•πšŽ` feature allowing you to explore the API calls representing consumer expectations within a Pact contract.

    Install via Nuget: https://www.nuget.org/packages/Explore.Cli
    Standalone binaries: https://github.com/SmartBear-DevRel/explore-cli/releases/tag/0.8.0