Its an alternative to Monolithic Requests - Voiden has composable blocks which are an alternative to copy pasting entire request objects. We do not lock in collections in cloud like other api clients like postman and have a file centric and git native approach. Also we offer a unified toolchain - for design, testing, and documentation as an alternative to juggling multiple disconnected apps.
Well having decent documentation is kind of rare.
Thanks for this.
They do !
Here’s how to get started : https://docs.voiden.md/docs/getting-started-section/getting-started/openapi-imports
Unfortunately I agree but there are a few that are different, for example have you tried Voiden ( https://voiden.md/) maybe? We opensourced a few weeks back.
Postman was great when it made APIs simple, but over time all the accounts, cloud sync, and extra features kind of slowed down the core workflow. And then a lot of clients just ended up copying that model instead of rethinking it.
On the optimistic side we are seeing some stuff that want to rethink this: tools like Voiden and Yaak with a few new approaches like Git-native workflows, reusable request pieces, more composable setups basically making API work feel more like actual dev work again.
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!
Everyone seems to hate this template.