Postman Reviews

I use Postman to test REST APIs. I work with Node.js and create or modify multiple endpoints, and I use Postman to verify if the endpoints work. Additionally, I use Postman to test other endpoints, like public endpoints.

In Postman, we have collections that contain multiple endpoints that I can test. I can use multiple environments, which allows me to create environment variables for each endpoint.

Something that could be better is the inclusion of another type of test, for example, end-to-end tests. It would be beneficial to expand functionality with additional testing options.

I have been working with Postman for five years.

Postman is pretty stable. I have not experienced any issues or downtimes.

The initial setup for Postman is very simple.

The price is low, making it a reasonable price for the product.

Postman is currently the leader.

I recommend Postman for all business types.

I'd rate the solution nine out of ten.

I have been using Postman for three years. I am not using the tool's latest version, Postman v10.11.1, but I am not sure. I think I am using the older version, Postman v9. I am just a customer of the tool.

The solution's most valuable feature is the data flow. In Postman, the API additions are very easy to process. I think there is no other tool that makes things very easy like Postman. Postman is user-friendly. We can understand all three types of calls very easily in a single frame only. Everything is available in just a click of it. I think the user interface is really good for the application because there are a lot of tools available that let you handle API integration with Postman.

I am not sure where the product can be improved since I have used only one particular application to work with API and not any other applications. I currently do not have anything, you know, for Postman to be improved upon because I am very satisfied with whatever they have right now.

The product lacks a good console. In the future, I would want the tool to have a better console. I feel that the console can be a better option that can be added to the solution. When we use the API calls, the results are available in the console. The tool's console can be a bit better and more interactive. It is very weak currently, and I feel that it could have a better interactive console.

I have been using Postman for three years. I am not using the tool's latest version, Postman v10.11.1, but I am not sure. I think I am using the older version, Postman v9. I am just a customer of the tool.

It is a very stable solution. For the past three years, I have not faced any major problems related to Postman.

A lot of people in my team use the product. I would say that over 100 people are using the solution.

I have not had any interactions with the product's support team since I have not faced issues with this solution.

The product's deployment phase is easy.

In terms of the deployment model, I would say that I use it locally in my system.

Postman is an open-source product. It is free to download from Google.

Postman is really great if you are working with APIs. It is very easy to understand, and I think that a lot of tutorials are already available on YouTube. I don't think you have to break your head to understand it separately. The tool's user interface is very friendly, and it is very easy to use.

I have not used to the monitoring and automation features of the product.

The integration capabilities of Postman help streamline development processes, and it is one of its main highlights. Presently, I think Postman lets you interact with other tools and web applications. It makes the development phase easy.

Postman is a really good tool for API integration. I don't see the tool lacking any features because Postman helps us with all the data governance parts.

It may not exactly be easy for beginners to start learning how to use Postman for the first time. If he or she has experience working with API, then it might be easy to use Postman. For people who have no experience with APIs, it might be a bit difficult in the beginning to use Postman, but after a certain point in time, it will be easy.

I rate the tool a nine out of ten.

We use the solution for rest API testing purposes.

The solution's most valuable feature is code-based API testing. The technicians have complete control over the business logic code in the test tool.

Occasionally, a few variables get errors due to concurrent instances running simultaneously. They should improve this particular area. Also, providing more specific documentation on configuration would be helpful.

We have been using the solution for three years.

It is a stable solution. I rate its stability as a ten.

The solution is scalable.

I visit online forums for technical support in case of any errors.

We used UFT earlier.

The solution's initial setup process is straightforward. You must know about the required environment and security credentials for implementation. It needs two test automation engineers and one business analyst to execute and takes a few hours to complete.

I rate the process as an eight.

The solution's price is reasonable. We pay around £70 a month for it. I rate its pricing as one.

I advise others to gain knowledge of JavaScript. It will help them use the solution's test automation framework with ease.

I rate the solution as a nine.

We usually do our API testing and the endpoint testing on Postman. That's our primary purpose for using Postman. Sometimes, we also use it for load testing, but most of the time, we use a different tool for that. 

I don't know the exact version that we are using currently, but most of the time, it is the recent one because our enterprise keeps on updating the software. In terms of deployment, it is a client tool.  

It definitely increases the quality of our deliveries because we are able to test our APIs before moving them to production.

We use it for REST API testing. Feature-wise, it is pretty lightweight. It is pretty fast, and we don't have to do a lot of things. We can just simply go and post our endpoint, and it gives different kinds of authorizations. We usually use authentication 2.0, which is the most common industry practice. So, it has the support for authorization through 2.0.

It gives the flexibility to add headers, and it also gives the flexibility to build your payload at run time. If you want to do automation testing, you can just build your payloads at run time by supplying some parameters as variables.

It gives us good flexibility, and it is pretty easy to use. Even entry-level developers can quickly test their APIs. They don't have to rely on the QA testers or the specific QA resources to look at various use cases.

The request encryption could be one thing on which they can work a little bit. If we don't want to expose our production data but we still want to test our APIs on the production data, there should be a way to do that. It is not only with Postman. I think no tool in the market is doing that right now.

It would be helpful if better tutorials or recommendations are available while we are using the product. Otherwise, we have to go out and search for specific things. It would be good if they build something in the tool itself that provides recommendations based on the task that we are doing. If we are testing APIs, the tool should come up with some kind of information.

Scalability-wise, it can be improved a little bit. They can include more options to do the performance testing or rate testing so that we can query or push a lot of requests to our APIs.

There could be some kind of graphical interface for performance testing. It would be really helpful if it can give some data to visualize how the performance testing is going in real-time, but there are specific tools for that. Postman might not be meant for that, but they can think on those lines.

I've been using Postman for almost four years.

I have never seen it crashing, which is a good thing for a tool like this. Sometimes, it hangs, but that's more of an operating system problem. It is not related to the application.

If we want to scale our operations, we definitely try to test our APIs with many requests at the same time from the real scenario perspective. For performance testing, we use a separate tool. NeoLoad is the tool that we use for our API performance testing. Scalability-wise, Postman can be improved a little bit. They can include more options to do performance testing or rate testing so that we can query or push a lot of requests to our APIs.

We are a very big organization. We probably have around 2,000 developers. It is being used extensively. It is good for API testing.

I haven't talked to anyone from their support team.

I started with SoapUI. It is similar in terms of capabilities and functions. There was no specific reason for switching to Postman. I saw people using Postman more, so I started using it. 

Postman is more popular than SoapUI. When we are doing testing of the APIs that we want to consume, people usually say that this is a Postman request, and you can try it out. More people use Postman than SoapUI, and that was the reason I started using Postman. 

It is pretty straightforward. They also have a WebUI. If you don't want to use it on your device, you can go and use WebUI.

It was done in-house.

It is doing what it is supposed to do. It is a pretty nice tool, and there should not be any problem in using it. It is definitely better than other alternatives.

Based on my experience so far, it is a flawless product. I don't see any bugs or any kind of technical issues in using it. It is pretty easy to use and easy to learn. If you want to start with API testing, you can go ahead and start with Postman. It is the easiest option available in the market.

I would rate it a nine out of 10.

The primary use case for the solution is to test the response accuracy of services that we hit without the UI.

The most valuable feature is that JavaScript can be included as tests. That makes it easier to build an end-to-end API suite and it can be automated.

Integration of the solution towards Bitbucket, BitHub, and CI pipelines is difficult.

I have been using the solution for two years.

The solution is stable.

If used as a stand-alone solution it is easily scalable.

The initial setup is straightforward. You only need to download the solution from the internet and run it. The most complex part of the setup is setting up a proxy if it is required.

I implemented the solution in-house.

Unlike APIs, the solution does not require a license.

I rate the solution seven out of ten.

As a standalone option, it's a fantastic tool, but it's very hard for us to collaborate using the solution.

Our development people use the solution for testing.

The solution is a good tool to try out new APIs that the team is building or any existing APIs. It is relatively easier to build out scripts and automate certain flows. The solution as a standalone tool is beneficial in creating utility scripts. 

I primarily use Postman to manually test our APIs with HTTP and REST calls. I don't use the more advanced features, such as script automation.

Postman lets you create, manage, and validate a suite of tests. It has several features to help you organize your test suite. You can also automate stuff with a lot of validations and assertions. Postman supports GraphQL, and you can do various kinds of calls. 

The reporting could be better. It should give you a detailed PDF report after you run a test.

I have used Postman for about four or five years.

Postman is stable. 

Postman is scalable.

Setting up Postman is straightforward and takes about an hour. 

We use the free version. They introduced a new licensing model where your company must subscribe to their services if you're using it for business purposes. However, I think they charge too much if you're only using the basic features. It limits what your organization can do if you're not a paying customer.  

I rate Postman a seven out of 10. I think seven is a decent score because it's a solid tool that installs quickly and has tons of features. Postman supports multiple formats of REST and GraphQL. You can automate your test suite and run regressions. I don't think Postman lets you connect to a lot of databases, which could be a limitation, but I recommend it. 

We mostly use a REST API for testing related to third-party applications, integrating services with third parties responsible for food delivery. Use cases include onboarding for when a new store opens, uploading the menu on the third-party app. and an API for customers to order from a menu. We also use Postman for payments, whether debit or credit card. It covers all the validation points, including whether a card is fake, stolen, invalid or blocked. We are customers of Postman and I'm a senior consultant. 

We observed that in contrast to SoapUI Pro where you're only able to save your project, Postman allows you to also save your responses so that if something isn't working you can go to your saved results and verify the responses.

The solution is simple to use and you can easily store your projects. We mainly use Postman for our manual validation, but you can also schedule the automated validation. It offers multiple scenarios for a single API that you can run whenever needed. It offers a validation kind of functionality and the execution report of scripts. How many passed and how many failed. There's no manual intervention required, you click on the run button and that's it. The dashboards are good and the solution is user-friendly. The solution gives you the capability to run your use cases without manual intervention. 

The solution is quite complex and not so easy to understand at first glance. Part of the problem is the UI which needs simplification. There are many features available but they need to structure things more so that they're not scattered on the screen which complicates things. Each time you run the solution, you have to manually provide a username and password because those details are not automatic. That's a pain point for us. It also lacks a feature that will integrate with your database. I think this is a drawback of most applications whether it's Postman or SoapUI Pro. If you want to automate something when you're using the huge APIs, everything needs to be automated using dynamic data and that takes additional time. 

I've been using this solution for six months. 

We're a large organization and I imagine there are around 1,000 people using this solution. For maintenance and upgrades, our organization has the repository to maintain all software. Though it's freeware, you cannot install it directly and we have a separate team responsible for maintaining all the software.

We use the Postman community if we have any problems. 

The initial setup is straightforward. You just have to install the application, there is no complexity in that. Deployment takes a few minutes and then you build up your URI and start using it. In total, it takes less than half an hour. 

We don't pay for any license, the solution is freeware. There are some additional features that we do need to purchase.

It's important to figure out your requirements and if you need something special, then you will have to compare the different applications and figure out which gives you better results. 

I rate the solution seven out of 10.  

I use Postman from time to time to test real-time API connections.

When I receive documentation regarding API services, I use Postman to verify that the explanation in the documentation I received is working as described. In general, the tool is good for testing purposes.

The most valuable features of the solution are drafting requests, pushing the standard, and receiving responses. The tool's basic operational stuff is valuable.

The automation testing capability is something that I haven't used. In the past, I have used SoapUI to automate tasks, but I haven't tried it in Postman. I was not even aware that it was possible to automate tasks in Postman.

Some features related to the automation of tasks need to be added to the solution. The tool may already have some automated testing features, but I haven't discovered Postman's full operational status. When I need the tool's automated testing features, I will certainly have a look at the documentation.

I have been using Postman for four years. I am a user of the tool.

Stability-wise, I rate the solution a nine out of ten.

The stability of the product has been better since last month.

I have experience with SoapUI. The environment where I work for the moment is more Postman-oriented. In the past, some government departments in Belgium were using SoapUI. Postman is similar to SoapUI. The features in SoapUI, for instance, the automated testing features, are things that I don't need at the moment. Postman performs how I like it.

The product is easy to implement. You need some knowledge to implement the product. As I was more or less familiar with SoapUI, I could very easily pick up the way Postman works.

I use the tool's free version.

The product is not used for collaboration but for testing purposes in my company. In short, I use the product, and it is not used for exchanging or exporting data. I use the product at a very personal level, considering its API-related capabilities.

The tool performs well enough to meet my expectations.

I rate the tool an eight to nine out of ten.