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.
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.
Which deployment model are you using for this solution?
Simplifies API design and development for developers
What is our primary use case?
SwaggerHub securely saves API calls, thereby ensuring the confidentiality of secrets. Additionally, it facilitates the validation of APIs, making them safer to use on the server.
How has it helped my organization?
SwaggerHub has significantly changed its management capabilities. It offers a seamless experience for loading APIs.
What is most valuable?
Design and execution is an important thing. SwaggerHub is maintained and developed collaboratively by both the DevOps team and developers. Through SwaggerHub, API calls are documented, allowing for clear restrictions at both the method and request levels. This flexibility facilitates the creation of robust APIs.
What needs improvement?
Compared with tools like Postman and SoapUI, it offers similar functionality but is a licensed platform. It provides features for building and managing APIs, including advanced capabilities like designing endpoints and generating documentation. Unlike Postman and SoapUI, which primarily focus on testing APIs, SwaggerHub allows for comprehensive API design and collaboration. It enables users to create, organize, and share API definitions efficiently. SwaggerHub essentially empowers developers to design, document, and maintain APIs seamlessly.
What do I think about the stability of the solution?
The product is stable.
What other advice do I have?
SwaggerHub simplifies API development for developers by providing a platform where they can efficiently create APIs without manually creating JSON or visual files. Developers can streamline the process of developing APIs and generating requests.
SwaggerHub is a platform used for API design and management. Postman serves as a tool for creating and testing API requests. While Postman offers capabilities for scripting and automation, SwaggerHub focuses on defining APIs using the OpenAPI Specification, facilitating collaboration, and generating documentation automatically. While there may be ways to integrate Postman scripts into other testing tools like JMeter, such integration would typically require manual effort and customization.
Overall, I rate the solution an eight out of ten.
An easy-to-use and user-friendly tool
What is our primary use case?
The company I work for purchased SwaggerHub with the intent to use it for a certain period of time.
I use SwaggerHub in my company for testing purposes, especially testing the APIs.
What is most valuable?
The best feature of the product is that it is very easy to use. With SwaggerHub, users need not work a lot and insert tokens all the time as they do in Postman, which is obviously a big tool compared to SwaggerHub, which offers a lot of advantages. SwaggerHub is an easier tool to use than Postman.
What needs improvement?
SwaggerHub's UI needs to be improved as it looks very old school. SwaggerHub's UI should be similar to that of Postman, which offers very attractive colors. Apart from the UI, every other function is good in SwaggerHub.
For how long have I used the solution?
I have been using SwaggerHub for about six months. My company is a customer of the product.
What do I think about the stability of the solution?
I did not encounter any stability-related issues with the product.
What do I think about the scalability of the solution?
In my company, three QAs who work on a specific project use SwaggerHub.
How was the initial setup?
The product's initial setup phase was easy and not at all difficult.
The solution is deployed on an on-premises model.
Which other solutions did I evaluate?
My company chose SwaggerHub or other products because of the ease of use it provides to its users.
What other advice do I have?
I recommend SwaggerHub to those who plan to use it since it is an easy-to-use and easy-to-understand tool. Though Postman is a good tool, SwaggerHub is a good tool that is easy to understand. It takes only one or two days to understand how SwaggerHub works.
SwaggerHub is an easy-to-use and user-friendly tool that even a layperson can easily understand and use.
I rate the overall product an eight out of ten.
Which deployment model are you using for this solution?
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.
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