Try our new research platform with insights from 80,000+ expert users
Programmer Analyst at a university with 5,001-10,000 employees
Real User
Easy to manage with very good scalability
Pros and Cons
  • "No coding required."
  • "Could be more user friendly."

What is our primary use case?

My primary use case is for responses. I'm a user and work as a programmer analyst. 

What is most valuable?

This is an easy solution to manage. 

What needs improvement?

The solution can be confusing for first-time users so it could be made a little more user friendly. It's just click and proceed but still confusing if you haven't used it before. 

For how long have I used the solution?

I've been using this solution for three years. 

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

What do I think about the stability of the solution?

No problems with stability. 

What do I think about the scalability of the solution?

The scalability is good. I've used it in a company where there were around 200 people. It's generally used by an IT team.

What other advice do I have?

I would rate this solution an eight 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
Engineer 2 at a computer software company with 10,001+ employees
Real User
Top 5Leaderboard
Interactive and user friendly with a few performance hiccups
Pros and Cons
  • "The initial setup is simple."
  • "The performance needs to be improved."

What is our primary use case?

The solution is used for testing APIs, building monitors, and scheduling everyday runs to check API health.

What is most valuable?

Environment variable setup, pre-request script, tests, and monitors are most helpful.

The initial setup is simple. 

What needs improvement?

The Postman monitor will give the pass and fail status in the console. It could serve better if there is a downloadable report which gives tabular details of response time against each API and a pass/fail count (graphical representation) after the monitor runs.

The performance needs to be improved. Postman application freezes when a whole lot of APIs run under a collection.

For how long have I used the solution?

I have been using this solution for two years.

What do I think about the scalability of the solution?

Observed performance issues when used excessively. The application freezes and needs a restart. The response of the app is slow while running a collection with a lot of APIs.

How are customer service and support?

We do have some interaction with technical support. They are responsive and knowledgeable about the product.

How would you rate customer service and support?

Positive

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

I used SoapUI previously. I found Postman to be more interactive and accessible compared to SoapUI.

How was the initial setup?

It's a very straightforward solution to install. I'd rate the process five out of five in terms of ease of deployment. 

What other advice do I have?

I'd rate the solution 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.
PeerSpot user
Buyer's Guide
Postman
October 2024
Learn what your peers think about Postman. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
Software Quality Assurance Engineer at a tech services company with 51-200 employees
Real User
We can easily define the variables and it gets automatically updated
Pros and Cons
  • "The variables part is good. We can easily define the variables and we don't have to manually do a change every time, it gets automatically updated."
  • "If we have a certain build on one machine it won't work with another build even if we are using the same URL. It would give us a connection refuse. So developing environment compatibility would make it better."

What is our primary use case?

Our primary use case for Postman is API testing for our product. We haven't automated the request and response part yet, like how we used to do for automation scripts. Basically, we are just shooting the URL's and recording the response. As of now we have multiple API's and we are using the collection so that we can run it together in a single flow, like an automation execution.

Then we use the basic variables and the collection variables. We even saw that we have some additional validation through the response code and the status code, like if there is an expired date then we should be expecting 200 status codes. We are doing those kinds of things now. We have been using Postman for the API testing for two to three month.

What is most valuable?

The variables part is good. We can easily define the variables and we don't have to manually do a change every time, it gets automatically updated. Secondly, I like the validation feature which is required for our automation testing. This way we can see that our test case passed. I think we could add some more validation but we need to do more research on that. For example, how can we play with it and find the response code and the other statuses? We need to do more research on how we can validate the exact response and the code, and how we get the response messages.

We prefer Postman as it is the most usable solution. It's really accessible. We also use SoapUI for API testing. But we prefer Postman, based on the reviews, based on our research, and how easily the solutions are available if we get stuck somewhere.

What needs improvement?

In terms of what can be improved, I would expect extra features that would make our work easier.

I just saw that it's functioning is based on the machine. Meaning, if we have a certain build on one machine it won't work with another build even if we are using the same URL. It would give us a connection refuse. So developing environment compatibility would make it better. 

Other than that, I don't see anything more to improve. As it is now, I get for a return whatever I am expecting. That's why I gave it a seven or an eight. Because I'm not expecting much on that portion.

Because, we are mostly focused on that I would expect more validation points.

What do I think about the stability of the solution?

In terms of stability, it didn't crash or take time to load or anything like that. We did not face any issues with stability. It's a very old tool, so it's been used a lot. It gets daily usage.

What do I think about the scalability of the solution?

Right now, two to three people are testing it and other people are joining in. We have individually different user ID's and we don't have to go chasing anything because we are using the free version now. Because we are not using the paid version I won't be able to see the scalability yet because we are just doing the basic stuff, such as a request hit and run.

How was the initial setup?

The initial setup is very straightforward. We just have to download and do the setup. We already have the collection so we just have to share it with the teams and import the project. Furthermore, we didn't create the project and we had to do everything manually before creating the variables and still the installation was not complex.

Which other solutions did I evaluate?

We also use SoapUI.

What other advice do I have?

On a scale of one to ten I would rate it an eight.

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
QA Engineer at a tech services company with 201-500 employees
Real User
A stable solution for creating, sharing, and testing APIs
Pros and Cons
  • "The user-interface is very good."
  • "There needs to be more flexibility surrounding the testing of SOAP APIs."

What is our primary use case?

We use Postman for testing the functionality of REST APIs. 

Within my organization, there were roughly five people using this solution, however, currently, I am the only person who is developing API testing tools.

What is most valuable?

The user-interface is very good.

What needs improvement?

Actually, I received some errors regarding the testing of SOAP APIs. There's definitely some space for improving the user's experience. There needs to be more flexibility surrounding the testing of SOAP APIs. Currently, they are primarily based on JSON files — invest APIs actually.

I know that SOAP APIs are considered a little outdated but they're still in use. Unfortunately, because of this, I have to search for another solution that supports SOAP APIs, because Postman doesn't.

For how long have I used the solution?

I have been using this solution for roughly one year.

What do I think about the stability of the solution?

It's a very stable solution. Regarding the overall stability of the application and the test results that achieved — It's really a good application.

How are customer service and technical support?

We haven't really had to contact technical support. We have been able to solve nearly all issues via online forums.

How was the initial setup?

It's not exactly complex, but I wouldn't say it's straightforward either.

The deployment process was very quick; I believe it took roughly one week to get it all set up. Still, not all test cases were set up within that time period. 

What about the implementation team?

All implementation was done by our in-house team.

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

As we only had 10 APIs to test, we used the free version.

Which other solutions did I evaluate?

Recently, I compared Postman with JMeter 12 for testing the load performance of the same APIs.

What other advice do I have?

I would absolutely recommend this solution. It's one of the best solutions for testing REST APIs.

I had some great experiences using Postman, especially relating to REST APIs. Currently, I am in the process of learning about other tools suitable for API testing regarding SOAP APIs.

On a scale from one to ten, I would give Postman a rating of eight.

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
Lead Test Engineer at a tech services company with 501-1,000 employees
Real User
Helps to test APIs independently
Pros and Cons
  • "It helps me to test APIs independently. It also supports hosting."
  • "The tool needs to have a reporting feature."

What is our primary use case?

We use the solution for API testing. 

What is most valuable?

It helps me to test APIs independently. It also supports hosting. 

What needs improvement?

The tool needs to have a reporting feature. 

For how long have I used the solution?

I am using the tool for three years. 

What do I think about the scalability of the solution?

The tool's free version is scalable. My company has about 100 users for the tool.

How are customer service and support?

I never contacted the support team. Instead, I resorted to online help. 

How was the initial setup?

The product's setup is easy. 

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

This tool is open-source and free to download and use.

What other advice do I have?

I would rate the tool an eight out of ten. The product's features are simple. You will figure out to use the solution on your own. The tool is not hard to setup. 

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
PeerSpot user
Software QA Test Engineer at a tech services company with 51-200 employees
Consultant
Reliable and allows you to create and share collections with team members
Pros and Cons
  • "What is most valuable for me is that we can create and share collections between the team members."
  • "An area that needs some improvement would be to allow multiple windows with different collections to be open at the same time."

What is our primary use case?

We are using Postman for our testing and checking our API response and validations.

What is most valuable?

What is most valuable for me is that we can create and share collections between the team members.

What needs improvement?

An area that needs some improvement would be to allow multiple windows with different collections to be open at the same time. 

It only allows you to open one with the same collection. 

If we open a new Postman window, it does not allow me to have the same collection as I had in the previous window. Allowing us to have replicas of the same collection open independently would be helpful.

I would like to see if it can incorporate Jenkins integrations.

For how long have I used the solution?

I have been using Postman for five years.

What do I think about the stability of the solution?

It's a stable solution. It's running well.

What do I think about the scalability of the solution?

Scalability is not for load testing. 

You cannot scale vertically. You can only scale horizontally.

How are customer service and technical support?

I haven't contacted technical support, but they do have good documentation available online.

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

We are using the free version that is available.

What other advice do I have?

It's a good tool overall and quite stable.

It is mainly used for testing purposes, API responses, and validations.

I would rate this solution 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.
PeerSpot user
Senior DevOps Engineer at a tech services company with 201-500 employees
Real User
Good for anything API-related and has a good interface
Pros and Cons
  • "The interface and the different types of API methods you can use are the most valuable aspects of this solution."
  • "The pricing should be adjusted for the Pro plan."

What is our primary use case?

My primary use case is for API testing. 

What is most valuable?

The interface and the different types of API methods you can use are the most valuable aspects of this solution.

What needs improvement?

The pricing should be adjusted for the Pro plan.

For how long have I used the solution?

I have been using Postman for over a year. 

What do I think about the stability of the solution?

It is quite stable. I don't use it quite extensively but for what I use it for it's quite stable.

At my current company there are around 2,000 users. 

How are customer service and technical support?

I haven't used technical support. The documentation is quite good. I use the Postman website and forums. 

How was the initial setup?

The deployment depends on what you are going to use it for. It can be simple and it can be complex at the same time.

What other advice do I have?

When it comes to anything API related, I would recommend this solution. For anything API-related, it's perfect. REST API is the way to go and I would recommend Postman for it. 

I would rate it an eight out of ten.

The pricing is the only improvement. Its competitors are quite pricey. But it would be nice if there were more options like annual, monthly or enterprise-level.

Which deployment model are you using for this solution?

Hybrid Cloud
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: October 2024
Buyer's Guide
Download our free Postman Report and get advice and tips from experienced pros sharing their opinions.