Optimizing workflows and reducing manual effort with versatile API features
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Postman for about a year, during my training.
What do I think about the stability of the solution?
I haven't experienced any crashes or downtimes with Postman; I find it stable.
What do I think about the scalability of the solution?
In terms of scalability, I do find it scalable.
Which solution did I use previously and why did I switch?
I haven't used any other API testing tools apart from Postman.
How was the initial setup?
The initial setup of Postman was easy for individual calls. For the flows, it required additional work.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Postman review
What do you like best about the product?
Easy of use while doing the penetration test using burp as Proxy
What do you dislike about the product?
I have used postman during my Pentest process. Never feel any dislike.
What problems is the product solving and how is that benefiting you?
Understanding Api flow
Great for easy API testing
What do you like best about the product?
Great UI and saving history of API testing.
What do you dislike about the product?
Lacks some network data features that can be useful for debugging.
What problems is the product solving and how is that benefiting you?
Quick API testing.
Collaboration and scripting features streamline test processes and improve API management
What is our primary use case?
I used Postman for testing and automatic tests. I use it as a beta tester for API interface with the main programs.
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?
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?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Postman experience
What do you like best about the product?
It is very straightforward to use and very reliable.
What do you dislike about the product?
I don't like running it from the browser and I have challenges linking it to the desktop application.
What problems is the product solving and how is that benefiting you?
Testing endpoints in development and testing out third party integrations.
Reliable and user friendly API testing platform
What do you like best about the product?
I love postman and its really helpful for api tester and its streamlined everything from sending request and validate response to chaining complex workflow
In postman we can share collection and also using mock server.
Also have newman for CI/CD integration.
Postbot ai also have good feature
What do you dislike about the product?
It sometime slow due to large collection and large payload
limitation -limited version control
2.Restricted automation capabilities
What problems is the product solving and how is that benefiting you?
Postman is solving the challenge of testing api efficiency and it help for creating large collection and run in n+1 cycle.We can easily troubleshoot the error.It eliminate the need to write custom scripts for basic testing and reduce dependency
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.
What do you like best about the product?
Same to request and responses you can create scripts to resolve the most of problens in calls, to be personalised api without an complete api. The enviroments is the best to test apis in develop and production. All this this is just a part of this complete tool. I like so much!
What do you dislike about the product?
At the moment, nothing, for me is a complete tool and im really satifated with this software.
What problems is the product solving and how is that benefiting you?
To send requests with tokens and test the if security is work property.
APIs testing- Postman way to go
What do you like best about the product?
Api testing, details like response size, time, dns time and various api support like rest, rpc, graphql etc.
What do you dislike about the product?
Slower than cli based tool, ui focus is more and automation focus is less
What problems is the product solving and how is that benefiting you?
Manual api testing made very early, organizing and sharing api collections, chaining request and workflow testing, collaboration and versioning
Api test and automation is a few secongs task with postman
What do you like best about the product?
Postman provides a rich interface and automation to diagnose apis. This make easy to use and build an api collection.
What do you dislike about the product?
Collaboration is not that much smooth as expected.
What problems is the product solving and how is that benefiting you?
With a team of fron end and backend developers, Postman plays a major role for collaboration, This provides a way to share api details from backend team to front end team. And they can play arroud with apis with postman before integration.
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?
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?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
