Navigating Postman's Native Git and API Specs

Hi, first time here! This forum is almost as difficult to use as Postman… :wink:

I came here, because the link to “Explore the new Postman” fails to give hands-on explanations about where the new stuff is and how it works.

In particular I am wondering this:
How do I connect my Postman Team workspace to a GIT repository on GitLab? I do not mind manually creating the repository first.

Hey @altimetry-geoscien13 :waving_hand:

Welcome to the Postman Community! :postman:

This is a hosted community using the Discourse platform, we only have a certain level of control and configurability over this site :sweat_smile:


If you already have that repo cloned into your local file system, you should just be able to Create a New Workspace using the repo option.

From an existing Team Workspace you can also go to the Files options and open the folder from there.

Also more information can be found here:

Thanks for replying.

Unfortunately my Postman does not look like that, with a Files icon, probably because we are not on a Paid plan yet.

I went down the rabbit hole of trying to get AI-answers, and the conclusions are

  • This is for “API objects” (not Collections) that are not explained anywhere what it is for.
  • “API objects” are for API design, with a (for us) strange implied workflow of designing the API using rather poor tools, dicsonnected from the source code. Our API specifications are generated from the source code rather than the other way around, and GitLab already does a pretty good job of visualizing them.
  • Importing the swagger.yaml file from our codebase into Postman was possible, but failed to put the “API objects” in a place where it could be found. Had to enable “APIs” in the left sidebar first (not explained), or manually re-import from the APIs page later on (did it). The generated Collection from the imported file looks great though - a complete structured set of Collections and Requests.
  • I am pissed by the recent move to not allowing even 2-person Teams on the Free plan (not enforced yet), after forcing “cloud collaboration” down our throats earlier. Will seek a simpler and more scalable alternative like Bruno.

The native git feature is available to all plans.

Are you using the web or Desktop app? You would only be able to use the Desktop app to connect to a git repo. Are you using version v12?

If you’re importing a API into Postman, it would become a Spec and be under the Specs section in the right sidebar.

You can store Specs, Collections, Environments, Local Mocks, Globals, etc. in your project and access those in your Postman instance.

I’m happy to explain more if you have questions around certain flows are where things live in the platform. :folded_hands:

Thanks for patiently replying. :slight_smile:

I am using a Windows program - I do not know what version it might be, have trouble figuring out where to check it. There was an update, but I think I prefer not changing anything now (too many undesired changes already). Bummer, I think I cannot stop it now that the update has been downloaded. Hope nothing breaks.

In the Postman version that I use, API specifications appear under “APIs” in the left side menu (after finding the cryptic icon to add “APIs” there). I never figured that I should look in Specs (it was there) - the AI suggestion was that I should see “APIs” somewhere - a frustrating exercise looking in vain for where that import ended up.

I do not know what “Project” might be in Postman, and don’t think I have a need for it. I have Collections/Folders and Requests (and APIs, now that I figured out how to enable it in the UI).

Just to try and work through the questions:

To find the version, you can use the About section in the App Settings.

Settings > App Settings > About

This is for my Mac by you will have the OS version for you.


The APIs feature is being deprecated and all Specification with be access via the SpecHub feature in the platform.

Postman API Builder

The Postman API Builder is no longer supported. API specification management moves to Spec Hub.

Learn how to migrate your API specifications from the API Builder to Spec Hub.

For all elements within a Workspace, they can be found in the right sidebar. If a feature is not present, you can use the Customize sidebar option to add those into the Workspace.


I’m a little unclear about what you mean by Projects is that something in GitLab?

You can store your Collections, Requests and Specs inside a Postman Workspace, either in the Cloud Mode or in Local Mode which would be a local folder connected to your git repo.