Arunkumar Anand - PeerSpot reviewer
Technology Specialist at a tech vendor with 10,001+ employees
Real User
Top 20
The environment variables are a valuable feature because i can easily switch them and see all the developments in different cycles and stages
Pros and Cons
  • "The environment variables are a valuable feature because I can easily switch them and see all the developments in different cycles and stages."
  • "One area that could be better is collection management."

What is our primary use case?

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.

What is most valuable?

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. 

What needs improvement?

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.

For how long have I used the solution?

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

Buyer's Guide
Postman
March 2024
Learn what your peers think about Postman. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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. 

How are customer service and support?

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.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup was straightforward with a little complexity.

What about the implementation team?

Implementation was done in-house only.

Which other solutions did I evaluate?

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.

What other advice do I have?

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. 

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?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
RishiBhargava - PeerSpot reviewer
Sr. Technical Director at Axeno
Real User
Top 5
A very good ecosystem, especially when dealing with a scattered multi-discipline team
Pros and Cons
  • "Good at simulating the API code from a fictitious client application to check API behavior."
  • "Version management could be simplified."

What is our primary use case?

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

What is most valuable?

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. 

What needs improvement?

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. 

For how long have I used the solution?

I've been using this solution for five months. 

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

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. 

What other advice do I have?

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. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Postman
March 2024
Learn what your peers think about Postman. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
Product Lead at a healthcare company with 10,001+ employees
Real User
Lightweight, flexible, and easy to use and learn
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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.  

How has it helped my organization?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I've been using Postman for almost four years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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

Which solution did I use previously and why did I switch?

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. 

How was the initial setup?

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.

What about the implementation team?

It was done in-house.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
MustafaKocaadam - PeerSpot reviewer
QA Engineer at Techno Study
Real User
Top 10
A user-friendly that helps create some complex test suites with some simple Java codes
Pros and Cons
  • "The most valuable features of the solution are that it is easy to use and user-friendly."
  • "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."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Postman for half a year.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

I rate the technical support a six out of ten.

How would you rate customer service and support?

Neutral

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Senior Consultant at a consultancy with 10,001+ employees
Real User
Simple to use and projects are easily stored; somewhat complex, UI needs simplification
Pros and Cons
  • "Simple to use and you can easily store your projects."
  • "The solution is quite complex partly because the UI needs simplification."

What is our primary use case?

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. 

How has it helped my organization?

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.

What is most valuable?

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. 

What needs improvement?

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. 

For how long have I used the solution?

I've been using this solution for six months. 

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

We use the Postman community if we have any problems. 

How was the initial setup?

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. 

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.  

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Ferran T. - PeerSpot reviewer
Executive Director at Sosteca
Real User
Top 10
A simple and easy-to-use solution for API with easy maintenance
Pros and Cons
  • "The tool is simple and easy."
  • "Integration should be improved with our continuation system because we use Azure DevOps separately."

What is our primary use case?

We use this solution for every API development.

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

The solution is easy to scale till now.

We are using the solution for five people.

How are customer service and support?

We get help from videos and the web.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Muzammil Riaz - PeerSpot reviewer
Senior Test Engineer at a outsourcing company with 201-500 employees
Real User
Top 5Leaderboard
A stable, scalable solution with a user-friendly interface
Pros and Cons
  • "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."

What is our primary use case?

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

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have been using the solution for three years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

The solution is scalable.

How are customer service and support?

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

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is straightforward. 

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

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?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Associate Test Engineer at OSI Consulting, Inc.
Real User
Top 5Leaderboard
An ideal solution for single-user API testing that includes good visibility of PDF reports
Pros and Cons
  • "The solution provides visibility for PDF reports without needing to install plugins."
  • "The solution has some user interface difficulties when conducting environment collections."

What is our primary use case?

Our company uses the solution for single user regression testing of APIs. For each of our releases, we run a regression report that includes APIs contained in that release. 

We create structure suites by importing API information from swagger links, writing test scripts for APIs, and validating the values in our responses. This process can take some time but completed ignition suites can be reused. 

What is most valuable?

The solution provides visibility for PDF reports without needing to install plugins. 

Other solutions like JMeter require plugins which is not ideal. 

What needs improvement?

The solution has some user interface difficulties when conducting environment collections. 

It is important to be careful when storing information to ensure files are secure and not lost. Storing information can be a bit hectic. 

For how long have I used the solution?

I have been using the solution for one year. 

What do I think about the stability of the solution?

The solution is stable and provides a good user experience. 

What do I think about the scalability of the solution?

The solution is scalable. 

How was the initial setup?

The initial setup is quite easy because installation automatically sets up collections. 

What about the implementation team?

Our company implemented the solution which requires manually writing the process. 

What's my experience with pricing, setup cost, and licensing?

The solution has a licensing fee which might be prohibitive.

There are open source options that are cost effective and offer API testing such as JMeter. 

If JMeter is too restrictive based on your project, then I suggest moving to the solution. 

Which other solutions did I evaluate?

We use the solution for attrition and single user testing of APIs. 

We use JMeter for automated API testing and load testing for multiple users. 

What other advice do I have?

The solution requires an awareness of APIs, JSON format, XML format, schema, and Java scripting. 

I rate the solution a nine out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Postman Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2024
Buyer's Guide
Download our free Postman Report and get advice and tips from experienced pros sharing their opinions.