{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreigczwtts6qlcof7llhixxl53wn753wc6r76b37ltdqxguntm3ry5i",
"uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mgsdxiv5fbw2"
},
"coverImage": {
"$type": "blob",
"ref": {
"$link": "bafkreibar4rlencl63bx555cbywruxrst3226k2gu3s7qtolzorsq57tli"
},
"mimeType": "image/png",
"size": 45968
},
"path": "/post/47030474",
"publishedAt": "2026-03-11T13:38:46.000Z",
"site": "https://programming.dev",
"tags": [
"Opensource",
"dhruv3006",
"4 comments",
"https://github.com/VoidenHQ/voiden",
"docs.voiden.md/docs/plugins/build-a-plugin",
"github.com/VoidenHQ/voiden",
"voiden.md/download"
],
"textContent": "submitted by dhruv3006 to opensource\n21 points | 4 comments\nhttps://github.com/VoidenHQ/voiden\n\nVoiden is an offline-first, git-native API tool built on Markdown Voiden is an API client we have been building that takes a different approach from most existing tools.\n\nIt didn’t start with the idea of “building a better Postman”.\n\nA bit of background. Over time, API tooling has become heavyweight: cloud dependencies for local work, forced accounts, proprietary formats, and workflows that break the moment you are offline. On top of that, time wasted on fixing API specs that don’t match the code, docs in separate random tools, tests also separate and an overall governance mess. Not to mention collaboration.\n\nSo we asked a simple question: What if an API tool respected how developers already work?\n\nThat led to a few core ideas:\n\n * Offline-first , no accounts, no telemetry\n * Git as the source of truth.\n * Plain text files: specs, tests, and documentation live together in Markdown\n * A programmable interface instead of static forms: requests are composed from reusable blocks (endpoints, headers, auth, params, bodies, etc.) that you can structure the way you want\n * Plugin system for extending functionality rather than bloating the core with new features Some of our core plugins include gRPC,GraphQL,WebSockets,etc…\n\n\n\nWe have just also updated our docs to welcome community plugins, so teams can extend the tool for their own workflows or integrations. docs.voiden.md/docs/plugins/build-a-plugin\n\nWe opensourced Voiden because extensibility without openness just shifts the bottleneck. If (API) workflows should be transparent, the tools should be too.\n\nWelcome to try out and share feedback- happy to chat with everyone.\n\nStrong opinions are encouraged. :)\n\nGithub : github.com/VoidenHQ/voiden\n\nDownload here : voiden.md/download",
"title": "Voiden - A Markdown based Open Source Alternative to Postman"
}