Postman vs SwaggerHub comparison

"The solution has a great user interface and collection of features."

"The solution is stable."

"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."

"It is a scalable solution."

"What is most valuable for me is that we can create and share collections between the team members."

"We can test APIs. We know if they are functional or throwing any errors."

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

"The scalability is good."

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

"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."

"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."

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

"The scalability is endless."

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

"We cannot see transaction times in the product."

"Postman could be improved by providing options for performance testing of APIs."

"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."

"They should integrate the solution with one of the CRM solutions."

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

"Something that could be better is the inclusion of another type of test, for example, end-to-end tests."

"Reporting can be better. If you have bigger APIs, it takes time."

"Integration should be improved with our continuation system because we use Azure DevOps separately."

"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."

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

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

"The scalability aspect of SwaggerHub can be improved. It becomes a bit unreliable when the load is increased and isn't up to par with expectations for scalability."

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

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

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

"Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account."

"The solution's price is reasonable."

"We are using the free version that is available."

"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."

"Unlike APIs, the solution does not require a license."

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

"We are currently using the free version, but we have plans to buy a license."

"The solution is open-source and free."

"The tool is cheap."

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