Postman Reviews

I'm using Postman for manual testing of REST APIs. There are some built-in collections done by some of my teammates, so I use those.

The solution is deployed on a public cloud.

I have used some parameterization from a global variable, so that was working fine for me. It's easy to see different versions of responses. There's also a possibility for automation.

We cannot do database connections from Postman directly, and we don't have a way to do that. If they could implement auto-validations and assertions from SoapUI, that would be a very good feature.

We don't have a provision to go and connect to the database from Postman. That's one drawback. If you want to automate in Postman, there is a major drawback. Being a tester, you always want to cross-verify your data with the database. If the database is not connected, then part of your testing becomes manual.

I have used this solution for about seven years.

It's stable. Sometimes it has gone off, and I have had to rebuild the collections again. I've had to switch the logins sometimes. It has crashed twice, and I lost my suites and had to build it again.

Initial setup is easy. Sometimes we get the proxy errors, but when we go to the settings and disable the proxy things, it's pretty simple. Comparatively, SoapUI is easier for me.

Maybe some people who don't have a licensed version of Postman or ReadyAPI might feel that it's easier to automate with Postman, but I'm not sure about that because I haven't done it.

I would rate this solution as four out of ten.

If you don't have SoapUI or if you don't know about SoapUI, then of course you can use it. If you want to explore Postman, it's a free tool.

I am currently using Postman when working with different web applications. I use it particularly when working on APIs and endpoints, especially in testing REST APIs that I've built with Django REST framework in Python.

Using Postman has allowed me to efficiently conduct many tests on REST APIs. It has facilitated my ability to manage different data, handle various protocols, and process numerous customer requirements across various projects.

I mainly use Postman to conduct extensive testing on REST APIs, particularly those built with Python and the Django REST framework. Postman is very user-friendly and accessible even for those with minimal experience. In my role, I appreciate Postman for its parts in managing and testing APIs. 

Postman also simplifies working with endpoints by allowing different methods to send information, making the debugging process more manageable. It also offers robust compatibility with various environments, making it a vital tool in my operations. 

Additionally, the desktop version's features like cookie management, environment compatibility, security settings, proxy integration, and data synchronization add significant value.

One of the primary challenges with Postman is handling authentication issues, especially relating to tokens and passwords. The management of endpoints' headers sometimes conflicts with APIs that require information in the body, leading to difficulties. 

Furthermore, connection and timeout issues, like when testing APIs that require authentication, can occur.

I have been using Postman for eight years, utilizing it mainly for testing and working with different technological protocols.

The tool is generally stable, though there are occasional challenges, such as authentication issues causing errors or issues with connection stability.

The support from Postman has been satisfactory. I appreciate the ease of using Postman, especially its desktop version, due to the features it offers such as cookie management and environment synchronization.

Positive

The initial setup of Postman is relatively simple for experienced users, though it may present a learning curve for others.

I help in training others on using Postman, demonstrating its utility in managing APIs, diagnosing issues, and running tests.

Postman's pricing model includes a basic free version, which is favorable given the Professional enterprise options offered.

I rate Postman as a ten out of ten. I recommend Postman to others for its ease of use and comprehensive support for API testing and development.

I use Postman in my company for API testing.

Postman has a lot of additional features like the ones offered by SwaggerHub. Postman is a bit more complicated compared to SwaggerHub since you have to insert bearer tokens all the time and set everything from the start. I mainly use SwaggerHub as it is easy for me. I always get back to SwaggerHub from Postman.

Postman is a bit more of a complex tool, making it an area where improvements can be made.

Postman is good the way it is right now, so there's nothing to change in it.

I have been using Postman for a year. My company is a customer of the product.

It is a stable solution.

In my company, over 50 employees use Postman.

Given an opportunity, I would prefer to use Postman over SwaggerHub. People mostly prefer to use SwaggerHub over Postman.

The product's initial setup phase was easy and not difficult.

The solution is deployed on an on-premises model.

I would recommend others to use Postman. I am a QA, and I should know about different products before I use Postman. In short, a person should know to use it.

I rate the overall tool a nine out of ten.

Postman is a scripting tool.

I started using the solution when we did an SDN-based network implementation from Cisco. I got introduced to a particular scripting tool where I could actually put down everything in an Excel sheet. And if I want to configure, for example, ten ports, then I can actually do the configuration of everything in an Excel sheet. I can pass my credentials in Postman, and I can import the SQL script, and based on whether it's an infrastructure script or a configuration script, I can actually save it in Postman.

I'm using Postman to only push the scripts into the ACI, and that is a very limited use of Postman that we do right now.

I'm sure it might have other usages. That said, we have not explored other features beyond that at this point in time.

The initial setup is easy.

The solution is stable.

It is very user-friendly and has a nice UI.

My limited use of Postman has been to get the output of scripting in Postman or get the output from APIs and then open it in Postman or post the script. We don't use it much beyond that and therefore haven't really explored the features. It's hard to say what is lacking.

Postman does not have a check-in balance. Essentially what I mean by that is if there is something that is already configured on a particular device, it just overrides it without checking whether you really want to override it or not. Even if it is by mistake, if there is a dialogue box that is available before it overrides, it's just a much nicer feature to be notified if you're doing something by mistake.

I've been using the solution for a while. 

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. We haven't faced any issues.

I know that our team, which is three people, uses the solution. I'm not sure who else does in the company. We're all engineers. 

We have received all of the support we required. Postman has a very good team.

We use quite a few products from an infrastructure point of view. We use SolarWinds, both for server and infrastructure capacity, and we use a change management and a problem management tool. From a bandwidth monitoring perspective, we use a network analyzer; we use Splunk heavily. We do a lot of scripting tools using Postman and Python.

I'm more into Python since Python gives us many more API interjections and compatibility with a lot of other APIs. We started using Postman, and then we immediately moved to Python-based scripting.

The functionality that Python gives you concerning the available APIs and then the ability to put that in the Excel sheet is much better than Postman.

The solution is very easy to set up. There were no issues. 

I don't deal with the licensing aspect of the product. 

We looked into other solutions. However, Cisco actually recommended Postman, so we went with this product. 

I'm an end-user.

I'm not sure which version of the solution I'm using. 

New users need to watch a few videos and understand the solution pretty well. If you are using Postman for the first time, never use the administrative credentials. It is very easy for you if you're using the administrative credentials to pass through the Postman's scripts. It is possible that you might override the configuration unknowingly. If that happens, that can actually bring down a good amount of your configuration or an earlier configuration. It's best to actually get the solution into a development environment before you actually do anything on production.

I'd rate the solution seven out of ten. It's a good, very user-friendly scripting tool. Anybody can learn it and start using it. However, new users do need a little bit of knowledge and must be willing to learn as they go.

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.  

We use Postman for API testing, and I am also using it for training purposes.

I have found that our time is significantly saved in terms of debugging and writing down the code manually as Postman allows us to add the code with the help of test and assertions, eliminating the need to write code ourselves.

The user interface is very easy to learn and use, and it is a lightweight application. It's also an open-source tool for API testing. One of the best features is that you really don't need to be an expert in any programming language because Postman can generate the codes automatically for you.

Postman needs to improve its support for a lot of integrations. Additionally, browser add-ins or extensions would be helpful.

I have been using Postman for quite a while, perhaps for the past seven or eight years.

The initial setup is very easy and simple.

Being an open-source tool, it's a lightweight tool that I would prioritize as number one.

I would prefer Postman as my priority since it's an open-source tool, simple to install and use. You don't need to be a programming expert to use it, which presents several advantages.

I'd rate the solution 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.

The primary use case of this solution is for the API manual testing, manual verification to get the response, and for API automation.

The most valuable feature is the user interface because it provides a clear space for the URL, headers, body, prerequisites, and tests.

The solution can be improved by providing detailed error logs including the line the error took place to make it easier to correct. I would like to see functionality added for uploading specific scripts and not the entire collection.

I have been using the solution for three years.

The web app version is more stable than the desktop application.

The solution is scalable.

The support team is very responsive in resolving any issues we have.

Positive

The initial setup is straightforward. 

The solution is free for individuals, but for companies that use it across the organization, you have to pay per user. The solution is competitively priced.

I give the solution ten out of ten.

If you have a small amount of knowledge of HTTP status codes, how to make collections, and how to deal with environment variables is enough to use this solution.

We have 1000 people in our organization using the solution daily.