this post was submitted on 01 May 2026
59 points (95.4% liked)

Programming

26753 readers
180 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
59
Built an API dev tool and got 11k+ installs already, this is what happened since we open sourced. (github.com)
submitted 17 hours ago by dhruv3006@lemmy.world to c/programming@programming.dev
12 comments fedilink hide all child comments
 

Hey there,

A few months ago we open sourced Voiden, an offline API client we originally built to replace Postman internally.

Voiden now has around 11k installs and growing every day. ❤️

Core principles we built it on:

  • free and local-first
  • file-based, all plain executable markdown
  • composable through blocks
  • collaboration in Git, where devs are working already

The main thing is that in Voiden, API requests are not (static) forms. They are built from blocks (endpoint, auth, params, body) that can be used, reused, replaced and version in Git, just like code. And all that in plain executable text.

Our inspiration:

Our inspiration was curl, and how simple it is, and obsidian, because of how powerful it can be.

Who this is for:

Developers, QA, Technical Writers working and collaborating on APIs.

Progress:

Since open sourcing, almost everything that we shipped came from actual users, feedback and contributions that pushed the tool in a few interesting directions. You can check our change-log here: https://voiden.md/changelog

A few highlights:

  • Composable API workflows: Voiden lets you build reusable .void files that can be combined into flows, run multiple requests in sequence, and use real scripting (JS/Python/Shell) before and after requests.
  • Added a “skills” layer so tools like Claude/Codex can operate directly on .void files and request blocks.
  • We added an SDK for community plugins.
  • & more...

Feedback:

This project is now mostly shaped and driven by community ideas and contributions. Welcome to join and help us make this even more awesome.

There is no account setup, its free and totally offline.

GitHub: https://github.com/VoidenHQ/voiden

Download: https://voiden.md/download

you are viewing a single comment's thread
view the rest of the comments
[–] atzanteol@sh.itjust.works 2 points 12 hours ago

From both a tooling and user POV.

We intentionally started from Markdown because we wanted .void files to stay standards-compliant and not reinvent a new document format.

Unless I'm missing something you kinda have though? You've got a frontmatter bit followed by a MD document with a "footer" that has configuration in it?

We could put everything into one YAML object, but then the file becomes more like a config file than a Markdown document.

It seems like a config file to me. But reading through your documentation about blocks it seems like you're aiming to be something like Jupyter for REST? It's very confusing.