The tool's most valuable feature is licensing.

SwaggerHub for AWS
SmartBear SoftwareReviews from AWS customer
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
The tool's pricing is cheap and deployment is easy
What is most valuable?
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.
Has good stability and helps in testing APIs efficiently
What is our primary use case?
We use the solution to develop and test the APIs.
What needs improvement?
The solution could be more intuitive compared to Postman. They should improve this particular area.
For how long have I used the solution?
I have been using the solution for a few months.
What do I think about the stability of the solution?
It is a stable solution. I rate its stability an eight out of ten.
What do I think about the scalability of the solution?
We have around 30+ solution users as our customers.
Which solution did I use previously and why did I switch?
We used SoapUI earlier.
How was the initial setup?
The solution's initial setup process is more complicated than one of its competitors. The deployment involves installing it on the system and setting it up. It takes around an hour to complete and requires one executive to deploy and maintain it.
What about the implementation team?
We implemented the solution in-house.
What other advice do I have?
I recommend the solution to others and rate it an eight out of ten.
API designing using swaggerhub.
Some of the features which I like about swagger are :
* Instant output: You can instantly see the script's current output at any time.
* Flexible: You can also visually edit the output doc apart from the code.
* Codebase generation: You can generate a vast volume of code and add it to your API.
* Examples: You can add examples for successful runs or errors.
* Collaboration: You can collaborate with members of your team and members from other teams too.
* Lack of integration: Although SwaggerHub gives you connectors for integration, it doesn't have enough integration to cover all APIs like SVN or Jira.
Swaggerhub review
Make your API designing & testing simpler and faster with SwaggerHub
1. API designing and development
2. Testing and debugging issues in a seamless manner
3. Single platform to monitor all your API's
4. Creating API Documentation
Best tool for API designing and testing
The error response or message show are of excellent use, the second thing I liked about it is that I can create a team and share the whole collection at a single click and the UI and UX is also very simple and good, with all the same controller in a single format.
The UI make it really simple when working with the testing, as when the number of APIs increases, it becomes complicated to manage them, but the UI of SwaggerHub make it so much easier