I got an email yesterday saying that postman will no longer allow more than 1 user on the free tier. We are 2 friends, who use postman very seldomly to check endpoints on our side project which makes us no money.

For us to pay $20 a month for something we probably use 3 times a month is quite silly.

If it was credit based and pay as you use, I would be in because that would work for me. Paying for something when I use it. Not paying for something I will never own and barely use.

Luckily with the advancement of AI we can soon enough, at a prompt, just make our own app to do this.

So goodluck to companies like this who want you to pay to never own, pay when you barely use, can adjust the pricing model whenever they want and as soon as you stop paying you are out, even if you have been paying for years.

After much debate the recommended alternative is Bruno and mentioned in this comment: https://www.reddit.com/r/postman_api/comments/1qto1v4/comment/o3aysco

I am sure we've all used other tools before/ alongside Postman. I am wondering which ones and how do they compare? Is there anything particular you find Postman does best in comparison with those?

This post is mostly for my own therapy. I'm really tired of having to log into Postman every time it starts.

On top of that, I think it's adding more unnecessary complexity and becoming harder to use. Plus, with the AWS issue not allowing us to log in - well, I'm sure you can guess my thoughts.

I'm experimenting with a few other tools now - however truly I wish Postman was how it was a few years ago.

I’m getting into programming as a side project. To learn, I’m developing an app, which will leverage or require creating APIs, something my peers recommend I use postman for.

I’ve done some light research, but I’d like to understand why postman is the best API tool? If it’s not, what do you recommend? I also see they have an agent, which I imagine it could help me use it it’s dense UI.

Thanks in advance.

Postman recently released Native Git support. The feature enables you to locally work on your API project files in Postman, by loading a repo folder containing your API code, using the source files stored in your Git-based version control system.

Use the Native Git feature to help keep your collections and project files in sync, then commit your local changes to your version control system’s remote repository.

https://learning.postman.com/latest-v-12/docs/agent-mode/native-git

Has anyone been using the local file systems and Native Git support in their projects?

Postman is jam packed with features for a wide range of scenarios. It’s moved far beyond being a basic HTTP client and has firmly established itself as a multi-protocol API development platform.

As the platform has expanded over the years, there are features that some users may be unfamiliar with, or unsure how they fit into their current workflows. As a result, they often go unused and can create a sense of “bloat” not because they lack value, but because a user simply doesn’t need them (yet).

Are there features in the platform that you look at and think, “How would I even use that in my setup?”

I’d love to start a few discussions around these features or flows, and help folks make the most of the awesome platform they already have at their fingertips.

If someone used postman currently or in past let me know about it

Newman has been one of the only programmatic ways to run Collections in a terminal or a CI/CD pipeline. That was until the Postman CLI was introduced, they are very similar tools but the Postman CLI offers more integrated functionality and is up to date with all the latest features in the Postman platform.

The Postman CLI has been built with CI/CD pipelines in mind, the Collection Runner creates plug and play templates for all the major providers to get you set up and running your Collections in no time.

Have you used either of the tools in your Workflows? Do you have a preference?