Postman vs SwaggerHub comparison

"The interface and the different types of API methods you can use are the most valuable aspects of this solution."

"Postman lets you create, manage, and validate a suite of tests. It has several features to help you organize your test suite. You can also automate stuff with a lot of validations and assertions. Postman supports GraphQL, and you can do various kinds of calls."

"It is nice to have different workspaces. You have your personal workspace, and then you have a team workspace. In general, I like its UI. It is quite cool."

"With Postman you can do automation. Automation has increased efficiency by more than 30% or 40%. Because the speed has increased, it's also possible for us to do in-sprint automation testing."

"The initial setup of this solution is straightforward. Postman can be used as an extension in Google Chrome for those who do not wish to install it directly. Deployment took an hour and a half."

"The most valuable feature is the user interface because it provides a clear space for the URL, headers, body, prerequisites, and tests."

"It's easy to see different versions of responses."

"The developers put the API in a common workspace which is a nice feature. It makes things much easier and faster to start testing."

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

"It is a stable solution."

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

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

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

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

"The solution can be improved by providing detailed error logs including the line the error took place to make it easier to correct."

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

"Initially, the setup is a little bit complex"

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

"The solution has some user interface difficulties when conducting environment collections."

"The tool needs to have a reporting feature."

"Integration of the solution towards Bitbucket, BitHub, and CI pipelines is difficult."

"I live in Turkey, so for me, the value of dollar currency is high...Postman can change its pricing policy and decrease the prices for Turkey."

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

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

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

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

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

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

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

"Postman is an open-source product. It is free to download from Google."

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

"We are using its free version."

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

"The solution has a licensing fee which might be prohibitive."

"It is free."

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

"The solution has moderate pricing."

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

"The tool is cheap."