We use this solution for every API development.
Postman Enterprise
PostmanExternal reviews
External reviews are not included in the AWS star rating for the product.
Great tool to verify and test APIs
Excellent Tool for API Testing and Collaboration
User-Friendly Interface: Postman's user interface is exceptionally user-friendly. It makes it easy for me to create, manage, and run API tests without a steep learning curve. This intuitiveness significantly reduces the time it takes to get started and be productive.
Robust Testing Capabilities: Postman provides a comprehensive suite of testing tools. I appreciate the ability to create detailed test cases, run automated tests, and validate API responses with ease. It's a time-saver and ensures the reliability of our APIs.
Team Collaboration: Collaboration is seamless with Postman. The ability to share collections, collaborate on API development, and leave comments on requests fosters effective teamwork. This feature has improved communication within our development team.
Documentation Generation: The ability to generate API documentation from our collections is a standout feature. It helps us maintain well-documented APIs that are accessible to both technical and non-technical team members, making it easier to understand and use our APIs.
Integration Options: Postman integrates seamlessly with our other development tools, such as Jira and GitHub. This integration streamlines our workflow and helps us manage and track API-related tasks more efficiently.
Overall, what I like best about Postman is its combination of user-friendliness, powerful testing capabilities, collaborative features, documentation generation, and integration options. It has become an essential tool in our development process, making API testing and development much smoother and more efficient.
What I dislike about Postman is:
Learning Curve for Advanced Features: While Postman is generally user-friendly, I've found that some of the more advanced features can be challenging to master. It would be beneficial if there were more accessible resources or tutorials to help users unlock the full potential of these features.
Cost for Pro and Enterprise Plans: The pricing for the Pro and Enterprise plans can be a bit high, especially for smaller teams or individual developers. While the features they offer are valuable, it may be a barrier for some users. More flexible pricing options or a more affordable tier for small teams would be appreciated.
Performance Issues: Occasionally, I've experienced performance issues when working with very large collections or running extensive test suites. It would be great to see improvements in the platform's performance and resource optimization to handle larger workloads more smoothly.
Limited Offline Mode: Postman primarily relies on an internet connection, which can be a limitation when working in environments with unreliable or restricted internet access. An improved offline mode or the ability to cache collections for offline use would be a valuable addition.
Documentation Updates: While Postman does offer documentation, it could benefit from more frequent updates to keep pace with new features and changes in the tool. This would help users stay informed and make the most of Postman's capabilities.
In summary, my dislikes about Postman revolve around the learning curve for advanced features, the pricing structure for Pro and Enterprise plans, occasional performance issues, limited offline functionality, and the need for more up-to-date documentation. These are areas where I believe Postman could make improvements to enhance the user experience further.
Streamlining API Development: Postman simplifies the process of API development by providing a user-friendly interface to design and test APIs. This streamlining of development tasks saves me time and effort, allowing me to focus on creating robust APIs.
Effective Communication: Postman acts as a communication bridge between backend and frontend teams. It allows me to share API endpoints, request examples, and documentation in a structured and organized manner. This ensures that both teams are on the same page and reduces the chances of miscommunication.
Real-World Testing: Postman enables me to perform real-world testing of APIs by simulating various scenarios, including error and success responses. This ensures that the APIs are thoroughly tested and ready for integration into frontend applications, reducing the likelihood of unexpected issues.
Collaborative Feedback: Postman's collaboration features facilitate seamless feedback and collaboration with the frontend team. They can provide comments, suggestions, and insights directly within Postman, leading to faster issue resolution and improved API quality.
Documentation Creation: Postman's ability to generate API documentation is a significant benefit. It allows me to create comprehensive documentation that serves as a reference for the frontend team. This documentation improves the usability of the APIs and reduces the need for constant clarification.
In summary, Postman solves problems related to API development, communication, testing, collaboration, and documentation. These solutions benefit me by making API development more efficient, ensuring effective communication, enhancing testing capabilities, enabling collaborative feedback, and providing comprehensive documentation, ultimately leading to smoother backend-frontend integration.
Best App for API Testing
Best For Professionals
Indispensable tool for API testing
Postman : API Management Tool
GOOD feature like collection ,api monitering ,api managment
version control can be there
Useful For Testing API
Review
API testing via postman
A simple and easy-to-use solution for API with easy maintenance
What is our primary use case?
What is most valuable?
We are exploring code generation and how it works. We also like the test functionalities and snippets that we can use directly.
Moreover, the tool is simple and easy.
What needs improvement?
Integration should be improved with our continuation system because we use Azure DevOps separately.
For how long have I used the solution?
I have been using Postman for around two years. Initially, we used it only once, and now we use it more.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is easy to scale till now.
We are using the solution for five people.
How are customer service and support?
We get help from videos and the web.
Which solution did I use previously and why did I switch?
We have also worked with SoapUI, but we like Postman because it has automation.
Postman is a more compact tool, and it has many functionalities. In the first stage that we used, Postman, we only tested how it works. Now we are using more functionalities. With SoapUI, it's because some customers have used it to define the APIs, and then we have to interact with this environment.
But we use Postman, and we prefer Postman. Although, there are some tools from SoapUI that are good. For example, the API design, checking, and definition. If Postman has anything similar, you can check the definition of the API, and it proposes you an improvement and so on, but in the development phase, we used Postman, and we like Postman.
How was the initial setup?
The solution’s initial setup is easy. The maintenance is easy as well because we are not doing all the possible accents and because we are not doing anything to maintain.
The solution is deployed on the public cloud and on-premises in our organization. But I use it more in the cloud.
What's my experience with pricing, setup cost, and licensing?
The solution’s pricing is realistic according to our usage level. As we grow and require additional functionality beyond what we currently use, there is a higher cost while upgrading the developer plan. We want to explore features like automatic code generation and other functionalities.
We are paying only for the license for now, and it comes with a monthly subscription.
What other advice do I have?
Postman is one of the most widely used tools in the market. When you use it, it is practical and useful. You need to check whether it suits your team, project type, and work to take profit from the way Postman works. From the beginning, it is one of the three main tools you must explore if you regularly deal with APIs.
However, I am still exploring all the tools, and I don't know if I can maintain it or not. When I know all the different technologies better, I will be able to say.
Overall, I would rate the solution an eight or nine out of ten.