We use Postman for our day-to-day operations, investigations, and other tasks.

The value of Postman's collaboration tools, such as version control and team workspaces, is significant in maintaining and updating API projects, even though we don't use workspaces. I have an idea about the team workspace where I can invite my colleagues, and we can run on the API calls and all the functionalities we try to implement, which are transparent and visible to the other team members or invited members with access to that workspace. It's more about personal workspace and shareable workspace; you can do all your own work and shareable is something that you have to explore with someone else.

We don't have Postman integrated with our CI/CD pipelines; that's not under my expertise, but we do have it.

We use Postman Web; it's not that we bought Postman and integrated it with our cloud environments. It's only an end-user Postman we utilize, not at a full scripting level.

From my perspective, Postman offers great features, so I get a better opportunity to run bulk tasks through single command lines and single APIs, and we have an internal Postman AI tool, which helps improvise the code and analyze the quality if you find any errors. Instead of going into Google or ChatGPT or Gemini, the internal Postman AI is superior, and we also schedule certain calls for our operations. It helps reduce almost 90% of the manual effort in processes that we feel could take a lot of manual work.

I would appreciate seeing Postman become more automated. We need easier calls in the workflows. I tried to utilize the flows, but it wasn't clear under the documentation, and implementing it required more investigation. Eventually, we understood it, but we still need improvements in flows.

The environments, respective repositories, and collections we have are good for segregation. Another excellent aspect is that when we close Postman, it doesn't straight away terminate everything; it stores the values, which is very useful, as it has data storage and response storage benefits.

Regarding specific features that I'd want to see included in the next releases of Postman, I must say I'm not very involved with it daily. We utilize it in a randomized way—a couple of days or weeks in a month—based on our work dependencies.

Postman was one of the best solutions we found while researching, and we got training on it. We have been utilizing Postman from day one during training sessions, and when we checked for others, Postman offered a much easier user experience than the alternatives.

I can say that I'm using Postman with the REST APIs. The adaptability of Postman's support for both REST and SOAP APIs, as well as various data formats such as JSON and XML, is not something we do at that level of Postman. It's about our single time usage or consecutive runs usage, but not at that automation level. We do use a little scripting with REST APIs.

I don't utilize Postman's monitoring capabilities. I don't know anything about the pricing, as I'm working only on the free version of Postman.

Given my experience with Postman, my advice for other organizations or users considering it is that it's pretty simple to use Postman, except for the flows. For the flows, I expect to see more live examples or test cases within the documentation to utilize and learn it more effectively.

I would rate Postman as a product an eight out of ten.

I have not yet used Selenium within the last 12 months; I just completed some POCs, but not actually used it.

There are many other tools that we are working on aside from Selenium.

We use TestIM, Katalon, and those are all UI function tools, and in terms of API, we are working on Postman and Ready API.

Personally, I have been using Postman for seven or eight years plus.

Postman is the easiest tool I know, there's no challenge at all. In fact, most of the Postman testing that we do is all locally, but when I say deployment, that deployment is for cloud, and whenever we want to run it in CI/CD, it's all on Azure and AWS, so it's one of the easiest things.

Postman doesn't require much time to deploy, just a few minutes or so. This applies to almost all the tools that we're working on; Selenium is one of the most mature automation framework tools we have, so there's no issue with that.

I don't find anything difficult based on my experience, but the organization of collection, running, and assertions in the last few years have been really good for me; the environment is managed well.

Postman is one of the easiest tools; I have not seen anybody complaining because it's just one Google search away.

It's easy to navigate because tons of documentation and examples are available.

It has helped significantly since it is easy; the development team and QA team all use it, enabling us to automate almost 70% of our APIs using Postman.

I wouldn't say there are weak points or drawbacks for Postman, but there are definitely features that could be improved; for example, if you derive it from Ready API, maybe Postman can be a good contender and replicate some features such as more scripting and control over API calls.

Personally, I have been using Postman for seven or eight years plus.

The technical support for Postman is all good.

Positive

I don't have exact numbers, but since 70% of APIs are automated, you can say that a minimum of 50% time is saved when comparing manual to automation; for example, if I take 10 hours to test an API for every release, I can do it in half that time or much faster.

Postman is much cheaper than the other tools.

I am not aware of the current pricing for Postman because that's taken care of by the client; we just pay and they simply create options.

On a per-person basis, I would rate it seven to eight for pricing because whatever they are offering at that price gives huge satisfaction.

We have various projects, and not all the projects use Postman, as we use REST Assured, Ready API, and Postman in two ways: one is manual, where you feed and update the data every time, and the second is automation, where we use both manual and automation methods.

I would recommend this product to others because it's much easier, has a cheaper free version available, is widely used, and has a lot of examples and documentation available.

There are over 50 users of the free version, but for the paid version, there are five plus users.

We're talking about engineers, and that number might vary, but that's the current status I can estimate.

On a scale of one to ten, I rate Postman an eight.

In our development, I basically use Postman just to test the APIs.

With the help of Postman, I explore API training and other features. It is beneficial to have flexibility, especially with API chaining. This feature allows me to combine and, with the help of some code, run multiple APIs at once. API chaining is a very good concept and easy to implement.

Since I am not exhaustively using Postman, I never think about its limitations. 

I have worked with Postman for the last four years. For four to five years, I have worked on Postman. Postman is a good tool.

I would say the scalability is very good since it is very scalable. I have never faced a problem.

I basically do not go to support. So I cannot tell you more, though I have some experience.

Neutral

I was using SoapUI before basically for web services. At that time, the web 3D AI concept was not implemented in the market.

Initially, the setup is a little bit complex. Whenever a user comes to Postman for the first time, it is just a bit complex since they do not know where to start and what is the structure. However, once a user has gone through the things, it gets easy. Other tools are easy to use for the first-time user.

Postman is easily available. Most of the features are already available, and people can learn and benefit from them. The other features are also very good in collaboration and API chaining. 

It is easy to maintain and easy to share with other users. For example, if I have created a collection, I can share the collection with others and get a benefit. 

This product deserves an eight out of ten. 

The primary use case for Postman is mostly for unit testing of the APIs. Additionally, I have developed scripts for end-to-end testing of the APIs.

One of the biggest advantages of Postman is its user-base approach. All collections created in Postman are not maintained locally and are instead maintained on the server, making it easy for me to continue work from anywhere if I log in with the same credentials. Any team member can continue the work as nothing is maintained locally.

One of the features that is missing in Postman is reporting; it's very basic. If they could enhance it and provide a browser-based dashboard view, it would be beneficial. 

Postman is limited to request and response kind of validation. If they can enhance it to have a database kind of validation like we have in ReadyAPI, it would be better. This feature would allow the response to be validated in the database as well.

I have been working with Postman for more than three years.

The solution is open-source and does the work required for day-to-day API testing activities. I would rate it ten out of ten for stability.

Postman does not have database validation available, which affects its scalability. If this option were available, I would rate it ten out of ten. Currently, I would say it is around seven or eight out of ten.

There is a lot of support available through forums and user groups, which has been sufficient for me. I hardly reach out to the vendor for support because the forums provide the required help.

Positive

To start with, Postman is a good option, but ReadyAPI is a commercial tool with lots of built-in features. If cost isn't a concern, ReadyAPI is better, however, if it is, Postman is still a viable choice.

The initial setup of Postman is very simple. There is an option for both browser-based and desktop applications. The desktop application requires installation, which is straightforward, while the browser option is also available and easy to use.

Postman is open-source, so the cost is minimal compared to commercial platforms.

I have a partnership with ReadyAPI but I am a Postman user.

If you compare Postman and ReadyAPI, Postman is a very good starting option. However, ReadyAPI, being a commercial tool, offers additional features. If cost is not a concern, ReadyAPI is preferred. 

Nonetheless, Postman offers ample features for API testing at no cost. 

Overall, I would rate Postman as eight out of ten. I can recommend this solution to other users.