Exporting a Collection
Exporting a collection saves it as a Collection v2.1 JSON file — a plain text schema describing every folder, request, script, and variable — which you can share via email, commit to a Git repo, or attach to documentation. Because the export is just JSON, it's diffable in version control, letting a team review changes to API requests the same way they review code changes.
Cricket analogy: Exporting a collection to JSON is like a scorer converting a match's ball-by-ball record into a standard scorecard format that any other board can read, file, and compare against a previous match without needing to watch the game itself.
Importing from Files, URLs, and Other Tools
Postman's Import button accepts a raw collection JSON file, a public URL pointing to one, or specs from other formats entirely — an OpenAPI/Swagger YAML file, a cURL command pasted directly, or an Insomnia export — auto-converting each into native Postman requests. This makes Postman a practical landing spot for API definitions that originated in a completely different tool or that a backend team maintains as an OpenAPI spec alongside their code.
Cricket analogy: Importing from an OpenAPI spec is like a franchise auto-converting a rival board's raw statistics feed into their own analytics dashboard's format, so scouting data from an entirely different board's system becomes usable without manual re-entry.
# Pasting this into Postman's Import dialog auto-converts it to a request
curl -X POST https://api.example.com/v1/users \
-H "Content-Type: application/json" \
-H "Authorization: Bearer {{auth_token}}" \
-d '{"name": "Ada Lovelace", "email": "ada@example.com"}'Postman's 'Fork' feature creates a linked copy of a collection inside a team workspace that can later be merged back via pull request, which is a better fit for ongoing team collaboration than repeatedly exporting and re-importing static files.
Keeping Imports and Exports in Sync
A raw file export is a point-in-time snapshot, so if you import a collection and later the source is updated, you won't see those changes unless someone re-exports and you re-import; teams that need continuous sync instead use shared team workspaces or Postman's Git-based collection sync so everyone works off the same live source instead of drifting file copies.
Cricket analogy: A raw file export is like a printed scorecard handed out at the ground — accurate for that moment, but it won't update itself if a wicket falls after you've walked away, unlike a live scoreboard feed that a whole stadium watches in sync.
Re-importing a collection JSON file that shares the same underlying collection ID as one already in your workspace will overwrite it, including any local requests, scripts, or variable edits you made since the last import — export your local version first if you need to preserve those changes.
- Exporting a collection produces a Collection v2.1 JSON file describing every folder, request, script, and variable.
- Exported JSON is diffable, so teams can review API request changes in Git the same way they review code.
- Postman's Import accepts raw JSON files, public URLs, OpenAPI/Swagger specs, cURL commands, and exports from other tools.
- A raw file export is a point-in-time snapshot that won't reflect later changes to the source.
- Team workspaces and Git-based collection sync keep everyone on a live shared source instead of drifting file copies.
- Re-importing a file with the same collection ID can silently overwrite local changes.
- Postman's Fork feature creates a linked, mergeable copy better suited to ongoing collaboration than repeated file exports.
Practice what you learned
1. What format does Postman use when you export a collection?
2. Besides a raw JSON file, what else can Postman's Import accept?
3. What is a key limitation of a raw file export/import for keeping teams in sync?
4. What risk should you be aware of before re-importing a collection JSON file?
5. What is Postman's Fork feature best suited for?
Was this page helpful?
You May Also Like
Collections Basics
Learn how Postman Collections group related API requests into a single organized, shareable, and runnable unit.
Organizing Requests with Folders
Learn how to use folders inside a Postman Collection to group related requests, apply shared settings, and control execution order at scale.
Environments and Variables
Understand how Postman Environments let you swap base URLs, tokens, and config values between dev, staging, and production without editing every request.