Quick story on why I wrote this.
I got assigned to a handover project with a lot of API work. No API docs, no Postman collections, nothing. Just the project files.
So, I built my own Postman collection from scratch. Then a second dev joined the project and did the same thing. Then a third.
Everyone had their own copy. Nobody was in sync. Requests were slightly different across the team.
If your team stores collections in Azure DevOps or GitHub, there's a simple way to share them through Postman and keep everyone on the same page.
What the guide covers
- How to export a Postman collection properly. Only properly exported JSON files can be reliably imported using Raw URLs.
- How to structure your repo. Keep a
/postman folder with your exported collection files so imports are easy.
- Import using Raw URLs from GitHub. Open your JSON file on GitHub, click Raw, copy the URL, and paste it into Postman's import dialog. This is the fastest method.
- Import by downloading the file. If raw URLs are restricted or you prefer working offline, download the JSON file and drag it into Postman.
Part 1 of 3
This is the first post in a 3-part series:
- Part 1 (this one): Import using Raw URLs
- Part 2: Connecting GitHub directly to Postman
- Part 3: Full CI/CD automation with the Postman API
Links
How does your team share API collections? Would love to hear what works for you.