Postman vs SwaggerHub comparison

"Postman helps to write pre-request scripts and make a collection out of each request. You don’t have to spend time writing or copying the requests. The solution lets you integrate multiple environments and their features. Either the tool’s pro or premium version lets you do the merge and pull request for the Git directly."

"Postman is easy to use and enables us to test all possible API testing scenarios."

"The environment variables are a valuable feature because I can easily switch them and see all the developments in different cycles and stages."

"It is simple, easy to use and a good tool."

"The most valuable features of the solution are that it is easy to use and user-friendly."

"It is stable and reliable."

"No coding required."

"We can also submit requests multiple times and it allows us to capture the response each time by using utility scripts."

"The scalability is endless."

"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."

"It is quite a useful tool. It is quite good with the validation of the spec. It works quite well in terms of errors and conformity to the OpenAPI standard. It is better than Visual Studio Code in terms of editing."

"It is a stable solution."

"You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs."

"I rate the solution's stability a ten out of ten."

"The product's initial setup phase was easy and not at all difficult."

"The tool's most valuable feature is licensing."

"Testing API is pretty straightforward in Postman, but it falls short when testing web services. For example, when we test web services, there is a visual component that we can import in SoapUI but not in Postman."

"We have previously used Tosca which allowed us to verify information using authentications. It would be useful if this was also possible using Postman. In a future release, Postman should connect to DB."

"Multi-part requests should be handled in the octet-stream."

"One of the features that is missing in Postman is reporting; it's very basic."

"Should have a more improved easy-to-use interface."

"I would like that if you click on one of the fields you should be able to see the entire row of fields, names, and values."

"Postman is a bit more of a complex tool, making it an area where improvements can be made."

"To get this email reporting function, we have to integrate Postman with Newman. If the two are not integrated, we won't be getting all these things in one group."

"It has limited functionality...Unfortunately, some of its features are not what we need."

"The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism. They support some comments, but it is really hard to manage those comments. We would like to use the full request. Therefore, we are now looking to integrate with repositories. It has integration with Bitbucket and GitHub, but we have some internal constraints, and we need to move some of the repositories to GitHub. Our source code is on-premise in Bitbucket, and it was a bit of a problem for us to integrate. Now we are transitioning our repositories to GitHub, and hopefully, we can enable the integration. This will probably solve the problem with the review and approval. Its customization should also be improved. There are limitations around the support for the developer portal. There should be more customization options for the website that you can use as a developer portal. Currently, it has only Swagger UI with minimal customization. You cannot actually add additional pages and documentation for explaining concepts and general things. That's why we have started to look around to see what other tools are doing. They should also allow tagging on the API. We would like to add some tagging on the API to reflect certain things. Currently, any metadata that you would like to have has to be a part of the spec. You cannot do anything else. It should also have support for Open API 3.1, which was released at the beginning of the year. It would be great to be able to switch to that."

"SwaggerHub could be improved with better integration for tools."

"It could be more intuitive compared to one of its competitors."

"SwaggerHub's UI needs to be improved as it looks very old school."

"More integration and usability with the cloud microservices would be nice"

"We have to use additional tools to test APIs."

"Its price is moderate as compared to other competitors. The version that we are using is not open source, so it is not free."

"We are using its free version."

"We do not pay any money for Postman."

"It is free."

"I rate the product's price a nine or ten on a scale of one to ten, where one is cheap, and ten is very expensive. Postman is an expensive tool for Turkey."

"I use the tool's free version."

"The solution is free for individuals, but for companies that use it across the organization, you have to pay per user."

"This tool is open-source and free to download and use."

"It has a yearly subscription, but I am not sure."

"The tool is cheap."