Spent months thinking about scripting in API tools.
Honestly, most tools don’t go far enough. They stop at JavaScript, a limited sandbox and a system that is not really extensible.
That works for small tests, but it can also quickly break down when you want to start building real, multi-step workflows.
We wanted to go further. So we spent time observing how developers actually work with APIs, talking to them, and learning from the patterns and frustrations in real workflows. We saw token rotations handled manually, small helper scripts scattered across repos, and tools that forced engineers into JavaScript even when their stack was Python, Go etc.
So for Voiden Pre & Post Request Scripts adapt to how developers work.
- JavaScript + Python (first-class): use the language you already know and trust
- Real runtimes & package imports: run actual code, import libraries,
reuse existing logic - Stateful workflows: share variables, store data, and chain requests dynamically
- Orchestration-ready: automate multi-step flows, token rotations, and dependent API calls
Again, it's a basic principle we had from day 1: API tools should not dictate how devs think. It should adapt to how they work.
We believe this is one of the most powerful scripting systems available in any API client today.
And we are just getting started.
🌐 Beta: https://voiden.md/download#beta
📂 GitHub: https://github.com/VoidenHQ/voiden
Top comments (1)
link to docs: https://docs.voiden.md/docs/core-features-section/voiden-blocks/pre%20&%20post%20script/pre-script