I used Postman for testing and automatic tests. I use it as a beta tester for API interface with the main programs.
Postman Enterprise
PostmanExternal reviews
External reviews are not included in the AWS star rating for the product.
Great for easy API testing
Collaboration and scripting features streamline test processes and improve API management
What is our primary use case?
What is most valuable?
The scripting capabilities in Postman are excellent. You can implement scripts before and after, making it easy to create interfaces. We have multiple versions available. I can mark which version to use when sending calls for authorization and tokens. Depending on the version and client, I can activate everything with one button through scripting.
Postman's collaboration tools, such as version control and team workspaces, are particularly useful when working with teams of three to four people. Some team members create scripts, and updates can be made through the cloud platform.
The collaboration features are valuable for maintaining and updating projects.
What needs improvement?
There are some limitations regarding large result sets in Postman. When dealing with several hundred records, accessing all the information can be challenging. However, these limitations are less restrictive compared to Swagger, which has more severe limitations when used with web navigation.
For how long have I used the solution?
The company purchases Postman licenses for multiple users.
What was my experience with deployment of the solution?
Previously, we didn't use Postman but had API functionality through IIS. We implemented XML replies for SQL Server.
Postman's integration with CI/CD pipelines has impacted the continuity and deployment of our APIs. We use Postman to integrate with JIRA, collecting tasks through JIRA's commercial API. We are implementing experimental applications to read and collect information from JIRA.
Postman performs excellently for these integrations. The main challenge lies in understanding external documentation to access the API correctly, but once configured, Postman excels at collecting information.
What do I think about the stability of the solution?
Postman is an extremely stable program without any significant issues.
How are customer service and support?
I primarily use documentation and haven't tried support or extended support when considering Postman's adaptability for both REST and SOAP APIs.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I use SwaggerHub at the client side to test and ensure API functionality. I only implement Postman in the client environment under exceptional circumstances.
How was the initial setup?
Postman is easy to set up, though company policy restricts implementing solutions on local machines.
What other advice do I have?
I utilize this product with AWS for REST applications. The automated testing features are available but limited by license restrictions. I primarily run repositories and work with JSON format. We have standardized all old XML versions to make implementation and future development easier.
I work as a programmer analyst for research and development. My email is marcel.cote@acceo.com.
On a scale of 1-10, I rate Postman a 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Postman experience
Reliable and user friendly API testing platform
In postman we can share collection and also using mock server.
Also have newman for CI/CD integration.
Postbot ai also have good feature
limitation -limited version control
2.Restricted automation capabilities
Its speed up my testing cycle, increase testing efficiency , improver team communication
Recently I am using AI agent postman MCP feature in our project
The fast tool to send requests and receive responses, not so fast but for me the more complete tool.
APIs testing- Postman way to go
Api test and automation is a few secongs task with postman
Cost efficiency and user satisfaction improve with diverse tool integration
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
Personally, I have been using Postman for seven or eight years plus.
How are customer service and support?
The technical support for Postman is all good.
How would you rate customer service and support?
Positive
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Postman enables seamless workflow with efficient data transmission capabilities
What is our primary use case?
What is most valuable?
The features of Postman that I use most are POST and PUT functionalities for sending the data.
The service logs can be useful in our work. The data you are sending and fetching from that endpoint is very clean and understandable. Anyone can understand it.
What needs improvement?
As for room for improvement in Postman, I haven't observed anything that needs improvement as of now. What I have observed has been good.
Sometimes there might be issues, though not major ones, but the documentation helps with these.
For how long have I used the solution?
I am a user of the Postman application.
What do I think about the stability of the solution?
For stability, I haven't faced any issues with bugs or breaking down. Once it goes to real-time production, it won't get affected. During the development phase, you will face issues, but once it goes to production, you won't face such issues. That is a good thing.
Regarding stability, I would rate it nine out of ten.
What do I think about the scalability of the solution?
Regarding scalability, while I cannot fully judge that particular concept, it has been good as I haven't faced any challenges.
How are customer service and support?
Regarding their support, I don't have any judgment I can make on that.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup for Postman is easy and doesn't require much effort.
What other advice do I have?
I am using Postman for my current development work.
Regarding whether Postman is an easy tool to use, I wouldn't say specific experience and knowledge are necessary, but regarding real-time configuration, users should follow the best practices. For using this tool, there isn't much needed experience in other technologies or coding. Technical backgrounds aren't needed; users just need to follow best practices.
I can describe how Postman's automation feature works when getting data from any database through an API. The automation happens in the background, though you can't track how much time it takes.
Overall, I would give Postman a nine, as it was great and good. Though there are sometimes issues, I would recommend it.
Postman review
2. Comprehensive features
3.Collaboration.
4. Automation
5. Documentation
6. Community and Support
2. Limited customization.
3. Complexity for beginners.
Automating test cases.
Environment and management.
Collaboration and sharing.
Mock responses.
Integration with other tools.