3 ms·
I've posted this in a reply comment but here's a top level comment as well. The main reason I dislike Postman is not actually the web based interface, but the
by Cthulhu_ 5y ago
I've posted this in a reply comment but here's a top level comment as well.
The main reason I dislike Postman is not actually the web based interface, but the fact it keeps its data files to itself to try and push teams to using their cloud offerings.
If a HTTP client stores its requests and configuration as a plain text file, it becomes really easy to manage it alongside a codebase and share between teams. But alas.
That said, I have seen a paid version of postman be used in a company and it worked really well. But it's an expense.
An alternative is what is mentioned in the top comment at this time, VS Code's Rest Client or Intellij's built-in rest client, which use plain text files (.http files) with plain text based HTTP request definitions. Those can be executed directly, without hidden functionality, and stored / updated / diffed in git.
Another alternative - but this is restricted to HTTP based APIs - is Swagger/OpenAPI combined with Swagger-UI, which is both a documentation page and a demo page. The UX isn't the best, but it works very well imo.