Postman Reviews

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 use this solution for manual API testing, which we call penetration testing. Postman provides a user friendly interface that can be used by non-technical team members. 

It is easy and simple to use and install. It is compatible with Linux, Mac or Windows. Postman is a great solution and resource for those who are new to technical platforms in terms of API development and testing. Postman is an open source solution and so is an affordable resource for those wanting to learn. 

I would like to have a code snippet where I can write a code and for the responses of the endpoints to be validated using my custom business conditions. In certain scenarios, we want to have custom business scenarios and not generic ones. 

We would like to have a code interpreter in Postman and also for automation to be less complex. My team want various complex automations using APIs depending upon their complex business conditions but automation using Postman is limited.

The UI of Postman could be enhanced by adding a proper panel or code. 

I have been using this solution for five years. 

This is a stable solution but user rights can be complicated and cause disruptions. 

This is a scalable solution but scaling it can be complex. 

For support, we use the open communities and documentation provided.

The initial setup is very straightforward.

This is an open source solution.

I have previously worked in the airline industry and used ReadyAPI. This is a licensed product and was used to ensure GDPR requirements and data privacy policy requirements were met. This solution costs approximately 800 Euros. Postman, on the other hand, is free as it is an open source solution. 

Running test cases using Postman is not as easy as with ReadyAPI. 

I would rate this solution a seven out of ten.

We use Postman for API testing only. We test it locally and share contracts with other teams. We also enter environmental variables to test different environments.

The environment variables are a valuable feature because I can easily switch them and see all the developments in different cycles and stages. I can deploy it locally and QA everything in different environments. 

I can copy the cURL request from the browser when browsing any website, copy the network tab from the browser and import it to Postman instead of rewriting everything, which comes in handy when debugging. If I'm working with a complete browser-deployed app, I can open a specific URL and see the recursion. 

One area that could be better is collection management. I duplicate collections and end up with lots of them. Maybe I'm not using it properly. But a better way to manage and save collections would be an improvement.

Another improvement would be the ability to clone a collection (or even have cloning as the default) to avoid time-consuming production issues.

We've been using the product for three or four years.

Postman is pretty reliable. I haven't encountered many stability problems.

Only the client can test it. I do not see much use for scalability. For example, if I have all these collections, I can use some script and automate the flow. Other than that, we don't see many use cases for Postman itself. 

So far, we've had no issues with Postman that required support because we just make an HTTP call and show the results. So we can get all the support we might need from sites like Stack Overflow.

Positive

The initial setup was straightforward with a little complexity.

Implementation was done in-house only.

We tried some different solutions after using Postman, not before. But Postman has better graphical support than its peers. At that time, I tried using a product whose name I can't remember ("Fire" something, I think) and others but had problems with them, so stopped.

I would rate this solution eight out of 10.

Regarding our relationship with the vendor, as far as I'm aware, the company has no business relationship with Postman. We use the product because it's the world's most commonly used open-source tool for repair testing.  

Regarding the number of staff required for the daily maintenance of the solution, we only make changes when the Postman tool or the contract changes. API contracts are modified daily. Most staff members continually modify or update these collections. Our developers use Postman at least once a day when developing.

My advice for others looking to implement Postman in their companies is that there is no reason to implement Postman. Plenty of other solutions are available, but most people are familiar with Postman because it appears in several YouTube tutorials. 

We use Postman for testing and documenting APIs. I'm the technical director. 

Postman helps me recreate our client environment so I can send different parameters and get that authentication information. Postman helps me simulate the API code from a fictitious client application so that I can check the API behavior. It gives you a good ecosystem, especially when you have a multi-discipline team that is scattered. It's a great product, easy to use, and people like it. 

I think they could make version management easier and release it when it comes to container-based or Docker-based architecture. The solution is not really integrated in the sense that there's no distinction regarding single-tenant or multi-tenant use, or whether there are different versions for different container applications. Different versions of APIs might be required but there's currently no distinction between them. 

I think Postman should now focus on integrating into the whole DevOps and CI/CD pipeline and publish more white papers and articles to make it easier for somebody doing the DevOps and integrating Postman into the different development scenarios. 

I've been using this solution for five months. 

The solution is very stable. We were able to test it and simulate different client experiences. 

The solution is scalable, we use it for millions of customers' API codes. 

We haven't needed to contact technical support because the documentation is very straightforward and very helpful. It has good community support.

The initial setup was straightforward and was carried out in-house.

We've been using the open-source version until now, but I think within the next six months we might move to the enterprise solution. Licensing costs are reasonable, in the mid-range. There are more expensive solutions. 

Postman has taken the development community by storm. A lot of developers are using Postman for different things. Not everybody understands the end-to-end capability of Postman yet; one person might think it's only for testing, another that you can build applications, and somebody else might use it for documentation. Different developers look at it from different perspectives, and it has huge versatility. 

I rate this solution nine out of 10. 

I use Postman as a testing tool. I used Postman for one of the education-based applications named Compass. I can use Postman effectively.

The most valuable features of the solution are that it is easy to use and user-friendly. I can use Postman with simple Java codes, along with some secret codes. With Postman, I can create some complex test suites. With Postman, I can get some statistical reports, making its use so much fun for me.

From an improvement perspective, Postman can help users create a stronger feedback loop along with quicker and more responsive support resources.

I live in Turkey, so for me, the value of dollar currency is high. Postman can change its pricing policy and decrease the prices for Turkey.

I have been using Postman for half a year.

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

Scalability-wise, I rate the solution an eight out of ten.

I worked with Postman all by myself in my IT group, but there is another group in my company with three or four members who use Postman presently.

I may use Postman even more for another project if needed in the future.

I rate the technical support a six out of ten.

Neutral

I use Selenium as a web development tool and testing tool. I also use Azure Database for MySQL.

I rate the product's initial setup phase a ten on a scale of one to ten, where one is a difficult setup phase, and ten is a very easy setup.

The product's installation phase is very easy.

The solution is not deployed on a cloud model.

The solution can be deployed in six or seven weeks.

The product's deployment process revolves around controlling back-end activities while also keeping control over the part of writing output codes, after which I could classify some tests on it. The deployment process of the product was easy.

I was alone in the project for deployment, as it was not so complicated for one person.

I could take care of the deployment of the product by myself without any other person or support.

I rate the product's price a nine or ten on a scale of one to ten, where one is cheap, and ten is very expensive. Postman is an expensive tool for Turkey.

I researched other applications in the market and found that Postman is better than the others.

I can recommend Postman to others.

Considering the shortcomings that stem from Postman's pricing model and issues with support, I rate the overall tool an eight out of ten.

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.

We use this solution for every API development.

We are exploring code generation and how it works. We also like the test functionalities and snippets that we can use directly.  

Moreover, the tool is simple and easy.

Integration should be improved with our continuation system because we use Azure DevOps separately.

I have been using Postman for around two years. Initially, we used it only once, and now we use it more.

The solution is stable.

The solution is easy to scale till now.

We are using the solution for five people.

We get help from videos and the web.

Positive

We have also worked with SoapUI, but we like Postman because it has automation.

Postman is a more compact tool, and it has many functionalities. In the first stage that we used, Postman, we only tested how it works. Now we are using more functionalities. With SoapUI, it's because some customers have used it to define the APIs, and then we have to interact with this environment.

But we use Postman, and we prefer Postman. Although, there are some tools from SoapUI that are good. For example, the API design, checking, and definition. If Postman has anything similar, you can check the definition of the API, and it proposes you an improvement and so on, but in the development phase, we used Postman, and we like Postman.

The solution’s initial setup is easy. The maintenance is easy as well because we are not doing all the possible accents and because we are not doing anything to maintain.

The solution is deployed on the public cloud and on-premises in our organization. But I use it more in the cloud.

The solution’s pricing is realistic according to our usage level. As we grow and require additional functionality beyond what we currently use, there is a higher cost while upgrading the developer plan. We want to explore features like automatic code generation and other functionalities.

We are paying only for the license for now, and it comes with a monthly subscription.

Postman is one of the most widely used tools in the market. When you use it, it is practical and useful. You need to check whether it suits your team, project type, and work to take profit from the way Postman works. From the beginning, it is one of the three main tools you must explore if you regularly deal with APIs.

However, I am still exploring all the tools, and I don't know if I can maintain it or not. When I know all the different technologies better, I will be able to say.
Overall, I would rate the solution an eight or nine out of ten.