Open-source Postman alternative with type safety
Hello! This is Jeane and Samuel and we’re building RecipeUI. RecipeUI is an open source Postman alternative that uses TypeScript to statically type and autocomplete requests. We built this because current API tools don’t deal with the fact that some APIs are just painful to work with. For us, it’s usually error after error as we try to figure out how to properly form the first request. We recorded a demo to show you how TypeScript helps us autocomplete a request correctly. https://youtu.be/O_Mly_p-g5s How does our platform improve the developer experience? The analogy is…
In plain words
RecipeUI is an open-source API testing tool for developers that replaces Postman by using TypeScript for static typing and autocomplete. It helps developers construct API requests correctly on the first try through type safety, reducing trial-and-error when working with complex APIs. The tool provides parameter definitions and autocompletion similar to statically typed programming languages, addressing the common frustration of repeatedly consulting documentation and Stack Overflow while building requests.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
Hello! This is Jeane and Samuel and we’re building RecipeUI. RecipeUI is an open source Postman alternative that uses TypeScript to statically type and autocomplete requests. We built this because current API tools don’t deal with the fact that some APIs are just painful to work with. For us, it’s usually error after error as we try to figure out how to properly form the first request. We recorded a demo to show you how TypeScript helps us autocomplete a request correctly. https://youtu.be/O_Mly_p-g5s How does our platform improve the developer experience? The analogy is similar to using a statically typed language vs dynamically typed. Most API tools are dynamically typed. You’re guessing the params and relying on the request to magically work at runtime, only for you to go back to stack overflow or the docs when it doesn’t. We take the approach of defining parameters and the schema first. When you add a new parameter, you need to mention upfront if it’s required and what type it is (integer, string, boolean). While this can be painful in the beginning, it will save you and anyone you share this with the hassle of understanding how this API works. Our app is cross-platform on web and desktop. Our desktop app is <20mb and built on top of Rust with Tauri, NextJS, and Supabase. We open source our code because we want to be transparent about how API requests and secrets are handled (all local IndexDB). I built the first version of this at Robinhood when my colleagues were sharing bash scripts and internal APIs on slack to test things. I wanted to make it easier for anyone to use an API quickly and made use of our OpenAPI specs to generate a nice autocomplete API tool. Soon after, the Options team, then the Crypto team, and then the whole eng org at Robinhood adopted this tool! Try it out at recipeui.com! Please star us on GitHub if you like the product https://github.com/RecipeUI/RecipeUI.
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 1d ago · opentrailpaper.com
