Voiden
Open SiteVoiden is an offline-first, Git-native API workspace that keeps requests, documentation, tests, mocks, and context in programmable Markdown files. It gives developers a file-based alternative to cloud API tools while keeping API work version-controlled and reviewable.
Added on June 25, 2026
Product Information
What is Voiden?
Voiden is a developer workspace for designing, testing, documenting, and mocking APIs in one Markdown-based format. Instead of storing API knowledge inside a hosted platform, Voiden keeps executable API files in the user's repo so Git remains the source of truth. Requests, docs, explanations, reusable blocks, and team context can live side by side and be reviewed like code. It is built for developers and teams that want API workflows to be offline, transparent, diffable, and free from vendor lock-in.
How to use Voiden?
- Download and install Voiden for your operating system.
- Create or open a workspace in a project repository.
- Write API requests, docs, variables, and reusable blocks in .void Markdown files.
- Run requests, test flows, or mocks directly from the same files.
- Commit the files to Git so API changes can be branched, reviewed, and shared with the team.
Core Features
- Markdown API files — Combines executable requests, docs, and context in plain text files.
- Git-native storage — Keeps API work inside repositories for diffs, branches, reviews, and history.
- Offline-first workflow — Works without requiring a cloud workspace or hosted sync service.
- Composable HTTP blocks — Lets teams reuse endpoints, headers, auth, parameters, and request parts like code modules.
- Unified API workspace — Collapses API design, testing, documentation, and mocks into one workflow.
- Open-source foundation — Provides a transparent alternative to proprietary API clients and shared workspaces.
Use Cases
- API development — Build and test requests while documenting the reasoning beside them.
- Team API reviews — Review API changes through Git diffs instead of exported collections.
- Offline engineering work — Keep API tooling usable without a hosted workspace dependency.
- Documentation as code — Store living API examples and explanations alongside implementation code.