Features
Everything you need to work with APIs the way you work with code.
What Voiden Does Differently
File-centric. Text-based. Git-native. These capabilities don't exist in traditional API clients.
Executable API Documentation Inside Markdown
The first tool where runnable API requests, block-level structures, and human-written explanations live side-by-side in the same Markdown file—and the editor can execute them in-place. This is the first true "live Markdown + API runner" paradigm.
Block-Based API Composition (LEGO for HTTP)
Every other API tool treats a request as a monolithic object. Voiden is the first to deconstruct requests into composable blocks (endpoint, query, headers, json, auth) that are independently editable, reusable across requests, and version-controlled as text. Function abstraction for API work.
Git-Native API Workflows With Zero Export/Import
Postman exports JSON blobs. Insomnia exports YAML. Bruno has collections but not docs. Voiden is the first where the native format is Markdown, everything is plain-text blocks, no proprietary collections, no export, no sync integrations. Git is literally the storage layer.
Unified Model for Design + Testing + Documentation
Design lives in OpenAPI. Testing lives in Postman. Docs live in Confluence. Voiden is the first tool where you design a request, test it, capture responses, write documentation above it, and commit—all in the same place. Three categories collapsed into one unified artifact.
Everything Is Text—Future-Proof & AI-Friendly
No proprietary workspace. No binary exports. No schema lock-in. Pure text all the way down. The first tool to make API knowledge a pure-text asset that's diffable like code, refactorable, greppable, AI-editable, and merge-friendly. Unlocks AI manipulation like code.
Reusable Blocks With Inheritance-Like Behavior
Auth blocks reused across files. Environment blocks defining variables. Header blocks toggled on/off. Blocks overridden at request level. The first inheritance-like abstraction for API request building. No other tool has this.
Programmable Interfaces
For the first time, you don't have a fixed interface for an API client. Compose it however you want. Your API needs headers? Add headers, nothing else. Needs body + headers? Add just those. Arrange blocks in an order that makes sense for your documentation. The interface adapts to your API, not the other way around.
Multi-Format Input Blocks as First-Class Citizens
XML blocks, JSON blocks, text blocks, file attachments, environment variables, multi-body types, raw and structured bodies—all as auto-previewable sections. Other tools handle these as UI toggles. Voiden is the first to treat content types as Markdown block primitives, not UI widgets.
Editor-Neutral, Tool-Neutral API Artifacts
Voiden files open in VS Code, GitHub, your own Electron client, can be parsed by future tools, CI-tested, generated, or linted. The first tool where API requests are portable across editors, repos, platforms, team setups, and future tools. There's no "Voiden workspace"—the repo is the workspace.