Apiary vs SwaggerHub comparison

"In two years, there was one time the service was down for an hour or so."

"The feature I find most valuable is that it offers authentication and allows us to develop communication points."

"Quick and easy way to share a new API design with teams."

"I find the generation of mock services very useful, especially when demonstrating for new consumers."

"Git integration"

"I do like the overall performance of the solution."

"This solution has allowed us to standardize API definitions and bring consistency into our shared components, reducing the effort and cost of using functionality across domains within the organization, with Apiary being crucial to our good API strategy."

"Quick and easy way to share a new API design with teams."

"SwaggerHub plays a crucial role in order to bring teams and automate things faster and also reduce the man-hours and increase the work efficiency."

"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 scalability is endless."

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

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

"Since I started using SwaggerHub, it has had a positive impact on our organization due to better collaboration between developers and the quality assurance team, and it has reduced errors because of its automated validation."

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

"SwaggerHub is helping with team collaboration, as all the people now know the link, they just go there and get the information they need, and it is really a documentation tool for sharing documentation information about the API we support."

"I would like an integrated option to download a Swagger version of the definition."

"Better Swagger support."

"I would like an integrated option to download a Swagger version of the definition."

"The Oracle release cycle is very bad because the patches only update once a year."

"Validation messages could be a bit clearer."

"I don't think this solution is very stable so we try to manage stability from our side."

"Swagger (OpenAPI Specification) and Blueprint Support"

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

"SwaggerHub can be improved since the API testing features are limited compared to Postman, and it is somewhat expensive for small teams as paid plans cost a lot."

"The customization and doc formatting options for documentation pages are restricted in SwaggerHub."

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

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

"One of the most difficult things about SwaggerHub is the user interface and its usability, as it can feel quite complex and require too many clicks for simple actions."

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

"There is a free subscription option to start and try the service."

"It is easy to get started with personal (free) accounts, but a subscription is required for additional features."

"The tool is cheap."

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