SwaggerHub Reviews

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.

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.