Voiden : API Work - But Done Better - Working with APIs in your flow, plain markdown. Open Source.
by•
Voiden is an offline-first, Git-native API workspace where specs, docs, tests, mocks, and requests all live together in the same plain text files, as programmable Markdown blocks.
Build and Test APIs locally, version everything, and work the way developers actually do.


Replies
ApyHub APIs
Hey PH community 👋
A few months ago we open-sourced Voiden, the API client we built to bring a new perspective on how API work can be done.
Open sourcing turned out to be a good idea: the tool has been growing steadily (12k installs ❤️), mostly driven by developers who share the same frustration we had.
So what is Voiden?
Voiden is a free, local-first, git-native API workspace where everything lives in plain executable markdown files.
Yes, plain files. This includes everything: API specs, docs, requests, tests, and flows, all in one place, in plain markdown, versioned and tracked in Git.
Who this is for:
• Software Developers, QA engineers, and Technical Writers who work with APIs, who already work and collab on Git and care about clarity, simplicity and composable, Git-native workflows.
What the heck does composable mean? I hear someone ask.
Anyone with experience using Postman or other tools will know this: API requests are like static forms you have to fill in. In Voiden, requests are not like that. Instead, they are built from composable blocks (endpoint, auth, params, body, scripts). These blocks can be added wherever you want, reused, replaced, versioned, or shared, just like code. Everything is plain text and fully executable.
Core principles we built it on:
• free and local-first, plain text executable files
• composable through reusable blocks - define once and reuse across files, (like functions when coding)
• collaboration happens in Git, where developers already work
• no accounts, no lock-in, no cloud dependency
Our inspiration came from two places:
• curl — for its simplicity
• Obsidian — for its composability and power through plain files
Our most recent and proud update is that we added the Voiden Runner, so you can execute your API workflows directly from the terminal!
Other important features that we+the community have added:
• Chaining multiple requests into flows
• Real scripting (JS / Python / Shell) before & after requests
• A Voiden “skills” layer so tools like Claude/Codex can operate on .void files
• SDK for community plugins so we can get the tool extended: https://voiden.md/plugins. The first community plugins are already there and are super cool.
We are still early, and this launch is really about meeting more builders who care about this space.
I wish I could give a discount coupon but the tool is already free forever.
👉 Download (mac, windows, linux) : https://voiden.md/download
👉 Repo: https://github.com/VoidenHQ/voiden
👉 Changelog: https://voiden.md/changelog
Would love your feedback, especially:
What’s the most painful part of working with APIs today?
What's keeping you use Postman or any other legacy tool?
How would you extend Voiden to use it in your specific flows and use cases?
Thanks a lot,
Nikolas
as someone who tests apis daily, i like that this is git native. reviewing request changes along with docs and tests sounds much more practical than hunting across multiple tools. great idea and best wishes for the launch🙌
ApyHub APIs
@simranxdhindsa thank you! yes, it actually happened to us: we were working on Postman for the api work, confluence for the docs, slack for the context etc. So having everything in the same file is what we believe in!
Very cool approach to the problem, what did you build the desktop app with? Electron, Tauri, or something else?
Dropped a star on the repo.. congrats for launch @nikolas_dimitroulakis
ApyHub APIs
@vikramp7470 thanks Vikram!
We built it with Electron - here is why :)
https://docs.voiden.md/docs/getting-started-section/getting-started/why-electron
@nikolas_dimitroulakis Thanks for sharing