RARattlesnakeJake·Nov 21, 2025Submission
After four years, Postman adds color-coding to environments
2 points · Open discussionpostmanlabs
postman-app-support
OPEN SOURCE2017–2025
postmanlabs / postman-app-support
postman-app-support
Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
16Distinct people
18Mentions
0Explicit recommenders
6KGitHub stars
What to know before exploring
What it is
Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year18 dated mentions
Observed mentions: 2017-03-24 00:04:46 UTC to 2025-11-21 14:02:38 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
18 sourcesI ditched Postman for Insomnia (Open source) after Postman refused to adhere to customers to disable auto-updates for 6 years+. I checked on their GitHub issue tracker and it turns out, the solution was to upgrade to their "Enterprise plan".
https://github.com/postmanlabs/postman-app-support/issues/69...
So, I said fuck it and switched to a real, open source alternative, Insomnia, instead:
https://insomnia.rest
In Postman which I thought worked locally on my computer, is downDo you have any details on the equivalent Postman change? How long ago did Postman force users to create an account? I found this github issue, but I'm not sure if it's what everyone keeps referencing.
https://github.com/postmanlabs/postman-app-support/issues/12...
In Insomnia REST client now requires an accountPostman founder here. Thank you HN community for highlighting this feature. We have been seeing gRPC usage exploding especially in microservices driven architectures and we are looking forward to the feedback we get on the feature.
A few other observations on comments that I read through:
1. Postman leans towards adding UI affordances instead of hiding them. This can irritate experienced developers at times who already know the complexities of HTTP or other protocols but that is really how new developers find their way around. So while it is attractive to have 1000 options hidden behind a command line interface, nobody uses 995 of those features. We are getting better at building experiences for both experienced and new developers. Also, I don’t believe reading man pages of git or curl is a better experience.
2. Performance is a huge area
Read the rest
for improvement. More to come in subsequent releases this year.
3. Our roadmap is community driven: https://github.com/postmanlabs/postman-app-support/issues. Raising more investment helps us do more. We have built a business model around doing the maximum for every developer on the planet while also providing value to companies so we can charge for it and continue development. I find it fair that companies spend hundreds of millions of dollars on salaries can pay some money for improving their productivity by spending in developer tools.
4. API Development is a huge and growing area and developers are spending more and more time working with APIs rather than their IDEs. API Design, documentation, and testing are areas that a large number of developers tell us they wish they had better tooling for. Most of their time is spend pointlessly in trying to figure out how an API works (in some cases whether an API even exists). We decided to take Postman in those areas even though paradoxically it might lead to “less” Postman usage. (The faster people figure out an API the fewer number of calls they have to send)
5. Finally, it is good to see here a call for fewer features which we insist internally as well. Unfortunately at some point some part of the community is upset that we are NOT adding features (just see the gRPC thread on our issue tracker!). We don’t see issues to remove features as much as we have requests to fulfill. We do remove features consciously but it is a hard problem, so we default to adding them slowly.
This is OP's issue: https://github.com/postmanlabs/postman-app-support/issues/38...
In Postman Now Supports gRPCI'v really had it with Postman. I don't get the priorities. Slow and sometimes confusing and auto-saving the configuration is still impossible(!) and I just keep loosing % of work done every single day. [0]
Glad to see lots of comment with alternatives here.
[0] https://github.com/postmanlabs/postman-app-support/issues/81...
In Postman Now Supports gRPCThis sounds unbelievable but it seems to be true? https://github.com/postmanlabs/postman-app-support/issues/10...
In Postman Now Supports gRPCIt's a socially-networked gui around curl commands! I need to dig up the quotes, but in Bruce Sterling's sci fi book Heavy Weather, he says that no one pays for sotware, except groupwere, which everyone begrudgingly pays out for.
I gotta say though I am super unimpressed by the Postman team's ability to prioritize / do the right things. Basic capabilities likes SOCKS proxies or proxies DNS are just totally awol, making this tool practically useless in a wide variety of everyday development circumstances. Ticket's been open 6 years now[1]. Really not that hard to add, would make such a powerful difference.
[1] https://github.com/postmanlabs/postman-app-support/issues/13...
In Postman raises $225M Series D at $5.6B valuationIf your blind like me the advantage is that Hoppscotch actually makes an effort to be accessible [1] while Postman does not. [2]
[1] https://github.com/hoppscotch/hoppscotch/issues/1106
[2] https://github.com/postmanlabs/postman-app-support/issues/31...
In Hoppscotch – A free, fast API request builderI'm probably going to try this out for its websocket support. I use Postman, they've had a long-standing open issue to add it with no ETA/progress: https://github.com/postmanlabs/postman-app-support/issues/40.... Haven't used Insomnia but they don't mention websockets anywhere in their docs so I assume they don't support it either: https://support.insomnia.rest/search?collectionId=&query=web...
In Hoppscotch – A free, fast API request builderI'm planning on migrating all our Postman documentation away to https://github.com/slatedocs/slate if that's what you mean.
PS. The reason why we're moving away from Postman is due to some tiny issue[1] that has caused lots of "you need to click here to see everthing" conversations.
[1] : https://github.com/postmanlabs/postman-app-support/issues/57...
In Ockam built a JAMStack site and it's 100% Open SourceI'm not sure if accessibility is something you focused on or if you just got lucky but according to this thread I need to give insomnia a try since Postman is not concerned with making there software even marginally usable if your blind.
https://github.com/postmanlabs/postman-app-support/issues/31...
In Announcing Updated Postman Plans and PricingAsk HN: Using HTTP GET with request body
We are doing a RESTful service that is non-public. For a request that is read-only and potentially uses 20+ parameters, we are planning to implement it as a GET request that will pass these parameters in the body.
I have seen the well known announcement by Dropbox in 2015: https://blogs.dropbox.com/developers/2015/03/limitations-of-the-get-method-in-http/ and the response in Hacker News: https://news.ycombinator.com/item?id=9133469
As I understand it, there are three potential issues with a GET with request body:
(1) Not all servers will support this.
(2) Not all tools will support this (POSTMAN added support this year: https://github.com/postmanlabs/postman-app-support/issues/131)
(3) There is not yet a consensus on GET with request body. (For example, is Dropbox still using a POST)
I am not finding too many recent statements about
Read the rest
this, I wanted to open up the question here and see what the current opinions are.
I heard that ElasticSearch is using GET request parameters in the body. It sounds like there are some who are against this approach:
https://stackoverflow.com/questions/36939748/elasticsearch-get-request-with-reques…
(1) Does this make sense for a private server? (The answer here seems to be yes -- unless I am missing something)
(2) Does this make sense in general? If the tools needed support it, what is wrong with implementing a RESTful service that requires GET request parameters in the body?
Postman Disk space used multiplies after each update (2018)
1 points · Open discussionShowing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.