Postman Enterprise Reviews

The primary use case for Postman is mostly for unit testing of the APIs. Additionally, I have developed scripts for end-to-end testing of the APIs.

One of the biggest advantages of Postman is its user-base approach. All collections created in Postman are not maintained locally and are instead maintained on the server, making it easy for me to continue work from anywhere if I log in with the same credentials. Any team member can continue the work as nothing is maintained locally.

One of the features that is missing in Postman is reporting; it's very basic. If they could enhance it and provide a browser-based dashboard view, it would be beneficial. 

Postman is limited to request and response kind of validation. If they can enhance it to have a database kind of validation like we have in ReadyAPI, it would be better. This feature would allow the response to be validated in the database as well.

I have been working with Postman for more than three years.

The solution is open-source and does the work required for day-to-day API testing activities. I would rate it ten out of ten for stability.

Postman does not have database validation available, which affects its scalability. If this option were available, I would rate it ten out of ten. Currently, I would say it is around seven or eight out of ten.

There is a lot of support available through forums and user groups, which has been sufficient for me. I hardly reach out to the vendor for support because the forums provide the required help.

To start with, Postman is a good option, but ReadyAPI is a commercial tool with lots of built-in features. If cost isn't a concern, ReadyAPI is better, however, if it is, Postman is still a viable choice.

The initial setup of Postman is very simple. There is an option for both browser-based and desktop applications. The desktop application requires installation, which is straightforward, while the browser option is also available and easy to use.

Postman is open-source, so the cost is minimal compared to commercial platforms.

I have a partnership with ReadyAPI but I am a Postman user.

If you compare Postman and ReadyAPI, Postman is a very good starting option. However, ReadyAPI, being a commercial tool, offers additional features. If cost is not a concern, ReadyAPI is preferred. 

Nonetheless, Postman offers ample features for API testing at no cost. 

Overall, I would rate Postman as eight out of ten. I can recommend this solution to other users.

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.

In our development, I basically use Postman just to test the APIs.

With the help of Postman, I explore API training and other features. It is beneficial to have flexibility, especially with API chaining. This feature allows me to combine and, with the help of some code, run multiple APIs at once. API chaining is a very good concept and easy to implement.

Since I am not exhaustively using Postman, I never think about its limitations. 

I have worked with Postman for the last four years. For four to five years, I have worked on Postman. Postman is a good tool.

I would say the scalability is very good since it is very scalable. I have never faced a problem.

I basically do not go to support. So I cannot tell you more, though I have some experience.

Neutral

I was using SoapUI before basically for web services. At that time, the web 3D AI concept was not implemented in the market.

Initially, the setup is a little bit complex. Whenever a user comes to Postman for the first time, it is just a bit complex since they do not know where to start and what is the structure. However, once a user has gone through the things, it gets easy. Other tools are easy to use for the first-time user.

Postman is easily available. Most of the features are already available, and people can learn and benefit from them. The other features are also very good in collaboration and API chaining. 

It is easy to maintain and easy to share with other users. For example, if I have created a collection, I can share the collection with others and get a benefit. 

This product deserves an eight out of ten. 

We use Postman for our day-to-day operations, investigations, and other tasks.

The value of Postman's collaboration tools, such as version control and team workspaces, is significant in maintaining and updating API projects, even though we don't use workspaces. I have an idea about the team workspace where I can invite my colleagues, and we can run on the API calls and all the functionalities we try to implement, which are transparent and visible to the other team members or invited members with access to that workspace. It's more about personal workspace and shareable workspace; you can do all your own work and shareable is something that you have to explore with someone else.

We don't have Postman integrated with our CI/CD pipelines; that's not under my expertise, but we do have it.

We use Postman Web; it's not that we bought Postman and integrated it with our cloud environments. It's only an end-user Postman we utilize, not at a full scripting level.

From my perspective, Postman offers great features, so I get a better opportunity to run bulk tasks through single command lines and single APIs, and we have an internal Postman AI tool, which helps improvise the code and analyze the quality if you find any errors. Instead of going into Google or ChatGPT or Gemini, the internal Postman AI is superior, and we also schedule certain calls for our operations. It helps reduce almost 90% of the manual effort in processes that we feel could take a lot of manual work.

I would appreciate seeing Postman become more automated. We need easier calls in the workflows. I tried to utilize the flows, but it wasn't clear under the documentation, and implementing it required more investigation. Eventually, we understood it, but we still need improvements in flows.

The environments, respective repositories, and collections we have are good for segregation. Another excellent aspect is that when we close Postman, it doesn't straight away terminate everything; it stores the values, which is very useful, as it has data storage and response storage benefits.

Regarding specific features that I'd want to see included in the next releases of Postman, I must say I'm not very involved with it daily. We utilize it in a randomized way—a couple of days or weeks in a month—based on our work dependencies.

Postman was one of the best solutions we found while researching, and we got training on it. We have been utilizing Postman from day one during training sessions, and when we checked for others, Postman offered a much easier user experience than the alternatives.

I can say that I'm using Postman with the REST APIs. The adaptability of Postman's support for both REST and SOAP APIs, as well as various data formats such as JSON and XML, is not something we do at that level of Postman. It's about our single time usage or consecutive runs usage, but not at that automation level. We do use a little scripting with REST APIs.

I don't utilize Postman's monitoring capabilities. I don't know anything about the pricing, as I'm working only on the free version of Postman.

Given my experience with Postman, my advice for other organizations or users considering it is that it's pretty simple to use Postman, except for the flows. For the flows, I expect to see more live examples or test cases within the documentation to utilize and learn it more effectively.

I would rate Postman as a product an eight out of ten.

I use Postman to test REST APIs. I work with Node.js and create or modify multiple endpoints, and I use Postman to verify if the endpoints work. Additionally, I use Postman to test other endpoints, like public endpoints.

In Postman, we have collections that contain multiple endpoints that I can test. I can use multiple environments, which allows me to create environment variables for each endpoint.

Something that could be better is the inclusion of another type of test, for example, end-to-end tests. It would be beneficial to expand functionality with additional testing options.

I have been working with Postman for five years.

Postman is pretty stable. I have not experienced any issues or downtimes.

The initial setup for Postman is very simple.

The price is low, making it a reasonable price for the product.

Postman is currently the leader.

I recommend Postman for all business types.

I'd rate the solution nine out of ten.

I have been using Postman for three years. I am not using the tool's latest version, Postman v10.11.1, but I am not sure. I think I am using the older version, Postman v9. I am just a customer of the tool.

The solution's most valuable feature is the data flow. In Postman, the API additions are very easy to process. I think there is no other tool that makes things very easy like Postman. Postman is user-friendly. We can understand all three types of calls very easily in a single frame only. Everything is available in just a click of it. I think the user interface is really good for the application because there are a lot of tools available that let you handle API integration with Postman.

I am not sure where the product can be improved since I have used only one particular application to work with API and not any other applications. I currently do not have anything, you know, for Postman to be improved upon because I am very satisfied with whatever they have right now.

The product lacks a good console. In the future, I would want the tool to have a better console. I feel that the console can be a better option that can be added to the solution. When we use the API calls, the results are available in the console. The tool's console can be a bit better and more interactive. It is very weak currently, and I feel that it could have a better interactive console.

I have been using Postman for three years. I am not using the tool's latest version, Postman v10.11.1, but I am not sure. I think I am using the older version, Postman v9. I am just a customer of the tool.

It is a very stable solution. For the past three years, I have not faced any major problems related to Postman.

A lot of people in my team use the product. I would say that over 100 people are using the solution.

I have not had any interactions with the product's support team since I have not faced issues with this solution.

The product's deployment phase is easy.

In terms of the deployment model, I would say that I use it locally in my system.

Postman is an open-source product. It is free to download from Google.

Postman is really great if you are working with APIs. It is very easy to understand, and I think that a lot of tutorials are already available on YouTube. I don't think you have to break your head to understand it separately. The tool's user interface is very friendly, and it is very easy to use.

I have not used to the monitoring and automation features of the product.

The integration capabilities of Postman help streamline development processes, and it is one of its main highlights. Presently, I think Postman lets you interact with other tools and web applications. It makes the development phase easy.

Postman is a really good tool for API integration. I don't see the tool lacking any features because Postman helps us with all the data governance parts.

It may not exactly be easy for beginners to start learning how to use Postman for the first time. If he or she has experience working with API, then it might be easy to use Postman. For people who have no experience with APIs, it might be a bit difficult in the beginning to use Postman, but after a certain point in time, it will be easy.

I rate the tool a nine out of ten.

There is a regular set of use cases, such as basic logins and long-form fills and submissions. There is a regular data set that we pick from the APIs, mostly with the GET, POST, and PUT calls. These are the three API methods we use regularly.

We are using the local version of Postman that we download for manual testing of the API. We do the automation directly in REST Assured with Java.

It makes manual testing very flexible, It's very user-friendly. When we do it through the Swagger file, we just go directly through a URL and hit the request/response, and validate that. Postman is very easy to use even for a person who doesn't have much knowledge or technical skills. It's very easy to use Postman and validate whatever we want to do. It's very comfortable and doesn't really require a user manual. It's a very user-friendly tool, and in a corporate environment, anyone can use the tool very easily. That's a benefit of Postman.

In Postman, we have an option to directly import a call, make it a Postman collection, and execute it in a batch. This feature is very useful. It saves a lot of time. The manual effort is also reduced when we can just pick it in a Postman collection and then run and execute it to get the results.

When you try to code something and put it in the code, it's not useful. We have our developers or testers who know Java, but Postman is not flexible to use. The option to code in Java is not there in Postman. In ReadyAPI, we do it through Groovy scripts. If there was a provision in Postman to write down a few steps in Java code and run them together, that would be an improvement in Postman.

In Postman, for now, we are just doing API validations and running API scripts. If there is any way to have a record and playback feature through UI, as we do in Selenium and IDEs such as Eclipse, it would be great.

It has been almost two years.

It's very stable. I haven't faced any Postman crashes. Very often, you have latency issues. When there are any additional pop-ups or more tasks when it's open, there are a few latency issues. Other than that, it's a good tool.

Performance-wise, it's pretty good. On average, it does the job right. It's good enough for our requirements.

It's scalable. They have put a lot of new features into Postman. They have developed it in terms of UX/UI designing as well as features like runner, input level, and raw text level. So, it's scalable, but the downside is that they don't have any UI level of testing, and it cannot be integrated with any other supporting tool. It's not scalable in that way. 

I don't know the exact count, but we probably have 100 to 150 people using it. We use it very frequently. We use it on a daily basis.

So far, I haven't faced any challenges with it. I haven't been in touch with their support.

I also work with ReadyAPI. ReadyAPI is a more advanced tool than Postman because a lot of heavy data can be driven and a lot of test cases can be automated and triggered on a daily basis. That's how I worked with ReadyAPI. Postman is more of a manual effort tool, whereas ReadyAPI is more of an automation tool. It did have the option of scripting in Java or JavaScript, but I just worked with Google Script with ReadyAPI. So, I haven't worked on any other programming language with ReadyAPI, and I'm not very sure whether it supports any other languages such as Python or JavaScript. Other than that, it works very well for regression cycles. Getting the email-triggering functionality was also very good. If you want to have a lot of automation and run it on a regular basis, it's one of the recommended tools.

It's straightforward for me. I've been using Postman for a while. You can just directly download Postman from the web and use the version on your desktop. It takes minutes to download the EXE file and install that. It takes around 10 to 15 minutes.

Its updates are not very frequent. It's once every six months or one year. There are not many failures in Postman.

We are using its free version.

You can just give it a try. You can start with the free version and later upgrade to the paid ones. You would be able to do most of the things through the free version of Postman.

You can just learn the basic commands of Postman, various types of authentications, and the basics of API. You can learn how to send the environment variables, how to set the headers, etc. If you know all these things, it's very easy to use the Postman tool on a daily basis.

It's a very good product. I would rate it a nine out of ten.

We have been using Postman primarily for API automation.

API automation is crucial because every change in an API could have a significant impact. Postman has greatly reduced the effort required in testing APIs, thus enhancing our efficiency.

Postman is easy to use and enables us to test all possible API testing scenarios. It is economical compared to other testing tools, which is a valuable feature for us.

The main improvement needed is better integration with test management and other tools to allow a common dashboard for all testing metrics and details.

We have been using Postman for four to five years.

Postman is stable enough for our needs, although we have not tested it extensively with a large number of test cases.

We did not test Postman with thousands of test cases, so we cannot comment on its scalability for larger repositories.

We have not contacted Postman's technical support as we have managed all our needs internally.

Positive

Prior to using Postman, we used SoapUI. SoapUI was very basic and lacked many features that were then added in the paid version, SoapUI Pro, which was expensive. Postman provides better features than SoapUI.

Installation of Postman is straightforward and can be completed in a few hours by one person.

We did not require any external team for the implementation and managed it internally.

The return on investment is significant due to Postman's efficiency in automating API testing, which involves many input and output parameters.

Postman is economical and is considered to be rather cheap compared to other software solutions.

I have evaluated other tools such as Katalon, Tricentis Tosca, and Universal Function Test (UFT) from OpenText.

I would recommend enhancing Postman's integration capabilities with test management tools to better consolidate testing metrics.

I'd rate the solution eight out of ten.

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 used the solution in multiple ways, including:

1. We create Rest APIs for the communication of the front end to the backend. For the testing of those Rest APIs, we use Postman. It provides a user-friendly platform for API testing with all the request methods like GET, POST, PUT, DELETE, PATCH, and many more. We can create our own collections like group requests. We can easily share the collection with the team.

2. We are using Postman to create the documentation of the REST APIs, which the backend team creates, so the frontend engineer can easily see the request type, headers, methods, and response body for the request. 

3. It is also used as an API testing tool by the automation testing team. We can write our own tests with the assert statements in Postman after the response. 

Postman helps us to automate the API testing in the team.

It helps to share the Rest API documents with the front-end team so that they can easily integrate the API with the front-end.

It also helps in the monitoring of the APIs to check the health of an existing API.

It makes API development and testing faster and more user-friendly. It does not require any prior knowledge to work with the Postman. 

It supports the GQL requests as well as the REST API.

It allows all the request methods like GET, POST, PUT, PATCH, DELETE, COPY, OPTIONS, LINK, UNLINK, and many more. 

It allows all types of authentication requests like API Key, JWT bearer, Basic OAuth, OAuth 2.0, Bearer token, and many more. 

It allows us to set the environment variables as per our different environments, like QA1, QA2, STAGE, DEV, PERF, and UAT.

It allows you to write the pre-request script that runs prior to any API call. 

It allows us to save requests in a collection and share the collection with the team.

There is no support for the SOCKET testing with Postman.

There is no support for the testing of the SOAP APIs.  

Sometimes it crashes when a lot of collections are imported in a Postman.

There is no mechanism for parallel testing. 

There is no scope for load testing like in JMeter. 

There is low script reusability. 

It does not support SMTP protocols; it only allows HTTP protocol.

It does not allow for a data-driven approach. It cannot get the data from a database and use it for testing purposes.

I have been using Postman for the last three years.

It is easy to use and is a lightweight solution. For the last three years it has been working perfectly fine, and we are using it for API development, API testing, and documentation to share with the front end.

We can easily use Postman for large projects. We can create collections - as many as we want - and share them as JSON, for example.

There is a huge community of Postman users. I have never had a chance to connect directly with the support team of Postman as I get help online. 

Positive

We have been using Postman from the start as it is user-friendly and does not require any prerequisite language to use it.

It's quite easy to set up. You simply download it and then install it and start using it. 

We are using the free version as of now. However, the paid version allows users to create the workspace and share the common collection with more than four teammates.

We evaluated Katalon as well.

It is easy to use. However, it does not allow for Socket and SOAP API testing.