When you want to define an API with your customers using SwaggerHub, you first interact with them to understand their requirements. Then, you proceed to build the API definition. This involves creating endpoints, schemas, paths, operations, error codes, and more. Once you've agreed on the API definition, you can generate client code in any desired language or even generate a server-side implementation.
SwaggerHub for AWS
SmartBear SoftwareExternal reviews
External reviews are not included in the AWS star rating for the product.
Solid platform for API lifecycle management with strong governance features
A stable solution solution with human-readable notation but doesn't define contract
What is our primary use case?
What is most valuable?
You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs.
What needs improvement?
I noticed that the editor on SwaggerHub, like Gabbiti, is graphical in nature. With this mind map interface, one can easily define endpoints and paths.
The solution is lacking behind because it not only define the contract. It define and use one-time policies.
For how long have I used the solution?
I have been using SwaggerHub as an implementor since 2017.
What do I think about the stability of the solution?
Having multiple versions online simultaneously is a common feature in software development, allowing teams to work on different iterations concurrently. However, if it led to confusion in copying and pasting contents that needs to be adressed.
I rate the solution’s stability an eight out of ten.
What do I think about the scalability of the solution?
The solution is scalable enough. However, it depends on the project when you need it. We are searching for an API gateway, and the API gateway often has also integrated such an API designer tool.
How was the initial setup?
The initial setup is easy. It is a software service and it deployment is matter of minutes or maybe an hour.
I rate the initial setup an eight out of ten, where one is difficult and ten is easy.
What other advice do I have?
It was great to show them how you write the API contract in a textual form, and then see the graphical representation of the contract, the networks, and the components. This was a very good interaction with business consultants and for business requirements engineering.
It is easy to use, and access. It supports the main versions of of OS X-ray. it's a Swiss knife.
Overall, I rate the solution a seven out of ten.
The tool's pricing is cheap and deployment is easy
What is most valuable?
The tool's most valuable feature is licensing.
What needs improvement?
We have to use additional tools to test APIs.
For how long have I used the solution?
I have been using the product for four years.
What do I think about the scalability of the solution?
My company has four to five users.
How are customer service and support?
We haven't contacted support yet.
How was the initial setup?
SwaggerHub's deployment is easy.
What's my experience with pricing, setup cost, and licensing?
The tool is cheap.
What other advice do I have?
I rate SwaggerHub a seven out of ten.
An easy-to-use solution for the entry point of API documentation that needs to introduce some regulatory controls
What is our primary use case?
We are using the software as a service for SwaggerHub.
We use it as an entry point for API documentation.
It has other features, but we don't use much of it.
What is most valuable?
SwaggerHub was convenient during my initial time because it was very easy to use. Unfortunately, some of its features are not what we need. We wanted somewhere to put our OpenAPI documentation so it's easily accessible. It's about the simplicity of the thing. I wish to use more features, but we found workarounds and now have a different custom workflow.
What needs improvement?
We want some regulatory control to understand who is reading our documentation in the space where we are active. It would be interesting to see who is looking for our API documentation, so that would be one way to understand the users. If it supports public API documentation, it's public. You never know who is likely to use it.
There are other smaller things like tagging APIs and various other details. The workflow for editing to offer OpenAPI is not as rich as we would like, so we did the editing with other tools. Additionally, you cannot include additional pages explaining certain workflows you can do with the API. These additional content pages would enhance the OpenAPI specification for the API. So these things are not significant, but they can make a difference when you don't have them.
For how long have I used the solution?
I have been using SwaggerHub as a customer for five years, considering it was before the pandemic. We are using the cloud deployment model, so it is the latest version of the solution. We use the application as consumers.
What do I think about the stability of the solution?
I think I have seen a stability issue only once in all these years since I don't use it each and every day or all day long.
I rate the solution's stability a ten out of ten.
What do I think about the scalability of the solution?
We have over 100 to 200 users using this solution, comprising software developers, engineers, producers, and consumers of the APIs. These APIs are for developers of various groups for interactions.
We have a very limited API, and it is working well. They do not have scalability problems.
Based on that, I rate the solution's scalability a nine out of ten.
How are customer service and support?
We had a few conversations with customer support, mainly on how it can be integrated into the development workflow, and discussed missing features. They were very helpful. I rate the support a ten out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
Since it's a cloud-based product, we access it via the browser. It's a cloud-based deployment that gets managed, so we don't care much about it. We don't have any concerns or complaints regarding deployment.
What's my experience with pricing, setup cost, and licensing?
I am a technical person, so I don't know about the cost, and it's hard to compare.
What other advice do I have?
We don't require any maintenance. It is a cloud-based deployment. They manage completely. We don't care about this.
It has limited functionality, but the features can be useful and simple if anyone understands them, especially given the simplicity of the solution.
There is room for improvement in terms of its features.
Overall, I rate the solution a seven out of ten.
Great documentation tool for building an API
Great software for generating API documentation software
it might happen due to different data types.
also linux terminal client can sometimes be hard to install.
our APIs can now be successfully and easily read and understood by engineers and computers, so these will be some of the core benefits.
Ease in sharing api specs and documentation within team
It shows what the input format and output format and the documentation.
Good but requires additional steps
swagger hug review
- needs more penetration in the open source community
- as a backend developer, its easy to lay out the api's at a single point using swagger
- it benefits the entire team as API discussions can be made easier if you can share the entire layout with everyone