Postman Enterprise Reviews

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.

I am working for an insurance firm, a big client in the USA. They wanted to upgrade the current technology with something new. However, they have legacy applications, and they don't want to handle APIs. They didn't want anything to hit their existing API since they have two layers of APIs. 

At the same time, there are different components with around 17 to 18 integrations and various applications.

We wanted one tool that could help us handle the restrictions and the implementation. This is both an API and a very helpful testing tool. It's user-friendly for everyone using it in a big firm.

There is a product called Guidewire that sends the data in an XML format. It's like a policy load. That information we trigger in Kafka. Kafka will take the information and send it to the REST API. With Kafka, they wanted to make two APIs to consolidate the effort. At that time, we are using the POST API tool. This tool is helping us to synchronize everything.

The version control is great. It can detect IP addresses really well.

It has a helpful API network.

The scalability is good.

It has been stable.

I haven't seen anything lacking in the solution. 

Support is not that good.

We'd like to see videos or user-friendly reference documentation to help us figure out the solution or troubleshoot issues on our own. That would be especially helpful for first-time users. 

I've worked with the solution for 18 months. 

The stability is okay. It's pretty reliable. I'd rate the stability seven out of ten overall. 

The scalability is good. I'd rate it eight out of ten. 

We have 70 top 80 people using the solution right now. 

We likely will increase usage in the future. 

Technical support hasn't been too helpful. On top of that, the documentation is lacking a bit. They're okay. They could be better.

We did not previously use a different solution. 

My understanding is that the solution is straightforward to set up. There are some challenges, sometimes, around configuration, specifically with REST API, however, it's not too difficult.

I'm not sure how many people are needed to deploy and maintain eh solution. We have a team of five or six, and we can handle it internally. 

We handled the setup in-house. We did not need outside assistance. 

I wasn't involved with the pricing. I'm not sure what the exact licensing costs are. My understanding is it is not too high. 

From a collaboration point of view, it's a useful tool. It's also super user-friendly. I'd rate it nine out of ten overall. 

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.

I use Postman for API testing and plan to start using it for automation testing.

Postman is useful for API testing. It also allows me to have multiple workspaces to share with my developers. I've just started using the mock servers and defining the flows, but that will take time.

The scalability of the solution can be improved.

I have been using Postman for more than seven to eight years.

The solution is stable. I rate Postman a ten out of ten for its stability.

The solution is scalable. Currently, three people are using the solution in my company. I rate Postman a six out of ten for its scalability.

I raised only two queries to the support team in the first month. I got responses for both of my queries when I was creating my mock service. So, the customer support was quick, and my issues were resolved.

The initial setup is easy and I rate Postman a ten out of ten for its initial setup. The deployment of the solution doesn't take much time. It just requires a few hours.

The solution has moderate pricing. We pay on a yearly basis for the solution’s licensing fee. I rate Postman a six out of ten for its pricing.

I have not yet updated to the 10.12 version of the solution. I use the solution very, very often, four times a week. I would recommend Postman to other users.

Overall, I rate Postman a nine out of ten. Once I cover the mock servers and automation, I should be able to give a higher rating.

I primarily use Postman to manually test our APIs with HTTP and REST calls. I don't use the more advanced features, such as script automation.

Postman lets you create, manage, and validate a suite of tests. It has several features to help you organize your test suite. You can also automate stuff with a lot of validations and assertions. Postman supports GraphQL, and you can do various kinds of calls. 

The reporting could be better. It should give you a detailed PDF report after you run a test.

I have used Postman for about four or five years.

Postman is stable. 

Postman is scalable.

Setting up Postman is straightforward and takes about an hour. 

We use the free version. They introduced a new licensing model where your company must subscribe to their services if you're using it for business purposes. However, I think they charge too much if you're only using the basic features. It limits what your organization can do if you're not a paying customer.  

I rate Postman a seven out of 10. I think seven is a decent score because it's a solid tool that installs quickly and has tons of features. Postman supports multiple formats of REST and GraphQL. You can automate your test suite and run regressions. I don't think Postman lets you connect to a lot of databases, which could be a limitation, but I recommend it. 

We use the solution for rest API testing purposes.

The solution's most valuable feature is code-based API testing. The technicians have complete control over the business logic code in the test tool.

Occasionally, a few variables get errors due to concurrent instances running simultaneously. They should improve this particular area. Also, providing more specific documentation on configuration would be helpful.

We have been using the solution for three years.

It is a stable solution. I rate its stability as a ten.

The solution is scalable.

I visit online forums for technical support in case of any errors.

We used UFT earlier.

The solution's initial setup process is straightforward. You must know about the required environment and security credentials for implementation. It needs two test automation engineers and one business analyst to execute and takes a few hours to complete.

I rate the process as an eight.

The solution's price is reasonable. We pay around £70 a month for it. I rate its pricing as one.

I advise others to gain knowledge of JavaScript. It will help them use the solution's test automation framework with ease.

I rate the solution as a nine.