But then how did Postman became so popular - we can’t deny it became the default.

subscription based right?

But whyyyy?

Awesome - would love some feedback !

Just fyi - voiden too is not us based.

Happy to help out - Check out our docs too - https://docs.voiden.md/docs/getting-started-section/intro.

I am making a GitHub repository https://github.com/dp1620/awesome-markdown-devtools for markdown tools - I will include revealjs.com along with sli.dev

Thanks - do give us a feedback :)

imo Swagger is good for looking at the API. For local and odd setups for example If you need shell scripts swagger becomes pretty rigid.

You can join our discord to meet people who are using it : https://discord.com/invite/XSYCf7JF4F

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.

That is the gap Voiden is trying to solve.

So for me it is not “curl vs Voiden.” curl is a low-level execution tool. Voiden is a workspace for actual API work: writing requests, organizing them, reusing pieces, documenting them, testing them, versioning them in Git, and not duplicating the same headers/body/auth setup 45 times like a person slowly losing control of their life.

This one is pretty great!