SwaggerHub Reviews

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.

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.

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.

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.

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

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.

The tool's most valuable feature is licensing. 

We have to use additional tools to test APIs.