I have mostly used Postman Enterprise for local development. Beyond that, we had cloud-related functionalities, so I never had to use Postman Enterprise on these external applications.
Postman Enterprise
PostmanExternal reviews
1,743 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Mock servers and API testing have streamlined local development and team collaboration
What is our primary use case?
What is most valuable?
The most valuable features I have found in Postman Enterprise are primarily the basic use for calling localhost URLs and calling some third-party APIs. Recently, I also had to create a server on Postman Enterprise for testing mock server functionality, which was very useful. Since I can configure whatever response is needed, I don't really need to write code to get the desired response. If some service is taking time or if it's a third-party service, it becomes easy to just mock the response and continue with work. Additionally, I can import and export the entire collection, so I can directly give the request payload and everything to people working with me. This makes it easier to get it on other machines as well. Postman Enterprise creates a file out of that collection, so it's not really a huge folder that I have to give to someone, even if there is a large number of requests.
What needs improvement?
I would like to see AI integration in Postman Enterprise. As I mentioned, I need mock servers at times, so it would be good if I can input my requirements in the mock server and it can itself create an output or mock response for me. If this could happen, it will save a lot of time. If that integrates with an IDE, it will be a game changer. Then it will become really easy. If it integrates directly with an IDE, it can release itself in the code and mock URL. It will become an entire flow for testing.
For how long have I used the solution?
I have been dealing with Postman Enterprise for about six to seven years.
What do I think about the stability of the solution?
Whenever I am checking the performance of the API using Postman Enterprise, the primary concern is how much time it's taking to return the response. The overall time of the API helps me understand whether it's working fine or not. I have an estimate of how long it should take.
Apart from that, I track time-related details on Postman Enterprise. Whatever is there in the code, logs and everything, I use that for tracking if any for loop is taking time or if there are database queries. I can check what is lagging in performance through those metrics as well.
What other advice do I have?
As far as monitoring is concerned, I have mostly been using Postman Enterprise for what I mentioned previously, specifically sending requests to the application and measuring how much time it takes to give the response.
I don't have much data about the automated testing capabilities in Postman Enterprise because I have been mostly using Jenkins with Groovy scripts. What I have seen is that they used to directly create pipelines using UI. I'm not very sure about this part of Postman Enterprise.
I have not worked on the integration of Postman Enterprise with tools like GitHub and Jenkins yet, where Postman Enterprise was already integrated with something like this.
I have not seen much use of Postman Enterprise for API governance capabilities in maintaining compliance and consistency within my organization up until now. For compliance or security, mostly what I have seen with Postman Enterprise usage is by developers on their machines. Apart from that, the people in the scripts use it, but apart from that, I have not seen much of it. I've not seen it cover larger operations in the organizations up until now. I have worked with, I think, about seven to eight clients, and I have not seen any one of them use it for these functionalities regarding compliance or security. So maybe it's not a very widely used feature as per my observation.
In my opinion, there is no room for improvement for Postman Enterprise because pretty much what is expected from Postman Enterprise for me is working fine and it is really useful. That being said, I have not used any other applications apart from Postman Enterprise. I don't have any comparison metrics, but this is really good. I never had to think if I should be using something else instead of Postman Enterprise. My overall rating for this product is 8 out of 10.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Great tool for API testing and debugging
What do you like best about the product?
I use Postman pretty much every day to test APIs and integrations. It makes it really easy to build requests, adjust payloads, and quickly view responses without having to write any extra code around it.
The collections feature is especially helpful for organising requests, and the ability to save and reuse them saves a lot of time. It’s also great for sharing with others when you’re working on the same integration, so everyone can stay aligned.
The collections feature is especially helpful for organising requests, and the ability to save and reuse them saves a lot of time. It’s also great for sharing with others when you’re working on the same integration, so everyone can stay aligned.
What do you dislike about the product?
It can start to feel a bit cluttered once you build up a lot of collections and environments, and navigating everything isn’t always as clean or intuitive as I’d like.
Some of the newer features also feel a little over the top if you’re mainly using it for straightforward API testing. I’ve noticed performance can dip slightly too as projects grow and things get bigger.
Some of the newer features also feel a little over the top if you’re mainly using it for straightforward API testing. I’ve noticed performance can dip slightly too as projects grow and things get bigger.
What problems is the product solving and how is that benefiting you?
It mainly helps with testing and debugging integrations. Rather than having to build things into the code just to test them, I can quickly send requests and see exactly what comes back.
It’s especially useful when I’m working with REST endpoints or troubleshooting issues between systems. It speeds things up a lot and makes it much easier to isolate where the problem is.
It’s especially useful when I’m working with REST endpoints or troubleshooting issues between systems. It speeds things up a lot and makes it much easier to isolate where the problem is.
Efficient API Testing with Room for UI Improvement
What do you like best about the product?
I love using Postman for API Testing and integrating APIs with our automation frameworks. It's easy to create different types of user states and behaviors, which speeds up my manual testing and accelerates our automation scripts using the Postman collections. I appreciate the easy way of understanding and keeping environments and collections in different folder structures. This allows me to adapt quickly and test features in various environments like stage, preprod, and prod by maintaining host URLs and keys separately. This structured format makes understanding and setting up simple.
What do you dislike about the product?
New UI is a bit confusing but I hope this also can be adaptable with the regular usage.
What problems is the product solving and how is that benefiting you?
I use Postman for API testing and integration, making it easy to create different user states and accelerate manual and automated testing. The structured format simplifies setup and helps manage environments and collections efficiently.
Postman Simplifies REST API Testing with Collections
What do you like best about the product?
Postman makes API development and testing simple and efficient. I mainly use it to test REST APIs in my Spring Boot applications, and it lets me quickly send requests, manage headers, and validate responses without having to write extra code. The Collections feature is especially helpful for keeping APIs organized, and environment variables make it easy to switch between different setups, such as development and production. I also appreciate the built-in testing scripts and the authentication support (JWT, OAuth 2.0), which saves me a lot of time during development.
What do you dislike about the product?
One downside is that Postman can feel slow or heavy when I’m working with large collections or keeping multiple tabs open. At times, syncing with the cloud workspace takes a while, which can get in the way of smooth collaboration. I’ve also found that some helpful features—like advanced monitoring and stronger team collaboration options—are limited in the free version, and that can be a real constraint for growing teams.
What problems is the product solving and how is that benefiting you?
Postman helps me test and debug APIs quickly without having to rely on frontend applications or write custom scripts. With it, I can verify endpoints, inspect responses, and automate test cases all in one place. This cuts down development time and makes it easier to catch issues early, which is especially valuable in a microservices environment. Overall, it boosts my productivity and helps ensure APIs are reliable before deployment.
A Developer’s Blessing for Fast, Reliable API Testing
What do you like best about the product?
Best thing i like about postman as a developer is it helps a lot to check the current status and response of api's to test and it gives proper response with code which helps a developer to find the route cause if any problem arises,
Most of the time, rather than checking the whole code, i check API in postman first to check wheather data is coming or not, if its api fault chhecking code is of no use, postman saves this time.
I usually use it more for SMS Service api test, to check the 3rd party api's wheather they are getting proper data or not.
at the end Its an very blessing software for developers, dosent depend you are a web dev or an app, same thing works for all.
Most of the time, rather than checking the whole code, i check API in postman first to check wheather data is coming or not, if its api fault chhecking code is of no use, postman saves this time.
I usually use it more for SMS Service api test, to check the 3rd party api's wheather they are getting proper data or not.
at the end Its an very blessing software for developers, dosent depend you are a web dev or an app, same thing works for all.
What do you dislike about the product?
Interface ban be improved, during run only the user interface iseems like complex. when i ask my Jr Developers to use the same, most of them gets confused with the UI, moreover for some config,its not fast, company should provide LITE Version for other users also who have low config machine.
Advance Team colabs are fully paid which limits user to a certain extent, this thing needs to be improved, and inteface should be very simple.
For experienced Developers its very good
Advance Team colabs are fully paid which limits user to a certain extent, this thing needs to be improved, and inteface should be very simple.
For experienced Developers its very good
What problems is the product solving and how is that benefiting you?
Testing and Manaaging api inspite of writing big codes helps a lot. it saves a lot of time and helps to avoid the errors in integration on live, it helps a lot to check like trial and error method type. managing multiple APi's in same software helps a lot. At the end of the day anything that matters is it saves your time.
It also solves debugging of code/issue
It also solves debugging of code/issue
Effortless API Testing with Postman
What do you like best about the product?
I find Postman very convenient for API testing. It's easy to create environments and collections, which helps me a lot. I like that Postman automatically creates a request when a curl is provided, and its ability to modify the body and payload is really useful. I can easily understand the existing API structure just by providing the curl and exploring the structure. Setting up Postman was very easy—just install and start using it.
What do you dislike about the product?
When using a request from a collection, I can't save the duplicate as a separate entry.
What problems is the product solving and how is that benefiting you?
Postman makes API testing easy, allows me to create environments and collections, and auto-generates requests from curl inputs, simplifying API exploration and modification.
Intuitive Interface That Streamlines the Entire API Lifecycle
What do you like best about the product?
Postman is highly regarded for its intuitive interface, which helps streamline the entire API lifecycle and makes the overall workflow feel more straightforward.
What do you dislike about the product?
The app uses a lot of resources (CPU/RAM), slows down noticeably with large collections, and the sign-in requirement has become increasingly pushy and feels mandatory.
What problems is the product solving and how is that benefiting you?
It’s a comprehensive API platform that addresses the pain of fragmented, manual, and unorganized API development and testing by bringing the work into a more structured, streamlined workflow.
Easy-to-Manage Dashboard That Keeps Everything in One Place
What do you like best about the product?
It is easy to manage and everything in postman and put all in one place, dashboard ui and everything is easy to understand.
What do you dislike about the product?
Only one thing I hate is about pricing and subscription model, when users increase cost is also increase. Rest is Everything Good.
What problems is the product solving and how is that benefiting you?
It's help me to make and manage api calls , put everything in one place, Centralized.
User-Friendly API Testing with Postman
What do you like best about the product?
I use Postman for making and testing APIs, which I love doing. As a full-stack developer, my work heavily depends on APIs. Postman makes creating and testing them easy and efficient, which I find invaluable. I really appreciate its user-friendly nature, allowing me to access APIs effortlessly and conduct tests smoothly. I also like the saving feature in Postman, which I think is fantastic for future tasks and something I truly enjoy.
What do you dislike about the product?
I feel API testing is a bit slow and could be improved. Also, there's no team sharing project feature, which makes me sad.
What problems is the product solving and how is that benefiting you?
I use Postman for making and testing APIs. It simplifies my workflow as a fullstack developer, making API creation and integration easy. It's user-friendly and allows easy access and testing. The saving feature is great for future use, though I wish it had a team-sharing feature.
The Industry Standard for Scalable API Development & Testing
What do you like best about the product?
Postman’s environment variables and collection runner are indispensable for backend development. I specifically appreciate how easily I can switch between local, staging, and production environments without changing the request body. The ability to write Pre-request and Test scripts in JavaScript allows me to automate authentication flows (like capturing a JWT and setting it as a global variable), which saves hours during recursive domain testing
What do you dislike about the product?
The desktop application can become quite resource-heavy (RAM consumption) when working with massive collections or multiple workspaces open. Additionally, the transition from the 'Scratchpad' to the forced Cloud Sync can be a hurdle for developers working on strictly local or offline environments, though the collaboration features partially make up for it.
What problems is the product solving and how is that benefiting you?
Postman bridges the gap between our NestJS backend and the documentation needs of frontend teams. It solves the problem of 'API drift' by providing a single source of truth for our endpoints. We use it to validate complex recursive domain models and ensure ownership inheritance logic is functioning correctly before we push to production.
showing 1 - 10