Best for rest API
What do you like best about the product?
The documentation style for the REST API is where we can save multiple responses and proper status codes. Number of features, ease of integration, ease of use.
What do you dislike about the product?
Older version was easy to manage but with new version very complex to find from where we can publish the api links.
What problems is the product solving and how is that benefiting you?
RESTful API documentation and mantanence.
Savier for software engineers
What do you like best about the product?
It's very easy to use user friendly help software engineer to know about APIs testing very helpful we can save the domain also for testing very helpful
What do you dislike about the product?
Nothing it's very easy to use and helpful
What problems is the product solving and how is that benefiting you?
Many api problems and ali testing it's very beneficial for engineers to test APIs through it and it makes work easy
Best for testing and creating APIs
What do you like best about the product?
Both the desktop application and the web version are easy to use. Ease of integration and ease of testing your own and third-party APIs, User interface is simple and intuitive. collaboration features are very helpful for teamwork.
What do you dislike about the product?
I find it unsafe when storing sensitive data. Postman becomes slow when performing high volume tests. For advanced features we have to pay license fees.
What problems is the product solving and how is that benefiting you?
Postman solves the problems of developers who need an easy to use tool when creating APIs and when testing with APIs. Postman solves the problems of work teams using collaboration features.
Best tool for checking the endpoint url or api call request to show the response
What do you like best about the product?
The UI part is amazing and also it provides the quick resolution for any error while sending request for api
What do you dislike about the product?
I don't have much dislike for postman , it's good and easy to use tool for beginners also
What problems is the product solving and how is that benefiting you?
It basically helps in checking the api request endpoint url tk fetch the response so that we can conveniently in apex class or java code without any issue
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.
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.
