Build API Requests
Like You Build Code
Plain text. Reusable blocks. Git-native. The first API client where requests live inside your repo — not some cloud workspace.
The Problem
Your API knowledge is scattered.
Every team has this same mess. Five tools. Zero coherence.
Before Voiden
- ✕Postman / Insomnia — the requests
- ✕Notion / Confluence — the docs
- ✕Slack / Jira — the context
- ✕README files — the examples
- ✕Git — code — but not the API stuff
Source of truth? Nobody knows.
With Voiden
- ✓Everything lives in .void files
- ✓Committed alongside your code in Git
- ✓Diffable, reviewable, branchable
- ✓One format — requests + docs + context
- ✓Offline, no cloud, no account
One repo. One source of truth.
Voiden fixes this.
API Work, Treated Like Code.
File-centric. Text-based. Git-native. Built for developers who version-control everything else.
Executable API Docs
Requests, docs, and explanations live side-by-side in plain Markdown — and execute in place. No switching tools.
LEGO for HTTP
Decompose requests into composable blocks — endpoint, headers, auth, params. Reuse across files like functions.
Truly Git-Native
No export. No sync. No JSON blobs. Pure Markdown. Git is the storage layer — your repo is the workspace.
Design + Test + Document
The first tool to collapse API design, testing, and documentation into one file, one format, one workflow.
From Developers
What people are saying
Tired of Platforms That
Think They Know Better?
Most API tools assume they should run your workflow. Voiden gives you structure, flexibility, and a workspace you actually control.