Co-Founder @ ApyHub - Helping dev teams streamline their API Lifefycle

productHunt

github

Nikolas Dimitroulakis  • Peerlist

What if we had a tool that combined the simplicity of curl and the power of Obsidian?A few months ago, we open-sourced Voiden.It’s now at ~12k installs, mostly from developers who ran into the same frustration we did: API tooling slowly turning into cloud platforms with accounts, sync, proprietary formats, and static request builders that don’t really reflect how we actually build software.We tried a different direction.<h3>Voiden: An offline-first, git-native API workspace where everything is plain executable Markdown.</h3>The key shift is flexibility and composability.Most API tools lock you into fixed forms and rigid UI flows. Voiden doesn’t.Instead of a predefined interface, you get a programmable workspace: slash commands, reusable blocks, and composable primitives that let you shape the tool around your workflow, not the other way around.You’re not filling out requests in a UI. You’re building your own interface.<h3>Key ideas</h3>Composability over fixed forms<ul><li>No static request builders like Postman-style UIs</li><li>APIs built from reusable blocks (auth, endpoints, params, bodies, scripts)</li><li>Everything versioned and composed in Git</li><li>The tool adapts to your workflow, not vice versa</li></ul>Terminal-first execution<ul><li>A Voiden Runner to execute workflows directly from the terminal</li><li>Treat API workflows like scripts, not UI state</li></ul>Workflow-native by design<ul><li>Chain requests into flows instead of isolated calls</li><li>JS / Python / Shell scripting before and after requests</li></ul>Single-source workspace<ul><li>Specs, docs, tests, requests in the same Markdown files</li><li>No split between documentation, client, and automation tools</li></ul>Extensible &amp; programmable<ul><li>Slash commands + composable primitives</li><li>Plugin system built on plain text workflows</li><li>SDK for community extensions</li></ul>Agent-friendly from day one<ul><li>No proprietary formats</li><li>No hidden UI state</li><li>Fully readable, generatable, and executable from files</li></ul>We open-sourced it because we wanted something closer to how developers already work: files, Git, and the terminal — not another siloed platform.If you’re coming from Postman, Insomnia, or OpenAPI-based setups, you can migrate gradually by importing existing collections/specs into Voiden Markdown and evolving them in-place without breaking your current workflows.Curious what others think:<ul><li>What’s still painful in your API workflow today?</li><li>What tools are you sticking with, and why?</li><li>What would “fully programmable API tooling” need to get right for you?</li></ul>Happy to hear thoughts.

Voiden API Client: Lego for APIs

What if we had a tool that combined the simplicity of curl and the power of Obsidian?A few months ago, we open-sourced Voiden.It’s now at ~12k installs, mostly from developers who ran into the same frustration we did: API tooling slowly turning into cloud platforms with accounts, sync, proprietary formats, and static request builders that don’t really reflect how we actually build software.We tried a different direction.What if curl and Obsidian had an API baby?That’s Voiden.An offline-first, git-native API workspace where everything is plain executable Markdown.The core idea is composability, not forms.Instead of fixed request builders, you compose APIs from reusable blocks: auth, endpoints, params, bodies, scripts, flows. Define once, reuse everywhere, and evolve it like code in Git.From that, a few things naturally follow:<ul><li>A Voiden Runner that executes workflows directly from the terminal</li><li>Chaining requests into flows instead of isolated calls</li><li>JS / Python / Shell scripting before and after requests</li><li>Specs, docs, tests, and requests living together in one place</li><li>Plugins built on top of plain text</li><li>An agent-friendly format from day one — nothing hidden, nothing to reverse-engineer</li></ul>We open-sourced it because we wanted something closer to how developers already work: files, Git, and the terminal — not another siloed platform.If you’re coming from Postman, Insomnia, or OpenAPI-based setups, you can migrate gradually by importing existing collections/specs into Voiden Markdown and evolving them in-place without breaking your current workflows.Curious what others think:<ul><li>What’s still painful in your API workflow today?</li><li>What tools are you sticking with, and why?</li><li>What would “curl + composable editor” need to get right for you?</li></ul>Happy to hear thoughts.

Voiden API Client

Developer Advocate @ApyHub

CEO @ ApyHub

<a target="_blank" rel="noopener noreferrer" class="break-all link-break text-gray-500 hover:underline" href="http://Voiden.md">Voiden.md</a> is a developer-first API client with local storage, Git-integrated all based on markdown + offline support. Voiden's modular API design and open-source plugins offer flexibility and security without the bloat.Voiden is like all API clients should be: Free and open (no login required).Over the years, we found ourselves managing way too many tools just to work with APIs: one for api specs, another for docs, a third for tests, etc etc. Eventually it starts to feel more like a performance than actual work.So we built Voiden: A git-native, extensible, and lightweight client that brings everything: specs, docs, tests, mocks into one single place. No bloat, no lock-in, no "platform overhead." Just structured API workflows that don’t fight your tools or your team.A few things we care about:<ul><li>Reusability and composability : APIs as building blocks, not silos.</li><li>Structure over scatter : everything lives together in one workspace.</li><li>No sign-in required : you can use it without creating an account.</li><li>Free and open : We are building this with the community in mind.</li></ul>Just to be clear: The goal is NOT to replace OpenAPI, but to provide a layer around existing specs that feels coherent, hackable, and friendly to real-world dev workflows.You can check it out here: <a target="_blank" rel="noopener noreferrer" class="break-all link-break text-gray-500 hover:underline" href="https://voiden.md/">https://voiden.md/</a>And if you have feedback, suggestions, or just want to follow along:<a target="_blank" rel="noopener noreferrer" class="break-all link-break text-gray-500 hover:underline" href="https://github.com/VoidenHQ/feedback">https://github.com/VoidenHQ/feedback</a>We are still early, but would love to hear from you: what you like, what is missing. Nikolas