API teams lose tests and setup when refreshing Postman collections
When an API specification changes, teams using generated Postman collections struggle to update them in place without losing tests, authentication, scripts, or custom request data. The evidence describes teams deleting and reimporting collections or doing manual work; one request specifically asks to automate updates in CI before running Newman tests. Most of these reports are from 2020–2021, so the current scale of the problem needs validation.
For API developers and QA engineers maintaining Postman collections. Mentioned from Nov 2015 to Sep 2025 on GitHub and Hacker News.
15 different people described this problem in 7 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.9/10
- Frequency
- 10.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Ability to Update Collections when manually importing an API Spec Is your feature request related to a problem? Please describe. Currently when manually importing an API spec that was not built in postman, the user has no option to "update" a collection that was previously created based off of that spec.
obieo on GitHub (postmanlabs/postman-app-support)Aug 2020+55 upvotesAsked for a toolHas a workaroundWe'd like a seamless workflow that doesn't require manual intervention. When the spec changes then we should be able to run a command from CI pipeline to update the collection and then run the postman tests using Newman using the updated collection
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 13 more quotes from people who have this problem
- Current workarounds, existing solutions and risks