Most API tools treat requests as monolithic blocks - Voiden doesn't

Source: Dev.to

Background

Legacy API tools such as Postman and Insomnia are built as platforms first—offering accounts, workspaces, cloud sync, dashboards, and paywalls—while the actual API work often comes second.

In contrast, many newer API tools are quickly coded, look sharp, but are thin abstractions over fetch calls. They lack a clear model for workflows, versioning, or how teams evolve their API usage over time.

Voiden

Voiden sits between these approaches. It is the result of years of synthesizing feedback from real developers—backend engineers, platform teams, and API designers—observing where workflows break, collections rot, and collaboration becomes painful.

Voiden is an offline‑first, Git‑native API tool where requests, specs, tests, and documentation live together as executable Markdown inside your repository.

Live Markdown + API Runner

• API requests, reusable blocks, and human explanations reside in the same Markdown file and can be executed in place.
• No request‑builder UI, no context switching.

Composable Request Blocks

Unlike tools that treat a request as a single opaque object, Voiden breaks a request into composable blocks (endpoint, headers, query, JSON, auth, etc.).

• Define a block once and reference it across multiple requests.
• When a block changes, all dependent requests stay in sync automatically.

Extensibility

Voiden is intentionally lightweight, with core functionality kept lean. Additional capabilities are provided via a plugin system, including:

• gRPC
• GraphQL
• WebSockets (WSS)
• Assertion blocks

Plugins can be added or omitted as needed, allowing the tool to grow without becoming bloated. The community can easily extend Voiden with new plugins.

Workflow Compatibility

Voiden works around your workflow, not the other way around. If you prefer to avoid bloated SaaS API clients, Voiden offers a flexible, developer‑centric alternative.

Getting Started

• GitHub:
• Migrate from Postman: