As Postman usage grows across a team, collections can become large and difficult to navigate. Without intentional structure and collaboration practices, people may duplicate work, create conflicting versions, or struggle to find the right requests. Optimising large collections keeps them useful and maintainable.
Refactoring Large Collections
Refactoring involves splitting monolithic collections into smaller, logically focused ones, and organising requests into clear folder hierarchies. You might separate public APIs from internal ones, or group requests by resource type and test purpose. Consistent naming conventions for requests and folders also improve discoverability.
# Example refactor
Before:
- One collection with 200+ mixed requests
After:
- Auth API collection
- Customer API collection
- Order API collection
Each with folders for smoke, regression, and error tests.Collaboration at scale also benefits from role clarity. Decide who owns which collections, how new requests are added, and how deprecated ones are removed. This reduces accidental divergence and duplicate efforts.
Managing Shared Assets
Shared environments, common script snippets, and base collections should be treated as shared assets with clear owners. Standardising patterns for auth, error handling, and naming prevents each team member from reinventing the wheel.
Common Mistakes
Mistake 1 — Letting collections grow organically without structure
Unstructured growth leads to confusion and duplicated work.
❌ Wrong: Adding every new request to the root of a single large collection.
✅ Correct: Periodically organise and split collections to reflect how the API and tests are logically grouped.
Mistake 2 — No ownership or review process
Without ownership, quality and consistency decline.
❌ Wrong: Anyone can change core collections at any time without review.
✅ Correct: Define owners and review practices for key assets.