SwaggerHub Reviews and Ratings

Rating: 8 out of 10

Score

8 out of 10

Community insights

TrustRadius Insights for SwaggerHub are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Easier API Design: Users have consistently found that designing APIs with the tool is made easier due to its ability to define API contracts using simple YAML file definitions. This simplifies and streamlines the design process, resulting in more efficient development.

Hassle-free Documentation: Many reviewers appreciate how the tool eliminates the hassle of documenting REST service/APIs. Its auto-generated code capability automates the documentation process, saving time and effort for users.

Seamless Integration: The tool seamlessly integrates with popular repositories like Bitbucket and AWS API Gateway, making it versatile for streamlining development and sharing APIs across multiple departments and developers. This integration enhances collaboration and efficiency within organizations.

Reviews

6 Reviews

SwaggerHub - Easy to use API designer

Rating: 8 out of 10

Incentivized

April 28, 2022

Use Cases and Deployment Scope

SwaggerHub is used in our organization to document our APIs and build out the models for them. This helps our entire team, by keeping them updated and know which resources we have and what to expect back from them. My favorite problem that this addresses is our testing. We can easily import the API into ReadyAPI and build out our tests directly from that, without having to build out an API at that step.

Pros

Designing APIs
Documenting APIs
Helps all devs stay up to date

Cons

I have been told that the models take quite some time to build out
Would love to see some more capability on import, as far as adding variables into endpoints

Likelihood to Recommend

ReadyAPI and SwaggerHub are a match made in heaven. Being able to so easily import the API directly into ReadyAPI and then being able to generate a test suite from the API is my favorite part of these softwares.

We have rather large services so building out the API can take some time.

Lisa Krol

Quality Assurance Engineer at Phase Change Software (11-50 employees)

Vetted Review

3 years of experience

One of the best tools for API management

Rating: 8 out of 10

Incentivized

September 29, 2021

Use Cases and Deployment Scope

We use SwaggerHub across the organization to design API endpoint and documentation for our microservices architecture. It's works well in collaborating more easily on developing API in our team. It also can be used to test our API endpoint which makes an integration test easier when we deploy changes to the API. And it is also user-friendly that any other developer/QA can easily understand the service contract and error handling structure etc when testing in it.

Pros

It is easy to share or use together for a collaborative team project.
Make better for the organization when it comes to documentation of API.
User-friendly to understand for non-developer to their needs.

Cons

The user interface could be more improved to sustain with other similar tools in the market.
Beneficial if we have better integration with third party softwares.
Nice to have ability to download the documentation in usable formats.

Likelihood to Recommend

We use SwaggerHub to design API endpoint and documentation for our microservices architecture system. It's working really great for us to be able to collaborate more easily on developing API in our team. It also can test our API endpoint which makes an integration test easier when we deploy changes to the API, especially for non-developers/QA.

Verified User

Consultant in Information Technology (10,001+ employees)

Vetted Review

3 years of experience

The best way to document your APIs & share APIs

Rating: 10 out of 10

Incentivized

August 10, 2021

Use Cases and Deployment Scope

Ours is a small startup; our product is still under development. We use SwaggerHub to document all our APIs. Try & execute the APIs from the console instead of using CURL or something. Always helps in checking our backend APIS calls and see how the APIs are functioning. A very handy tool.

Pros

The UI & easy of integration with bitbucket & other repositories.
It is easy to document your API using Swagger 2.0 or Open API specification.
You can use the "Try It Out" button and invoke API, authenticate and execute the APIs.
It also has ways to integrate AWS API gateway, Bitbucket, Github & other tools.
Helps streamline the development especially sharing APIs across multiple departments & developers.

Cons

It doesn't have a way to write test cases like postman has.
It does't have environments to configure different ENV variables like Postman has.
And may be having a client app for Swagger would be nice to have.

Likelihood to Recommend

It is always best to write your API specification first, using Open API 3 specification or SwaggerHub 2.0.

A clearly defined API definition will help streamline your development process & also help your QA understand all the different use cases. APIs can be individually tested with different models directly inside the SwaggerHub UI. If you plan to write test cases, SwaggerHub may not be of much help, but it does a great job at what it has. I definitely recommend SwaggerHub for API documentation, very to easy to use UI, and sharing your docs public. <span style="letter-spacing: -0.6px; word-spacing: -0.75px;">You can use the "Try It Out Button" to invoke API and authenticate and execute the APIs.</span><div>

</div>

Verified User

Engineer in Engineering (1-10 employees)

Vetted Review

4 years of experience

Design First approach to microservice APIs

Rating: 10 out of 10

Incentivized

June 10, 2021

Use Cases and Deployment Scope

We use SwaggerHub to design our micro service APIs prior to development starting. Our Solution Architect's and Technical Business Analysts are able to collaborate and define the APIs based off user stories. Our Swagger API definitions are a core part of our customer facing documentation, so we put a lot of effort into that design phase to make sure we have consistent naming standards and have great descriptions and examples for each endpoint. Our customers can read our API documentation to understand what each API does, and they can also import the Swagger definitions and code stubs into their IDEs to give them a head start on the development process.

Pros

Treating the design as documentation ensures that we have consistent and well defined APIs
API consumers can export the swagger definition or code stubs to use within their development environment
We can iterate through multiple versions of a definition privately before making a version publicly available

Cons

Under the Swagger 2.0 standards you can only provide one example for each endpoint. A complex /search endpoint is a great use case for having multiple examples.
Not able to define events that will be created or consumed by an API.

Likelihood to Recommend

SwaggerHub is perfectly suited for defining an API before development starts.

Verified User

Manager in Information Technology (51-200 employees)

Vetted Review

3 years of experience

SwaggerHub's Swag

Rating: 10 out of 10

Incentivized

March 9, 2021

Use Cases and Deployment Scope

SwaggerHub and its components are used in the process of defining APIs during the design and development of the micro-services application. In the API first approach, defining API contracts clearly is paramount, and to a large degree, success depends on this. SwaggerHub aids this process through its Swagger UI and it is used extensively in our projects.

Pros

Helps in defining the API contracts by simple YAML file definitions
REST service/API documentation is hassle free
Auto-generated code capability helps in reducing the efforts to define clients

Cons

Swagger Editor can be bit more user friendly by providing the means to persist different projects as part of user profiles
Swagger UI's testing capability or means to test APIs can be improved
Swagger UI clients can be added as part of Spring ecosystem

Likelihood to Recommend

SwaggerHub can be used to define API contracts and share with different teams that consume the services. These contracts will serve the API-friendly approach well. Code generation can be used for quick consumption of services. Libraries are available that generate Swagger UI screens based on the APIs defined in a given application. It's not good for legacy SOAP services, etc.

Muralidharan Balanandan

Cloud Engineer in Information Technology at NU Technology Inc (51-200 employees)

Vetted Review

2 years of experience

View profile

SwaggerHub is the best tool to manage your APIs

Rating: 7 out of 10

Incentivized

April 17, 2019

Use Cases and Deployment Scope

Pros

We can make comprehensive documentation of our API.
Easy to share or use together for a collaborative project.
Start at a fairly reasonable price.

Cons

Would be good to have better integration with third-party software e.g. AWS Lambda, Postman, etc. for automatic testing.
I would like to see the documentation to be able to convert to another format e.g. MD file, wiki pages, etc.
We are using RESTful APIs from SOAP, so would be good if we could transform SOAP designed API to RESTful API.

Likelihood to Recommend

If you have a huge amount of API endpoint and a lot of team members, SwaggerHub will be really good for you and your team. Communication about changes will be much easier and everyone will comply with the changes without any further communication just by reading the documentation. If you are just starting to make an API based application on your own, you might not need it since it could be overkill.

Verified User

Engineer in Information Technology (11-50 employees)

Vetted Review

1 year of experience

Loading Reviews List....

Home
,
API Management
,
SwaggerHub
,
Reviews and Ratings

The best way to document your APIs & share APIs

Rating: 10 out of 10

Incentivized

August 10, 2021

Use Cases and Deployment Scope

Pros

The UI & easy of integration with bitbucket & other repositories.
It is easy to document your API using Swagger 2.0 or Open API specification.
You can use the "Try It Out" button and invoke API, authenticate and execute the APIs.
It also has ways to integrate AWS API gateway, Bitbucket, Github & other tools.
Helps streamline the development especially sharing APIs across multiple departments & developers.

Cons

It doesn't have a way to write test cases like postman has.
It does't have environments to configure different ENV variables like Postman has.
And may be having a client app for Swagger would be nice to have.

Likelihood to Recommend

It is always best to write your API specification first, using Open API 3 specification or SwaggerHub 2.0.

</div>

Verified User

Engineer in Engineering (1-10 employees)

Vetted Review

4 years of experience