Folder Structure Based Off of Tags When Importing an openapi.json Spec File

I was originally going to post this in Help Hub, but I figured it out as I was writing up my question. So here is a guide for those who are wanting to do something similar when importing their openapi.json file.

We have an automatically generated openapi.json file that I would like to import into a public collection, but when I import it, the folder structure doesn’t match our api docs website:

But in postman it looks like this:

Notice the folder structure doesn’t match. For example there is note “Invites” directory showing in Postman.

To fix this when importing your openapi.json spec file click on the “View Import Settings” button before starting the import.

In the settings dialog there is section aptly named “Folder organization”. If you change it from the default to “Tags” it will create the folders like I’m expecting on import.

And this is how it now looks in Postman with the correct folders based off of the tags:

1 Like