Postman Enterprise Reviews

We are primarily using the solution for API testing. We do some automation and validation.

The solution offers automation execution. You can do automation very quickly. We can access the variables. The environment setup is over there, and we can utilize it.

We can execute validations. 

We can get reports very fast. The generation allows us to share those with end users and stakeholders. 

We can access the solution quickly via a SSO.

It can scale well.

It is stable and does not lag.

The initial setup is easy.

Reporting can be better. If you have bigger APIs, it takes time. The process should be faster and more automated. We'd like more visualizations. 

I've been using the solution for three or four years. 

I'd rate the stability eight or nine out of ten. There are no lag issues. It's easy to use and reliable. There are no bugs or glitches. 

There are multiples for API testing. The scaling is fine. I'd rate the ability to extend eight out of ten. 

The solution works well at the enterprise level. 2,000 to 5,000 people are in that company. It's quite compatible with a range of company sizes. 

I've never used technical support. I can't speak to how helpful or responsive they would be. 

We do have another tool. We are using Jmeter, among others. However, I do not like its look and feel. Postman allows for saving collections and has a nice look and feel. 

The initial setup is simple. It's not overly complex. We have a desktop version and downloaded it to laptops.

I am an end-user.

I'd rate the solution eight out of ten. I've been happy with its capabilities so far.

Postman is an API regression suite, and we design different workflow center processes. We maintain the Postman tool and add JavaScript applications. Since it is not that robust, like ReadyAPI, we have to write many scripts to support it.

The UI is good. It's appealing and free, and everyone can use it.

Postman needs more advanced data-driven testing. We have to provide the data filter in runtime only. It's not like software, and we can add different data sources. That feature is not in Postman yet.

We have been using Postman for one year.

It is not that stable because the bigger the APIs, the higher the chance of crashes. Also, it takes up a lot of RAM and system memory, so it is not that reliable.

It is scalable, but it takes up a lot of resources. We have 40 users using Postman, mostly from the dev, automation and manual test teams. We use the solution weekly.

Postman has a support center, but they are not responsive. Many issues are still pending. I rate the technical support a six out of ten.

Neutral

You complete some setup processes for an application and have to provide the URL. It is not a complex setup. With a bit of understanding of API, it can be set up. I rate the setup an eight out of ten. There is a dedicated framework team for maintenance comprising about six people. Maintenance is required every three months.

Postman is open-source and free to use. I believe there is a corporate license they add to make it more robust and fast, but everyone mostly uses the free version.

I rate this solution a seven out of ten. You can use Postman if you are a beginner or trying to learn API. Small-scale organizations can also use it because it does not need any license.

Postman is gaining pace because it supports the Google Chrome compatibility rate and plugin support. It is easy to set it up for the testing team. It is a good tool, but it still needs improvement for a scalable API tool.

Regarding advice, there are some secure APIs in different organizations, so it's better to get approval from your manager or architect so that APIs are not exposed. Also, it is important to be cautious about the organization's sensitive data before implementing Postman.

We used Postman to test APIs before implementing them. We used the latest version of Postman, and it was deployed on a private cloud, AWS.

It is one of the important tools in API testing, and it helped out team develop mobile apps. First, it allowed us to understand the working and performance of the APIs so we could know how long it takes to give a response and analyze. Then, if there were any problems, we fixed them and implemented them in the code.

The best thing about Postman is it was very easy to use, and we could test APIs and get immediate results. In addition, we could share all our APIs with our other developers securely.

It is not that easy to use and should have a more improved easy-to-use interface.

It was stable, and there were no issues.

We didn't use any other solution before Postman. A senior developer suggested Postman.

It was straightforward to install. We just downloaded it and used it as a tool for testing our APIs. We had a back-end developer and two mobile developers utilizing this solution.

Its usage depends on how many APIs we have to test. So we had a complete collection of APIs that we tested, and once we tested, everything was ready.

There are no licensing costs, and we used it for free.

I rate this solution a six out of ten because no solution is perfect, and every software has missing features. Postman should consider adding more features in the future.

Regarding advice, don't mix up all the endpoints and organize your collections according to the use case. It will be very helpful for other developers to understand the use of the APIs.

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. 

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.

Postman is a good tool for completing a sanity check or smoke test of REST APIs. It's a quick way to manage your REST API-related test cases, and it gives good options for assertions for the response of the APIs. We have 30 people using this solution in our business. 

Postman uses the DRY framework of JavaScript and that framework is easy and a good way to put assertions on responses.

Postman could be improved by providing options for performance testing of APIs. We would like to complete performance testing of a specific set of API's by checking them against thousands of the records and checking responses times.

I have been using this solution for six years. 

This is a stable solution. 

This is a scalable solution.

The initial setup is straightforward and only takes a few minutes. 

I would rate this solution an eight 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.

We are using Postman to verify and test APIs.

The solution has helped us make better APIs. The solution is able to provide us with error reports if there are problems with the APIs. This has saved our developers time.

The most valuable feature of Postman is the verification and testing of APIs. 

Postman could improve the saving date capabilities. 

I have been using Postman for approximately five years.

The stability of Postman is good.

The solution is scalable.

All the developers in my company are using this solution.

I rate the support for Postman a four out of five.

Positive

I have used Swagger. I would recommend Swagger for the backend developers. The APIs only need to be set up once, then Swagger generates the document for all of them. In Postman the APIs need to be set up manually.

The initial setup of Postman is straightforward.

I rate the price of Postman a four out of five.

We evaluated other options before we choose Postman.

I rate Postman a nine out of ten.