[konaraddi]

Your experience at Robinhood is relatable but I’m not sure I follow how RecipeUI would benefit us more than Postman.

Our team has OpenAPI specs but we have a rough time sending requests because each team member has valid requests for some subset of the API surface of a given service (from working on subsets of the service) and there isn’t a common repository for valid requests covering the entire surface area. On top of that there’s multiple forms of auth so there’s a flow to execute to obtain the auth token for a given request. Every team member has written their own scripts in various languages for one or more flavors of auth. We’re often sending each other one-off scripts or postman collection exports, or sharing fiddler traces or even tokens.

Would RecipeUI benefit us more than Postman?

[nomercy400]

Postman is moving more and more from a local tool tp a cloud-based tool under the company's control.

Exporting your data from Postman has been made more difficult over the last few releases and now the local scratchpad is about to be removed in favor of using the free account in two weeks time.

These actions make me worry that Postman will soon no longer be a free tool or will use my collections and data for their own purposes (e.g. AI training).

I need an alternative, and maybe RecipeUI can fill that gap. Or I will be stuck on Insomnia.

[rgblambda]

>and now the local scratchpad is about to be removed in favor of using the free account in two weeks time.

I was under the impression that you could continue using scratchpad so long as you didn't sign in (Which I never felt the need to).

[Volbohel]

Currently, we're not convincing enough for the team use case that tackles many of the things you're describing (especially auth). Thanks for the feedback!!!

We're closely working on an API Storybook that'll be more native to a codebase and a service. Would love to reach out and hear more about your Postman experience!