my goodness - I saw this pretty pretty long back.

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

caffein rich whey protein.

the best possible answer.

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.

Hey, that’s a fair comparison. .http files are actually one of the closest things conceptually.

The difference is mostly in how far the idea is pushed.

.http files are basically request definitions written in HTTP syntax. They are great for sending requests and keeping them next to your code.

Voiden treats the Markdown file more like an executable API workspace. Requests are composed from reusable blocks (endpoints, auth, headers, params, bodies, etc.), so instead of copying similar requests around you can structure them like small building blocks and reuse them across the file. That becomes useful once an API grows and you start repeating the same pieces everywhere.

Another difference is that the file can mix documentation, explanation, requests, tests, and scripts in the same place and actually run them. The goal is that the file itself becomes the living artifact of the API workflow rather than just a request list. And since everything is still plain text and Git-friendly, you can keep it alongside the codebase the same way you would with .http.

If someone is happy with .http files they probably don’t need Voiden. The idea is more for teams that want the requests, tests, and docs to live together in one executable spec rather than spread across tools.

Do you use .http mostly for quick testing, or do you keep full API workflows in them?

This is actually a great comparison ! Thanks for these words !

Thats pretty cool !

I posted this for womens day - a really really under rated person.

Collaboration?

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.

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

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.

You bring a regulation - can you really enforce it?

But a true easy to use discord alternative is still not there.

This one is pretty great!

We should always have more alternatives to chose from - good to see so many players.

I think the real breakthrough will come when we will be able to make powerful microbatteries.