Centralized API collaboration has improved cross-team workflows but still needs simpler usability
What is our primary use case?
My main use case for SwaggerHub is designing, documenting, and managing API documentation for client-facing applications.
Every time we need to update any documentation regarding APIs or add new endpoints, edit them, or remove them, we have it automated in such a way that the documentation is automatically generated for SwaggerHub.
We also use SwaggerHub in scenarios where several API endpoints need to be exposed to external customers, and in these cases, it acts as a centralized documentation and testing portal for them.
What is most valuable?
The best feature that SwaggerHub offers is the collaboration capability that helps us the most across all of our teams, as we have a single API infrastructure but several teams working in different areas of these APIs. Testing and documenting collaboration is key with SwaggerHub.
SwaggerHub positively impacts my organization by helping a lot with cross-communication between teams whenever they need to work on the API. If we need to create new endpoints, remove them, edit them, or whatever, collaboration across teams is much easier since they all use one central source of truth, which is SwaggerHub, and it is automatically updated with our automations. It also helps our QA teams know that whenever they need to test something with SwaggerHub, they always have a source of truth available that represents the latest status of the API endpoints.
What needs improvement?
One of the most difficult things about SwaggerHub is the user interface and its usability, as it can feel quite complex and require too many clicks for simple actions. Also, when managing big API ecosystems, it can feel quite slow. Lastly, pricing for small teams can be quite pricey.
Sharing options could also be improved, along with integration with cloud services, for example.
For how long have I used the solution?
I have been using SwaggerHub for almost eight years now.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
SwaggerHub's scalability is quite good, even though it has its performance issues.
How are customer service and support?
Customer support can be a bit slow sometimes, but overall, it is good enough.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I evaluated Postman before.
I did not evaluate other options besides Postman.
How was the initial setup?
The pricing, since it is subscription-based, is easy to set up, but it is quite pricey. We felt that when our team grew, it became easier to afford the cost, but at the beginning, it was quite expensive.
What about the implementation team?
We do not have a business relationship with this vendor other than being a customer.
What was our ROI?
I do not have metrics, but the return basically comes in the form of time saved and improved collaboration, which translates into time saved as well. It basically reduces miscommunication across teams and speeds up development cycles.
Using SwaggerHub has a high cost, but if your company is big enough and can afford it, it will see a return on investment quite early since it helps development teams and QA and DevOps, for example, focus on development and deployment rather than on documentation.
What's my experience with pricing, setup cost, and licensing?
One of the most difficult things about SwaggerHub is the user interface and its usability, as it can feel quite complex and require too many clicks for simple actions. Also, when managing big API ecosystems, it can feel quite slow. Lastly, pricing for small teams can be quite pricey.
Which other solutions did I evaluate?
I evaluated Postman before.
I did not evaluate other options besides Postman.
What other advice do I have?
I do not use any specific tools or integrations with SwaggerHub to make collaboration smoother.
SwaggerHub reduces errors for sure since documentation generation is automatic, so there is no human error. Speed is also increased since we do not have to spend time manually documenting these API endpoints; SwaggerHub takes care of it.
My overall review rating for SwaggerHub is 7.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Solid platform for API lifecycle management with strong governance features
What do you like best about the product?
The best part is how clean and developer-friendly the UI is. Designing APIs using OpenAPI spec is smooth, and the branching/version control feels like Git but made for API documentation. It really helps keep everything consistent across teams.
What do you dislike about the product?
The ability to enforce API design standards using style guides is a huge plus. Our team uses it to maintain uniformity across services. Integrations with GitHub and contract testing tools like PactFlow make CI/CD workflows much more reliable
What problems is the product solving and how is that benefiting you?
API Hub helps our teams standardize and centralize API design and documentation. It eliminates inconsistencies across services by enforcing design rules and making collaboration seamless. We no longer waste time managing multiple Swagger files or worrying about breaking changes in APIs. It’s also improved our DevOps efficiency by integrating contract testing early in the pipeline.
A stable solution solution with human-readable notation but doesn't define contract
What is our primary use case?
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.
What is most valuable?
You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs.
What needs improvement?
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.
For how long have I used the solution?
I have been using SwaggerHub as an implementor since 2017.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How was the initial setup?
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.
What other advice do I have?
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 tool's pricing is cheap and deployment is easy
What is most valuable?
The tool's most valuable feature is licensing.
What needs improvement?
We have to use additional tools to test APIs.
For how long have I used the solution?
I have been using the product for four years.
What do I think about the scalability of the solution?
My company has four to five users.
How are customer service and support?
We haven't contacted support yet.
How was the initial setup?
SwaggerHub's deployment is easy.
What's my experience with pricing, setup cost, and licensing?
What other advice do I have?
I rate SwaggerHub a seven out of ten.
An easy-to-use solution for the entry point of API documentation that needs to introduce some regulatory controls
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
I am a technical person, so I don't know about the cost, and it's hard to compare.
What other advice do I have?
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.
Great documentation tool for building an API
What do you like best about the product?
It makes it easy to create API documentation in a user interface so you can visually see what it will look like when generated. It also allows for easily setting standards for the data that generates the documentation fairly easily.
What do you dislike about the product?
The cost. It seems quite a bit over priced but does make things quite a bit easier to maintain and distribute your API documentation. The management of projects is also a bit confusing at first - grouping would help a lot.
What problems is the product solving and how is that benefiting you?
Swagger Hub allows my software development team to easily document APIs we build and maintain them over time as things get added or changed. It standardizes how to document all APIs.
Great software for generating API documentation software
What do you like best about the product?
Upsides of swagger hub would be the ease of use and generating easy API docs using open api specification, and the user interface is easy to understand for non-technical peeps as well.
What do you dislike about the product?
Sometimes the API definitions are not proper in the Auto-generated Swagger UI documentation, that's just a minor con, nothing too major.
it might happen due to different data types.
also linux terminal client can sometimes be hard to install.
What problems is the product solving and how is that benefiting you?
It has made API documentation easy for us,
our APIs can now be successfully and easily read and understood by engineers and computers, so these will be some of the core benefits.
Ease in sharing api specs and documentation within team
What do you like best about the product?
Ease in sharing api specs and documentation within team.
It shows what the input format and output format and the documentation.
What do you dislike about the product?
The framework is quite complex to understand the inner working.
What problems is the product solving and how is that benefiting you?
I am able to integrate swagger with GitLab and use the web portral to unit test api on the go.
Good but requires additional steps
What do you like best about the product?
Standard Output to HTML and JSON format.
What do you dislike about the product?
Requires additional work to define the structure of the response and payload.
What problems is the product solving and how is that benefiting you?
Developing SDK documentation or API endpoints was easier to develop and required less oversite to develop as the docs were generated from comments in the code.
swagger hug review
What do you like best about the product?
- the ease in which I can lay out the api's and the ability to test them on the UI itself
What do you dislike about the product?
- there needs to be better ux
- needs more penetration in the open source community
What problems is the product solving and how is that benefiting you?
- my project has a list of api's for development and consumption
- as a backend developer, its easy to lay out the api's at a single point using swagger
- it benefits the entire team as API discussions can be made easier if you can share the entire layout with everyone
