Postman users lose API request edits to manual saving
API developers using Postman collections have to save request changes manually, sometimes across dozens of requests. The reports describe missed saves leading to stale collection runs and wasted debugging, with added confusion because some fields appear to save automatically while request data does not. The supporting reports are from 2018–2020, so first check whether this behavior still exists in current Postman.
For API developers using Postman collections. Mentioned from Sep 2018 to Oct 2023 on GitHub and Hacker News.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 2.0/10
- Pain
- 5.2/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I ran a collection assuming it would save all the current request changes and spent a little while debugging a 404 response only to discover I hadn't hit "save" on one of the requests
Add as an optional setting?? Its super annoying to go through 50+ api requests and figure out which ones are
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks