I am wondering that nobody mentioned https://www.usebruno.com/ yet. Works good enough for our Team. We are sharing the collection allongisde the applications code to keep both in Sync.
this post was submitted on 08 Mar 2026
16 points (90.0% liked)
Technology
82414 readers
3447 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
postman died years ago now. At least 3 but I think much more. httpie is the way to go along with the fork of insomnium after it went to trump.
I guessl postman pivoted - didn't die really. Now they are a more of a AI Infra company - https://blog.astromode.ai/blog/hello-astro-ai/
Also httpie is great - you may like Voiden.We opensourced some days back and are not just a postman clone !
Take a look here maybe : https://github.com/VoidenHQ/voiden
Interesting. I've been using Hoppscotch for two years now.
Curl is great. I use curl. Most developers use curl. But “you can call an API with curl” and “curl is enough as an API working environment” are two very different claims.
The problem is that real API work is almost never just one request typed into a terminal like some kind of beautifully minimalist Unix haiku. It usually turns into auth, environments, copied headers, reused payload fragments, request chains, documentation, testing, debugging, sharing examples with teammates, reviewing changes in Git, and trying not to break prod because you forgot to swap one token or one base URL.
At that point, people are not really using “just curl” anymore. They are using curl plus shell scripts, plus notes, plus env files, plus copied commands from Slack, plus random JSON files, plus tribal knowledge. Which is fine, until it becomes annoying, fragile, and weirdly hard to collaborate around.
This argument doesn't really hold up, honestly. That is all easily done with shell scripting, and shell scripts can be committed to source control and shared to other members of the team easily. This is what my team does for our common API needs. It even has ecosystem support in many places, such as popular openapi renderers providing curl command examples for routes automatically, being able to copy the exact request made by a web browser as a curl command from the network tab automatically, and so on.
I use curl for absolutely everything, including testing out my work for each and every ticket I work on. Been doing this for years now. It works great and has many, many advantages over property bullshit like Postman.
You either die a hero or live long enough to become the villain?
I’ve never understood why anyone needs Postman. Just write some JavaScript and run it with Node. It’s so easy to use the Fetch API.
Collaboration?
what about people that are not JS?