Design & Build
Native Git
One repository for your code, collections, specs and tests. Local by default. Ship them the way you ship code.
Trusted by teams at
Your API work, as files in your repo
Collections and specs live with your code
One YAML file per request, per spec, per environment, under /postman in your repo. They diff line by line, like everything else you review.
Keep the Git workflow you have
They are plain files, so you branch, diff, and review them with the Git tooling you already use. Postman doesn't replace it.
Test in CI, publish on merge
Run your collections in the pipeline with the Postman CLI, then publish to Cloud View when the branch merges.
Postman AI reads your code, not just your collection
Your collection is a file in the same repo as your service, so Postman AI can read both. Ask it what your tests miss and the answer comes from the route handlers, not from a spec.
RESOURCES
Go deeper on Native Git
See Native Git on your own repository
Chat with a Postman expert about connecting your repository, keeping collections and specs versioned with the code they cover, and running them in the pipeline you already have.
