I started using SwaggerHub in its previous version, SmartMiner, with a tool called SoapUI. I used it to create mock web services to test web services and create test scripts and mock APIs. 

This usage began in 2009 or 2010. Later, I adopted SwaggerHub as the platform evolved into Swagger and now OpenAPI, to create APIs.

One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization. It serves as a central hub for API design, development, adoption, and management. I can create different teams within an organization and expose these APIs to other parts of the organization. SwaggerHub facilitates enterprise-wide governance and standardization in API adoption.

Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account. The scalability also needs enhancement, as it becomes flaky under increased load. 

Additionally, the versioning management could be improved to be on par with source code management tools.

I have been using SwaggerHub since its version as SmartMiner's SoapUI, which began around 2009 or 2010.

When load testing and stress testing SwaggerHub, it becomes a bit slow to react under extreme conditions. However, overall, it is stable for the most part and has improved over time.

The scalability aspect of SwaggerHub can be improved. It becomes a bit unreliable when the load is increased and isn't up to par with expectations for scalability.

The support from SwaggerHub is decent yet not the best. The response time needs improvement as it takes a while to receive a response.

Negative

Previously, I used SmartMiner with a tool called SoapUI before transitioning to SwaggerHub.

The initial setup for SwaggerHub is straightforward and allows setting up a basic API quickly, within 15 to 30 minutes.

Regarding pricing, while I do not have specifics for SwaggerHub, I recall licensing costs for SoapUI being around $600 to $700.

For newcomers, it is advisable to start small. Have one team use SwaggerHub initially, and then expand as needed. If you have existing APIs, begin by using SwaggerHub to test and standardize them. For new developments, adopting an API-first design is beneficial. 

I rate SwaggerHub as eight out of ten. It has grown significantly over the years.

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.

You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs.

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.

I have been using SwaggerHub as an implementor since 2017. 

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.

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.

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.

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.

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.

SwaggerHub has significantly changed its management capabilities. It offers a seamless experience for loading APIs.

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.

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.

The product is stable.

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.

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.

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.

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.

I have been using SwaggerHub for about six months. My company is a customer of the product.

I did not encounter any stability-related issues with the product.

In my company, three QAs who work on a specific project use SwaggerHub.

The product's initial setup phase was easy and not at all difficult.

The solution is deployed on an on-premises model.

My company chose SwaggerHub or other products because of the ease of use it provides to its users.

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.

The tool's most valuable feature is licensing. 

We have to use additional tools to test APIs. 

I have been using the product for four years. 

My company has four to five users. 

We haven't contacted support yet. 

SwaggerHub's deployment is easy. 

The tool is cheap. 

I rate SwaggerHub a seven out of ten. 

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.

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.

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.

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.

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.

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.

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.

Positive

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.

I am a technical person, so I don't know about the cost, and it's hard to compare.

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.

We use the solution to develop and test the APIs.

The solution could be more intuitive compared to Postman. They should improve this particular area.

I have been using the solution for a few months.

It is a stable solution. I rate its stability an eight out of ten.

We have around 30+ solution users as our customers.

We used SoapUI earlier.

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.

We implemented the solution in-house.

I recommend the solution to others and rate it an eight out of ten.