Postman Enterprise Reviews

My main use case for Postman Enterprise includes API testing and validation, team collaborations on APIs, automated API collections and framework, sharing environment and documentation across the team, and regression testing during releases. We monitor API performances, both uptime and downtime, and mainly use it for integrations with CI/CD pipelines and faster debugging and development coordination. The main benefit of using Postman Enterprise is centralized API management for larger teams and enterprise projects.

Recently, our team used Postman Enterprise to maintain the shared API collections for multiple microservices, developing and testing the endpoints before deployment using predefined environments and test scripts. The QA team runs the automated regression collections during release cycles. Common variables, tokens, and mock APIs are shared centrally, avoiding duplications. We also use it for API documentation, which automatically updates and is accessible to all teams, and integrated with CI/CD helps catch API failures before production deployment.

Postman Enterprise helps improve collaboration, standardizes API testing, and speeds up the development and release cycle. It is very helpful during the release cycle, especially in documentation and release cycle management.

In terms of the best features I have experienced with Postman Enterprise, they include API testing and annotations, shared workspace and team collaborations, role-based access, single sign-on (SSO), private API network, API governance for audit logs, and mock servers. We can test our applications before release with centralized and secure API management for the enterprise team.

The shared workspace and role-based access improve collaborations by keeping API collections, environments, and documentation in one project, reducing duplicate work and version confusion across teams. The role-based access helps control who can view, edit, and manage the APIs, improving security and preventing accidental changes in the production collection, which we have faced multiple times before going to production when those who should not have access edited files by mistake.

Postman Enterprise has positively impacted my organization in various ways, including faster API development and testing than before, improving collaboration between developer and QA teams. It has reduced manual testing efforts through automation, leading to fewer integration and development issues after adoption, as well as better API documentation and visibility.

In terms of improvement, the UI can sometimes feel heavy for larger collections in the workspaces. Additionally, performance may slow down with complex API projects, and pricing can be expensive for smaller teams. However, it is quite suitable for bigger teams. Other areas for improvement include better reporting and analytics dashboards, and more advanced native test environment features could enhance workflow, with smoother offline support and sync handling.

Additionally, better performance for very large collections would be helpful, along with more intuitive navigation for enterprise-scale workspaces, stronger reporting analytics, easier management of permissions across large teams, and more flexible automation and testing report options would be beneficial. Small usability and performance improvements would make Postman Enterprise even more efficient for larger organizations.

Postman Enterprise needs better performance optimization for large enterprises, more detailed analytics user reporting, improved API governance and audit visibility, simpler permissions and access control management, faster sync and loading times for larger collections, and more advanced built-in testing and reporting capabilities.

I have been using Postman Enterprise for the last two years.

Postman Enterprise has been pretty stable and reliable for us. Overall, it has consistently supported our day-to-day use of shared API collections and automated testing, and we have never experienced major downtime.

Postman Enterprise scales well for larger projects and growing teams, supporting centralized workspace management, team collaborations, role-based access control, SSO, and governance features for enterprise-scale use. Multiple teams can work across shared API collections and environments without major workflow issues, and features like organizations, private API networks, and advanced admin control help effectively manage large distributed teams. CI/CD integrations and automations support the increasing API workload and release cycles, demonstrating strong scalability for enterprise API development, governance, and collaboration workflows.

We have interacted with the support team mainly for licensing, workspace management, and integration-related issues, and overall, my experience has been positive and professional. The response time is generally good for enterprise-level tickets, and the documentation and community resources are helpful for resolving common issues. However, some complex issues take longer to escalate and resolve, and overall customer support has been reliable and supportive for enterprise users.

Rating the customer support is a bit difficult, but I would rate it an 8 out of 10.

Previously, the team relied on a mix of tools like SOAP UI, manual testing methods, and custom scripts. Collaborations and sharing were less organized compared to using Postman Enterprise, which necessitated setting up meetings for small updates and bug sharing. Managing environments and documentation across different teams was very difficult, and automating CI/CD integrations was less streamlined. This need for a more centralized, collaborative, and enterprise-friendly API platform with better automation and team management features is why we switched to Postman Enterprise.

The initial setup is relatively smooth, as the platform is cloud-based and easy to onboard, but most effort goes into organizing workspaces, collection permissions, and team standards. Licensing and user management are handled centrally through enterprise admin control.

We have seen a clear return on investment after adopting Postman Enterprise by automating API testing and significantly reducing manual testing efforts. This decrease has allowed for a shorter production cycle, and regression testing time reduced from nearly a full day to just a few hours. Faster bug detection has helped reduce production issues and rework, improving collaboration and reducing delays between development and QA teams. Teams can handle more API releases without increasing testing resources, leading to better productivity and faster release times.

When it comes to pricing, setup cost, and licensing, my experience indicates that the pricing is on the higher side, especially for smaller teams and growing organizations. However, enterprise licensing provides strong collaboration, security, and admin features that justify the cost for larger scale users.

Before choosing Postman Enterprise, we evaluated tools like SOAP UI, Swagger Hub, and Paw. We chose Postman Enterprise because it has better collaboration features, an easier UI, and onboarding processes. It offers strong automation and CI/CD integrations, and its centralized workspace and API management are advantageous for large cross-functional teams.

My advice for others considering Postman Enterprise is to maintain standard API collections and naming conventions earlier on, as this helps in organizing workspaces properly for different teams and environments. Utilizing automation along with CI/CD integration brings maximum value. Setting clear role-based access control from the beginning simplifies later adjustments. Maintaining clean documentation and shared environments will be very helpful and time-saving, and starting with governance practices is recommended.

Postman Enterprise is a strong enterprise-grade API collaboration and testing platform that significantly improves API development workflows, automation, and team coordination. It is best suited for organizations managing multiple APIs and cross-functional teams. While the pricing and performance for large workspaces can be improved, the overall value and productivity benefits are remarkably strong, offering great potential for teams seeking to standardize and scale API operations efficiently. I would rate this product an 8 out of 10 overall.

I use Postman Enterprise for API testing, collaborations, automated collections, environment management, and integration with CI/CD pipeline workflows for backend services.

Recently, while working on a backend order processing flow, I used Postman Enterprise to test APIs across multiple microservices such as inventory, payment, and order management. I created collections with automated test scripts and used the environment for different stages including dev environment and staging environment, then I shared the collections with the teams to validate the API response and catch the integration issues before deployment.

Apart from this, I have also used Postman Enterprise for API documentation and collaborations between frontend and backend teams, which helped keep API contracts consistent and reduce integration issues while speeding up testing during releases.

The best features of Postman Enterprise are team collaborations, automated API testing, environment management, and API governance. The shared workspace and collections make collaborations very smooth across the teams, and automated testing and CI/CD integrations help catch issues early. I also appreciate the governance and security features because they help maintain API standards and consistency across large projects.

API governance has helped my team maintain consistent API naming, request structures, and documentation standards across multiple services, reducing confusion between the teams and making onboarding easier. On the security side, environment variables and access control helped me avoid exposing sensitive data such as tokens or API keys, and they also made collaborations safer because different teams could access only the resources they needed.

I found that the collections runner and automated testing features are very valuable because they save a lot of manual task time and help identify issues quickly during deployments.

Postman Enterprise has improved collaborations, reduced API integration issues, and sped up the testing cycles in my organization. It provides a centralized platform for API development, documentation, and testing, which has improved consistency while reducing communication gaps between the frontend, backend, and QA teams. It has also helped catch issues earlier in the development cycle, improving overall release quality.

Postman Enterprise could enhance performance for very large collections and complex workspaces. Sometimes managing a huge number of APIs and environments can become difficult, and better advanced reporting, deeper analytics for API testing trends, and more simplified governance management for large organizations would also be valuable improvements.

Apart from this, improving offline support and reducing workspace loading time for larger teams while making collaboration conflict resolution simple would help a lot. More AI-assisted debugging and smart API testing recommendations could also make the platform even more efficient for enterprise teams.

I have been using Postman Enterprise for the last three years.

Postman Enterprise is quite stable based on my experience. I have not faced any issues, and overall, it is reliable for day-to-day API development and testing workflows.

Postman Enterprise is well-suited for large organizations, especially for teams working with APIs and microservices. Features such as shared workspace, role-based access control, governance, private API networks, and organization-level management make it suitable for enterprise collaboration. It also integrates well with CI/CD and cloud environments, supporting growing engineering teams. The main scalability challenge I have seen is performance slowdown when handling extremely large collections or very heavy workspaces, but overall, the platform is designed to scale effectively for enterprise API workflows.

The customer support was generally good in my experience. The documentation, community support, and onboarding resources were especially helpful for quickly resolving common issues. For enterprise-related issues, response quality was pretty good overall, though sometimes complex support requests could take longer to resolve. The support experience was reliable and professional.

Earlier, I used a mix of manual API testing tools and custom scripts for validations. I moved to Postman Enterprise because it provided a centralized platform for collaboration, automated testing, environment management, and API documentation, making workflows much more organized and scalable for larger teams and microservices-based systems.

From an engineering perspective, the experience with pricing, setup cost, and licensing was good because the platform provided strong collaboration and governance features that justify enterprise use. Setup was fairly straightforward for developers, especially with cloud integration and SSO support. Licensing and pricing felt more suitable for medium to large organizations rather than small teams since pricing is generally user-based, and enterprise features come at a premium cost.

I am not directly involved in the purchasing side, so I cannot confidently confirm whether it was purchased through the AWS Marketplace. My involvement is mainly on the engineering and API development side.

In terms of ROI, I saw clear time-saving productivity improvements mainly through automated API testing and better collaboration. Manual testing efforts were reduced significantly, integration issues were caught earlier, and release cycles became faster while reducing back-and-forth communications between frontend, backend, and QA teams because everyone worked from the same API collections and documentation. Earlier, I took one week for all planning before releasing some activities, which reduced to three days, sometimes to two days, which is about a 50% improvement in engineering efforts, time, and release cycles.

From an engineering perspective, the experience with pricing, setup cost, and licensing was good because the platform provided strong collaboration and governance features that justify enterprise use. Setup was fairly straightforward for developers, especially with cloud integration and SSO support. Licensing and pricing felt more suitable for medium to large organizations rather than small teams since pricing is generally user-based, and enterprise features come at a premium cost.

Before choosing Postman Enterprise, I evaluated tools such as Swagger, OpenAPI tools, and Insomnia for API testing and documentation workflows. Postman Enterprise stood out mainly because of its collaboration features, enterprise governance capabilities, shared workspace, and strong ecosystem integrations for larger development teams.

My advice for potential buyers would be to define your API workflows and collaborations needed before adopting Postman Enterprise since it provides the most value for teams working with multiple services, shared APIs, automated testing, and CI/CD integrations. I would also suggest setting up governance standards and environment management early, as that helps maintain consistency and scalability as organizations grow. I would rate my overall experience with Postman Enterprise as an 8 out of 10.

Our main use case for Postman Enterprise is API development, testing, and collaboration with other teams. We also use it heavily to design APIs and test endpoints and then share the collection within the team so that everyone is aligned.

The best feature that Postman Enterprise offers is the collections that we can create and then share with the other team. Postman Enterprise also has collections and environment management. We also have automation of testing if we use some scripts. Then we have API document generation as a feature. We also have history tracking enabled in Postman Enterprise.

The collaboration impacts our team the most because it has reduced the time required for our API testing and improved our collaboration between the teams such as development, QA, and integration.

Postman Enterprise has impacted our organization positively because on a day-to-day basis, when we are developing APIs for different services, we have to validate the different APIs. When we design this, we should not impact the old ones. Therefore, we have these collections useful in Postman Enterprise that we can share across team members. They can validate if anything is wrong in the existing when we are trying to push the new code. This helps us avoid recreating it, and we can just use the old collection that we have already. Another positive impact is the history feature. The history feature has really helped us a lot. There were cases when we tested an API earlier and needed to recheck the exact request. Instead of recreating it, we could just go back to the history and then find the request and then reuse it. This saved us time and also avoided errors, especially when we were debugging the issues.

One area for improvement is that sometimes performance is slightly slow when we are handling large collections. Also, we need better integrations with CI/CD tools so that automation would be smoother.

I would add one more needed improvement: the UI sometimes can feel cluttered. There are too many options when there are too many collections. A more simplified navigation would help for large-scale usage of the collections.

I have been using Postman Enterprise since six or seven years now.

In our experience, Postman Enterprise is stable. We have not faced many issues or any downtime because it is a desktop application. We do not feel any slowdown or anything with respect to the stability of the tool.

As we discussed earlier, when it comes to bigger collaborations or bigger collections, some performance tuning is expected and is needed. However, it is quite scalable, especially for growing teams with multiple APIs and environments. It supports collaboration, therefore collaboration is good and scalability is also good.

Customer support is really good.

Previously, we used basic tools and sometimes manual API-level testing methods. We switched to Postman Enterprise because it provides us a centralized, structured way of working.

Pricing-wise, the cost feels justified given the features such as collaboration and the collections that are there. The setup was straightforward, and we did not require much effort because from our side, it was really simple. Licensing is also simple and flexible, however managing seats for bigger teams needs some planning. Overall, the experience was smooth, just slightly expensive.

We do not have any integrations with Postman Enterprise. It is a standalone application in our use case.

We have definitely seen ROI, mainly in terms of time savings because we reduced the duplication of work, and also we have better collaboration because of Postman Enterprise.

Almost 30% of our time has been saved when it comes to complete regression testing of one feature. That is the rough estimate I can provide.

Before choosing Postman Enterprise, we did look at SoapUI, but Postman Enterprise feels more user-friendly, and it is better for collaboration.

I feel the AI features are helpful, especially in generating test scripts or suggestions. I think governance and security are handled very well. Overall, this is an enterprise tool, so there will be proper access control, and data is managed securely.

The AI features are helpful. Accuracy is good in most cases, but sometimes we need to still validate manually.

Postman Enterprise helps our organization ensure compliance with industry standards or regulations, but this is a desktop tool, so it does not mainly do many things around compliance issues as things are handled manually by the user. You should be taking care of how the request should be sent and what are the necessary parameters and what are the necessary headers you need to pass in the API. The user who is using the product should be taking care of this. Postman Enterprise does not necessarily have to take care of the industry standards or regulations.

For new users adopting Postman Enterprise, I would say the learning curve is flat. It is not hard to learn; it is very easy to learn how to use Postman Enterprise.

Postman Enterprise supports team collaboration and communication through a workspace, so we can share our collections or the requests to the API, and everybody can then utilize it, and they will get updates if something is updated.

Version control in Postman Enterprise in the sense that whenever we need to update anything, we save it in the workspace or in the collections. In our case, we mainly use different versions of collections either by duplicating them or naming conventions such as V1, V2, V3. So it is not exactly a traditional code versioning, but it works well when we are doing API-level tracking. There is no built-in version control and activity tracking, so we need to take care of those things.

Postman Enterprise handles large numbers of APIs or high request volumes well when we have a lot of data and also when we have a lot of things in the API request. However, especially when there are a lot of things on Postman Enterprise already preloaded, such as collections and workspaces, it becomes laggy. In that situation, if we are trying to handle a high request volume, then it is handling it fine for testing and development use cases. However, if the collections become very large, then we notice that there is a slight performance lag in the UI. Overall, it is reliable, but managing the structure properly becomes important when it comes to a large scale.

Postman Enterprise helps our organization with API documentation significantly since we can generate and share the documentation directly from the collection. It keeps everything centralized and up to date, which is helpful for internal and external teams. However, for onboarding new team members, I do not think we take care of it in Postman Enterprise. If you want to give somebody some information, we can give it independently.

For the person who is trying to look into Postman Enterprise, I would suggest starting with a proper organization of collections and environments from the beginning of its use because it will be better organized. Then you can make full use of workspaces and documentation features so that it will help your collaboration. You can also try the tool with a small team before scaling up the team. I give this review a rating of 9 out of 10.

I use Postman Enterprise for testing APIs in my day-to-day work. I have a workspace with specific API requests, and I am using that workspace to test our API endpoints. I examine what kind of requests we are sending, what kind of errors we are receiving, and the logs. Based on those requests, I write tests, and from those tests, I can understand if our API is working correctly. Based on the logs I get in the tests, I can easily write a report for our engineering team to check if there are ongoing issues with our current platform, our current endpoint, and why it is happening according to the logs.

In my team, we use it only for testing different case scenarios for different endpoints.

Postman Enterprise is efficient because if you write 10 different requests, and then need to write similar requests with only a few variable or parameter changes, you can duplicate that set of requests and modify what needs to be changed. You can extract the whole workspace in a JSON file and modify it easily with different tools, then import that updated JSON file back to Postman Enterprise. You can duplicate the whole workspace, and one workspace can have 10,000, 20,000, or even more requests where in the new workspace you just need to change access or different case scenarios.

The most valuable feature is that you can set a collection of requests and run that collection in an automated way. For example, with 200 requests, you run the collection, and each request will run sequentially, where you can easily create or test several different scenarios. Additionally, in each request, you can define a test to see if your request was successful as planned, or if that request followed the procedures written for our API.

It is straightforward if you have all access tokens and necessary access to the API provider itself. With access tokens, refresh tokens, or authorization set up in place, it takes just a couple of clicks to integrate Postman Enterprise with this environment.

I can set up environment variables quickly, so I have my pre-written variables in place. I can easily link them to each request without hard-coding any data or variables as they are read from the environment variables. You can duplicate the entire list of variables, change different naming, and they are ready for different sets of requests. The bundle of requests runs quickly in an automated way, and they execute in the order you specify. You can check the logs and terminal logs to see what is happening in the background, and easily connect Postman Enterprise with your API if you have the proper access keys. The visualization allows you to quickly notice and search the parameters, error types, or specific items. You can extract the JSON file of your workspace, check it with different tools, look for errors and improvements, and then import that JSON file back to Postman Enterprise to continue working on that set of requests, or send it to colleagues who can work on the same requests without writing them from scratch.

Since I am using the free tier, one improvement would be to increase the number of requests you can send in a short time period. Currently, if I send 200-300 requests in a short period, Postman Enterprise requires a 30-second wait before sending another bundle of requests unless you upgrade to a higher tier.

Secondly, Postman Enterprise sometimes takes several minutes to load the whole workspace. With 2,000-3,000 requests in a workspace, it can take a minute or two to load all requests. When creating a new workspace and moving requests between workspaces, depending on internet speed, it can take a longer period to copy those requests or workspace from one place to another.

I have been working with Postman Enterprise for two years now.

It depends on various factors. Sometimes it can be slightly buggy. It might skip requests and relies on internet connection, but even with perfect internet connection, it can occasionally have glitches. In my two years of usage, I only experienced one global incident with Postman Enterprise, which was announced and fixed within minutes or perhaps half an hour. It is a pretty stable solution.

I opened one case during a global incident, and they replied quickly to inform me about the situation. They updated us via their global incident platform. The process was straightforward.

It is quite scalable from my perspective because you can create different workspace scenarios in seconds. I can quickly extend my testing area by duplicating and copy-pasting different workspaces and environments, then adjusting what needs to be adjusted. However, I cannot speak to scalability for different Postman Enterprise purposes on a broader scale.

I opened one case during a global incident, and they replied quickly to inform me about the situation. They updated us via their global incident platform. The process was straightforward.

In my experience with only one case in less than two years, I would rate their service 10 out of 10 because everything was super fast and professional.

I personally used RapidAPI before.

Postman Enterprise is superior because you can create several different environments with pre-written variable environments for different use cases. You can switch environments to connect to different instances of your platform or client partners. You can test various scenarios quickly with the same request, which is not possible in Paw currently. Paw and RapidAPI are lightweight versions. Postman Enterprise allows you to write scripts for checking your requests through test scripting, which I believe RapidAPI does not offer. These features motivated my transition from Paw to Postman Enterprise.

The setup is straightforward if you have all access tokens and necessary access to the API provider itself. With access tokens, refresh tokens, or authorization set up in place, it takes just a couple of clicks to integrate Postman Enterprise with this environment.

I would rate Postman Enterprise 8 out of 10. Based on my experience with one support case in less than two years, I would give them a perfect score because everything was handled quickly and professionally.

I primarily use Postman Enterprise for API level testing with all the methods that we have: GET, PUT, POST, and DELETE.

On a day-to-day basis, we have many requests that we put into Postman Enterprise, and then we hit the request and check what response we are getting. Postman Enterprise has many features where we can store our requests and create a collection. We can then use those collections and share them with other people that we are collaborating with in our team.

In our case, we use Postman Enterprise for API development when we want to test it and collaborate. Developers use it for testing whatever they have implemented, and testers use it for checking all the changes that have been done. This allows us to verify whether there is any impact or if all test cases, edge cases, and rare case scenarios are working as expected. Postman Enterprise also enables collaboration through collections and workspaces, which can be shared with our teammates.

We also have a place in Postman Enterprise where we can specify what environment we are testing in. If we are testing for another environment, we can specify that as well. We can test at one level and then test another in parallel or sequential order, which is also possible in Postman Enterprise. Overall, the API development lifecycle has improved because we use Postman Enterprise.

The best feature of Postman Enterprise is the collections combined with team workspaces. These stand out most to me because they make it easy to organize and share with the team. We can maintain version consistency and collaborate without duplicating our work.

Postman Enterprise has had a positive impact on our organization in that we do not have to do duplicate work. Because we have collections in Postman Enterprise, we can share the work that we have done. We have seen improvement when it comes to dividing the work in Postman Enterprise, as we are able to divide it very efficiently with the feature where we can share the work and workspaces.

For example, once we were testing an application from front-end to back-end and back to front-end, which gave us a response. We had to check many things, and there was involvement of three APIs. We had to test three APIs in a way that each layer would give us a proper response. We were testing these three layers with three people, and we all had the same request, but we had to do it in three different ways. What we did was split the work by sharing the same collection with my teammates. One of us tested the first layer, another tested the second layer, and another tested the third layer. Once that was done, we also tested the end-to-end scenario. This is how Postman Enterprise has helped us in testing.

I think Postman Enterprise can be improved in the way that it has many features that are spread across all the screen. I feel if I could get all the features on one side, such as on the left side, and the main place where I have my request and run the thing should be main in the right side or in the left side. Eighty percent of the main work should stay in the center instead of arranging all things around it. This makes the main space look a little small, which is what I do not prefer about Postman Enterprise.

I have been using Postman Enterprise for four years.

Postman Enterprise is stable.

I feel Postman Enterprise's scalability is good.

We switched to Postman Enterprise.

I think out of six working days, we are able to save at least one day using Postman Enterprise for collaboration and sharing.

We do not have to take a license for most of the use cases in Postman Enterprise. However, if you want to use more AI and automation, I think you should use the subscription or licensing. If you want to share with the team, then we need to have a team license because sharing, collaboration, team, workspace, and collection require an unlimited license. We take the minimum cost subscription and it is really easy to obtain.

I would suggest that you can keep the collections handy when using Postman Enterprise. You can arrange all your things in Postman Enterprise in the way you prefer. It is really flexible. Before taking a license, I would recommend that you take a trial and understand all the features. According to the features that you need, you can choose the plan of licensing that suits you.

Sometimes I have given Postman Enterprise a request that was having some issues with the formatting. I gave it to the AI chat, and it corrected the syntax for me. There were some missing braces and some missing brackets. It fixed them for me and provided me with a working request. I found it very accurate in resolving the issue. If I would have done it myself, as the request is very large, I would have to check each element and each brace to find out where the issue is. It really helped me, and therefore I can rely on the AI capability of Postman Enterprise. I give this review a rating of eight out of ten.

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.

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.

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.

I have been dealing with Postman Enterprise for about six to seven years.

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.

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.

I have been using Postman Enterprise for the last six months. My main use case for Postman Enterprise is to use tables for the API. A specific example of how I use tables for the API is that, for using the backend, we can make policies, and to check the API, I use Postman.

The process saves my time, so I want to check if my idea is working, and I check it directly using this. The main use case I have for Postman Enterprise is for checking if the parameters are working correctly, especially for backend APIs where we have DevOps working, and we need to monitor the actual APIs.

The best features Postman Enterprise offers are to check backend APIs for quality, which the testing team can also verify. There are other features, but they all relate to backend APIs, testing APIs, and developers can monitor them in a single system using Postman. Postman Enterprise positively impacts my organization as it saves our time, eliminating the need to check it manually.

Postman Enterprise can be improved by explaining its many features one by one to the users for efficient use since there are numerous features in Postman. They can lower the pricing because small teams cannot afford it. We are in a company that can afford it, but startups will not have the budget.

I have been working in my current field for the last one year.

Postman Enterprise is more reliable and stable than any other application, which is why I use this.

On scalability, I can rate Postman Enterprise a 9.5.

I have never used customer support because there is nothing major to use customer support for at this time, but if I do, I will let you know.

I have not used any other solution other than Postman Enterprise.

We have seen a return on investment, saving a lot of money and time, particularly time, as we have saved with this.

The pricing, setup cost, and licensing were decent. It was not too much and actually great, though buying for a team is a bit expensive, but we can afford it.

Before choosing Postman Enterprise, I evaluated other options, but none were as efficient and scalable.

My advice to others looking into using Postman Enterprise is that they must buy it because it is more efficient. I would rate this product nine out of ten.

I used Postman for testing and automatic tests. I use it as a beta tester for API interface with the main programs.

The scripting capabilities in Postman are excellent. You can implement scripts before and after, making it easy to create interfaces. We have multiple versions available. I can mark which version to use when sending calls for authorization and tokens. Depending on the version and client, I can activate everything with one button through scripting.

Postman's collaboration tools, such as version control and team workspaces, are particularly useful when working with teams of three to four people. Some team members create scripts, and updates can be made through the cloud platform.

The collaboration features are valuable for maintaining and updating projects.

There are some limitations regarding large result sets in Postman. When dealing with several hundred records, accessing all the information can be challenging. However, these limitations are less restrictive compared to Swagger, which has more severe limitations when used with web navigation.

The company purchases Postman licenses for multiple users.

Previously, we didn't use Postman but had API functionality through IIS. We implemented XML replies for SQL Server.

Postman's integration with CI/CD pipelines has impacted the continuity and deployment of our APIs. We use Postman to integrate with JIRA, collecting tasks through JIRA's commercial API. We are implementing experimental applications to read and collect information from JIRA.

Postman performs excellently for these integrations. The main challenge lies in understanding external documentation to access the API correctly, but once configured, Postman excels at collecting information.

Postman is an extremely stable program without any significant issues.

I primarily use documentation and haven't tried support or extended support when considering Postman's adaptability for both REST and SOAP APIs.

Positive

I use SwaggerHub at the client side to test and ensure API functionality. I only implement Postman in the client environment under exceptional circumstances.

Postman is easy to set up, though company policy restricts implementing solutions on local machines.

I utilize this product with AWS for REST applications. The automated testing features are available but limited by license restrictions. I primarily run repositories and work with JSON format. We have standardized all old XML versions to make implementation and future development easier.

I work as a programmer analyst for research and development. My email is marcel.cote@acceo.com.

On a scale of 1-10, I rate Postman a 10.

My main use case for Postman Enterprise is in my college projects, where we are creating the full project for our capstone project in our university. We are working in a group of four to five, and when I am working with backend technologies, sometimes the front end is not fully designed. During that time, I need to check if my backend is properly working or testing if the backend is functional. I need to test the backend dependency fully, so I use Postman Enterprise while working with backend technologies and learning with the API to ensure it is working correctly.

Postman Enterprise helps me understand how to send a request and check the responses without writing the full front end. In my experience, Postman Enterprise is very useful for testing APIs. I can use it for POST requests, where I need to add the link of the server at localhost:5000, log in, and we must use the JSON format. For instance, if there is a login model, I need to write the username and password in JSON format. When we hit the POST method and send it, it fetches the data; if the username and password are correct, it shows a login successful message. I use it for GET and POST requests as well as PUT and other types of requests. I can check if our API endpoint is working or not without needing a full front end.

Once the front end works well, we may still encounter backend errors, which we can check from the backend side with Postman Enterprise. I verify the JSON responses and ensure my API functions properly before integrating it with the front end. I test various methods multiple times, and if any issues arise, it is easy to debug from the backend side. One feature I appreciate the most is the ability to save requests. While testing various activities, we often have a login module, which we can save and modify the values or variables without rewriting the URL repeatedly, making it extremely efficient.

Postman Enterprise offers various features, including PUT, GET, POST, and DELETE operations, making it easy to interface and support multiple formats such as XML, JSON, and binary. It simplifies API testing without needing the front end, which is particularly useful at the industry and organizational levels. It is also beneficial for debugging; when working with the backend, we do not need to check every API; we can focus on one and identify issues efficiently.

Postman Enterprise saves my time significantly. I can determine which API is broken and check that specific code without sifting through the entire codebase. I concentrate on what is not working.

Postman Enterprise has positively impacted productivity in my organization. It is easier for the QA team to test APIs using Postman Enterprise.

One potential improvement for Postman Enterprise could be incorporating AI features into its advanced options. It could enhance the interface as it is good but has room for modification and updates to bring it to an advanced level.

To improve, we could integrate an AI interface that assists users who may get stuck, providing direct suggestions on how certain functionalities work.

I started using Postman Enterprise in my second or third semester, so I have been using it for the last two to three years.

Postman Enterprise is stable in my experience. All developers in my industry use Postman Enterprise for testing purposes, and it works perfectly.

Postman Enterprise is fully scalable, and I have not noticed any issues with its ability to handle growth and additional users.

I have never needed to reach out to customer support for Postman Enterprise.

I did not previously use a different solution.

My experience with pricing, setup cost, and licensing is that as a student, I utilize the free version of Postman Enterprise. At the enterprise industry level, everything is provided by the IT department.

At the enterprise industry level, everything is provided by the IT department.

Postman Enterprise saves time significantly.

My experience with pricing, setup cost, and licensing is that as a student, I utilize the free version of Postman Enterprise.

I did not evaluate any other options before choosing Postman Enterprise.

My advice for others looking into using Postman Enterprise is that if you are a backend developer or QA, you need it for testing API services to check if they are functioning correctly. Using a product Postman Enterprise will definitely enhance your experience, and I believe you will feel much better using it.

When developers add any functionality, they check everything with Postman Enterprise, which is crucial because our product is live, and we cannot make changes directly without thorough testing to avoid breaking any functionalities.

I would rate my overall experience with Postman Enterprise a nine out of ten.

I have not yet used Selenium within the last 12 months; I just completed some POCs, but not actually used it.

There are many other tools that we are working on aside from Selenium.

We use TestIM, Katalon, and those are all UI function tools, and in terms of API, we are working on Postman and Ready API.

Personally, I have been using Postman for seven or eight years plus.

Postman is the easiest tool I know, there's no challenge at all. In fact, most of the Postman testing that we do is all locally, but when I say deployment, that deployment is for cloud, and whenever we want to run it in CI/CD, it's all on Azure and AWS, so it's one of the easiest things.

Postman doesn't require much time to deploy, just a few minutes or so. This applies to almost all the tools that we're working on; Selenium is one of the most mature automation framework tools we have, so there's no issue with that.

I don't find anything difficult based on my experience, but the organization of collection, running, and assertions in the last few years have been really good for me; the environment is managed well.

Postman is one of the easiest tools; I have not seen anybody complaining because it's just one Google search away.

It's easy to navigate because tons of documentation and examples are available.

It has helped significantly since it is easy; the development team and QA team all use it, enabling us to automate almost 70% of our APIs using Postman.

I wouldn't say there are weak points or drawbacks for Postman, but there are definitely features that could be improved; for example, if you derive it from Ready API, maybe Postman can be a good contender and replicate some features such as more scripting and control over API calls.

Personally, I have been using Postman for seven or eight years plus.

The technical support for Postman is all good.

Positive

I don't have exact numbers, but since 70% of APIs are automated, you can say that a minimum of 50% time is saved when comparing manual to automation; for example, if I take 10 hours to test an API for every release, I can do it in half that time or much faster.

Postman is much cheaper than the other tools.

I am not aware of the current pricing for Postman because that's taken care of by the client; we just pay and they simply create options.

On a per-person basis, I would rate it seven to eight for pricing because whatever they are offering at that price gives huge satisfaction.

We have various projects, and not all the projects use Postman, as we use REST Assured, Ready API, and Postman in two ways: one is manual, where you feed and update the data every time, and the second is automation, where we use both manual and automation methods.

I would recommend this product to others because it's much easier, has a cheaper free version available, is widely used, and has a lot of examples and documentation available.

There are over 50 users of the free version, but for the paid version, there are five plus users.

We're talking about engineers, and that number might vary, but that's the current status I can estimate.

On a scale of one to ten, I rate Postman an eight.