SwaggerHub Reviews

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.

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.

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. 

The most valuable features are the collaboration between multiple teams and the control and distribution of specifications.

SwaggerHub could be improved with better integration for tools.

I've been using SwaggerHub for six to eight months.

SwaggerHub's stability is fair.

I don't see SwaggerHub as an API gateway or API management tool - it's more like a certification for holding up your specifications and for collaboration with multiple teams. I would rate SwaggerHub eight out of ten.

We hope to use it for the design of the API and for the entry point of the documentation to help the consumers of the API in understanding the API and specifications.

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 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.

I have been using this solution for two years.

It is stable. I have noticed a downtime period only once, but I am not sure if it was down because of them or something else.

We have few APIs. We have a license that is limiting our users to 25 designers and 50 consumers. Consumers are the users who don't need full capabilities. It is working well for us, and we didn't have any problem.

They are very supportive. They try to get a lot of feedback from our side. We actually couldn't provide that much feedback. They wanted to help, and they provided hands-on sessions several times to explain what they do. They also have a lot of free webinars where you can hear the news, updates, and all kinds of stuff. They are quite good. Their documentation is also quite good.

It was quite straightforward.

It has a yearly subscription, but I am not sure.

I would recommend this solution. It is quite good and one of the best tools for open API. We might have to switch to another tool based on our investigation regarding the developer portal. Even though it has a few limitations, I am confident that it will get better. It is evolving like any other solution.

I would rate SwaggerHub a nine 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.

We use SwaggerHub to publish our APIs. We also integrate SmartBear ReadyAPI with Swagger.

We use it to manage our APIs. When we develop an API, we then integrate it with SwaggerHub. Centene is a large corporation with plenty of automation so there are various development teams across Centene who use this solution for various use cases. Normally, they publish their APIs on SwaggerHub for seamless integration with SmartBear and ReadyAPI. This allows us to perform detailed end-to-end automation testing. 

More integration and usability with the cloud microservices would be nice. Azure and GCP — there are multiple platforms we could talk about.

We have been using this solution for quite some time. I have been with my company for 4 years now and I have heard that name nearly the whole time. 

We have quite a few people using this solution, at least 70-80 people. 

The stability is good. I have yet to see any downtime. 

The scalability is endless.

On a scale from one to ten, I would give SwaggerHub a rating of seven.