Voiden Blog
API tutorials, resources & updates
Nikolas Dimitroulakis
Obsidian vs Voiden: When to Use Both
Obsidian is a notes workspace. Voiden is an API workspace. Where one job ends, the other begins, and why a lot of developers should be running both.
Phurpa Tsering
Migrating from Insomnia to Voiden, Without Starting Over
How to migrate from Insomnia to Voiden: import your Insomnia v5 export as plain-text .void files, with folder structure, headers, params, bodies, and auth included, then version everything in Git.
Davinder singh
Voiden 1 to Voiden 2: the changes that matter
Voiden 2 shipped across four releases. Here are the changes that actually change how you work: the CLI runner, a protocol-agnostic core, hierarchical inheritance, and preview tabs.
Nikolas Dimitroulakis
curl Is Great. The Mess Around It Isn't.
curl is a brilliant execution tool. But real API work is auth, environments, chains, docs, and Git, and that's where "just use curl" quietly stops being true.
Nikolas Dimitroulakis
Pre & Post Request Scripts Beyond the JavaScript Sandbox: Real Python and Shell in Voiden
Every API client runs pre- and post-request scripts in a JavaScript sandbox — and there's an architectural reason why. Voiden is the only one that runs them on real interpreters: JavaScript, Python, and shell.
Phurpa Tsering
How to Test WebSocket Applications: Functional, Load, and Debugging
A practical guide to testing multiuser WebSocket applications: functional testing, load testing with k6 or Artillery, debugging, and keeping WebSocket tests in Git.
Nikolas Dimitroulakis
Why Voiden Is Built on Electron
An honest look at why we chose Electron for Voiden — the real tradeoffs, the real numbers, and what the community pushback taught us about talking about them.
Nikolas
Request History in Voiden: Never Lose Track of a Request Again
How Voiden's Request History turns every API request into a local, replayable snapshot — what it records, where it lives, and how to get your last working request back.
Nikolas
What Is Git? Version Control Explained for API Developers
A plain-language guide to Git for developers who work with APIs: commits, branches, staging, remotes, merge conflicts, and the beginner mistakes that actually matter.