We performed a comparison between SwaggerHub and webMethods.io Integration based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I rate the solution's stability a ten out of ten."
"It is a stable solution."
"The scalability is endless."
"The tool's most valuable feature is licensing."
"Code generation is one of the important features of SwaggerHub. We design our API, and we can generate a very rich codebase and add to it. The code generation feature is very valuable."
"The product's initial setup phase was easy and not at all difficult."
"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."
"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."
"I like the tool's scalability."
"The solution is scalable."
"The connectivity that the tool provides, along with the functionalities needed for our company's business, are some of the beneficial aspects of the product."
"Our use case is for integration factory for SAP. It is mostly for SAP integration."
"It's easy to construct new interfaces like apps and client portals."
"There's hardware, software and application integration, providing hosting flexibility."
"Oracle's self-service capabilities, of which we make extensive use, is the most valuable feature."
"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 could be more intuitive compared to one of its competitors."
"It has limited functionality...Unfortunately, some of its features are not what we need."
"SwaggerHub lacks in terms of integrations. They have APIs integrated, and they also have some connectors, but they don't have integration with many of the things that we use. For example, for connecting with SVN, we had to implement external scripts. So, they should work on the integration because currently, we have to work on the integration with our DevOps, continuous delivery, or continuous deployment. It would be great if these integrations are built-in. Mainly, we would like it to integrate with SVN and Jira."
"SwaggerHub's UI needs to be improved as it looks very old school."
"SwaggerHub could be improved with better integration for tools."
"We have to use additional tools to test APIs."
"More integration and usability with the cloud microservices would be nice"
"The solution's release management feature could be better."
"It is difficult to maintain."
"Rules engine processes and BPM processes should be improved."
"The product's stability is an area of concern where improvements are required."
"webMethods.io Integration's installation is complex. It should also improve integration and connectors."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
"I am not satisfied with the solution because it takes too much effort to migrate and add new information. The migration could be easier."
SwaggerHub is ranked 13th in API Management with 8 reviews while webMethods.io Integration is ranked 29th in API Management with 7 reviews. SwaggerHub is rated 7.8, while webMethods.io Integration is rated 7.8. The top reviewer of SwaggerHub writes "An easy-to-use solution for the entry point of API documentation that needs to introduce some regulatory controls". On the other hand, the top reviewer of webMethods.io Integration writes "Though the tool provides great connectivity functionality, it needs to be made more stable". SwaggerHub is most compared with Microsoft Azure API Management, Apigee, MuleSoft Anypoint API Manager, Amazon API Gateway and RapidAPI, whereas webMethods.io Integration is most compared with webMethods Integration Server, SAP Cloud Platform, Apigee, Microsoft Azure API Management and Microsoft Azure Logic Apps. See our SwaggerHub vs. webMethods.io Integration report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
