Before using SwaggerHub, I advise having basic API knowledge, as those with API knowledge can easily use SwaggerHub. I would rate this review an eight out of ten.
As a technical person, I cannot comment on the money side, but we did not necessarily look to use the whole feature set of SwaggerHub. We do not do editing of the APIs in SwaggerHub; we basically use just a limited number of features from what they provide. SwaggerHub is a development tool for us. SwaggerHub is a way where we align between API producers and API consumers, and the impact is that of a documentation or a developer tool's usual introduction. It is important in a sense, but not something that we cannot live without. We want to keep it going, but there are other more important things. We do see some positive impact from SwaggerHub, but that is only because we are doing versioning of our API, so we have versioned documentation. We could not use SwaggerHub if they would not support versions. It is not driving our practices, but it is good they have it so we can continue with our practices while using SwaggerHub. If they would not have versioning, we would not use it because we would not have gotten the subscription in the first place, as we have had these versioning practices even before we had SwaggerHub. The licensing is subscription-based, which is okay. Most of the software these days is subscription-based, so it is just the standard these days. Our overall review rating for SwaggerHub is nine out of ten.
Based on my limited experience with SwaggerHub, I can share a few practical recommendations for implementing it effectively. Before onboarding multiple teams, it's important to define naming conventions and standards, and leverage reusable components to maintain consistency across APIs, which avoids tech debt in the future. Integrating SwaggerHub with Git-based workflows such as GitHub or GitLab repositories early on ensures that all API changes are traceable and synchronized with the code base. Once we finished scripting, we push the code into GitHub so that when we want to build the project in Jenkins, we configure Jenkins to run in the backend and send reports to stakeholders. It triggers mail notifications whether the build is successful or failures, and we set configurations for user email addresses and the timing of Jenkins runs. The centralized API management location in SwaggerHub has ensured that all teams, including developers, QA, and DevOps, work with the latest and approved API specifications to reduce miscommunication. SwaggerHub supports role-based permissions that enforce who could view, edit, and publish API specifications, which prevents unauthorized changes and helps secure workflows, especially in sensitive, regulated environments. The documentation capabilities via Swagger UI and SwaggerHub have significantly impacted both technical and non-technical stakeholders, improving their understanding and utilization of our APIs. This has resulted in reducing support requests, increasing adoption and integration speed, and empowering non-technical stakeholders while providing improved clarity for developers and QA teams. I rate this solution 8 out of 10.
Director/Enterprise Solutions Architect, Technology Advisor at Kyndryl
Real User
Top 5
Feb 5, 2025
For newcomers, it is advisable to start small. Have one team use SwaggerHub initially, and then expand as needed. If you have existing APIs, begin by using SwaggerHub to test and standardize them. For new developments, adopting an API-first design is beneficial. I rate SwaggerHub as eight out of ten. It has grown significantly over the years.
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.
SwaggerHub simplifies API development for developers by providing a platform where they can efficiently create APIs without manually creating JSON or visual files. Developers can streamline the process of developing APIs and generating requests. SwaggerHub is a platform used for API design and management. Postman serves as a tool for creating and testing API requests. While Postman offers capabilities for scripting and automation, SwaggerHub focuses on defining APIs using the OpenAPI Specification, facilitating collaboration, and generating documentation automatically. While there may be ways to integrate Postman scripts into other testing tools like JMeter, such integration would typically require manual effort and customization. Overall, I rate the solution an eight out of ten.
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.
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.
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.
SwaggerHub streamlines API management with features like centralized management and real-time collaboration, enhancing team efficiency. Its user-friendly interface facilitates API design and testing, offering seamless integration with third-party tools for enhanced teamwork.SwaggerHub provides centralized API definitions enabling easy access and reducing manual errors, which accelerates development. Its role-based access and versioning foster better communication and control among teams....
Before using SwaggerHub, I advise having basic API knowledge, as those with API knowledge can easily use SwaggerHub. I would rate this review an eight out of ten.
As a technical person, I cannot comment on the money side, but we did not necessarily look to use the whole feature set of SwaggerHub. We do not do editing of the APIs in SwaggerHub; we basically use just a limited number of features from what they provide. SwaggerHub is a development tool for us. SwaggerHub is a way where we align between API producers and API consumers, and the impact is that of a documentation or a developer tool's usual introduction. It is important in a sense, but not something that we cannot live without. We want to keep it going, but there are other more important things. We do see some positive impact from SwaggerHub, but that is only because we are doing versioning of our API, so we have versioned documentation. We could not use SwaggerHub if they would not support versions. It is not driving our practices, but it is good they have it so we can continue with our practices while using SwaggerHub. If they would not have versioning, we would not use it because we would not have gotten the subscription in the first place, as we have had these versioning practices even before we had SwaggerHub. The licensing is subscription-based, which is okay. Most of the software these days is subscription-based, so it is just the standard these days. Our overall review rating for SwaggerHub is nine out of ten.
Based on my limited experience with SwaggerHub, I can share a few practical recommendations for implementing it effectively. Before onboarding multiple teams, it's important to define naming conventions and standards, and leverage reusable components to maintain consistency across APIs, which avoids tech debt in the future. Integrating SwaggerHub with Git-based workflows such as GitHub or GitLab repositories early on ensures that all API changes are traceable and synchronized with the code base. Once we finished scripting, we push the code into GitHub so that when we want to build the project in Jenkins, we configure Jenkins to run in the backend and send reports to stakeholders. It triggers mail notifications whether the build is successful or failures, and we set configurations for user email addresses and the timing of Jenkins runs. The centralized API management location in SwaggerHub has ensured that all teams, including developers, QA, and DevOps, work with the latest and approved API specifications to reduce miscommunication. SwaggerHub supports role-based permissions that enforce who could view, edit, and publish API specifications, which prevents unauthorized changes and helps secure workflows, especially in sensitive, regulated environments. The documentation capabilities via Swagger UI and SwaggerHub have significantly impacted both technical and non-technical stakeholders, improving their understanding and utilization of our APIs. This has resulted in reducing support requests, increasing adoption and integration speed, and empowering non-technical stakeholders while providing improved clarity for developers and QA teams. I rate this solution 8 out of 10.
For newcomers, it is advisable to start small. Have one team use SwaggerHub initially, and then expand as needed. If you have existing APIs, begin by using SwaggerHub to test and standardize them. For new developments, adopting an API-first design is beneficial. I rate SwaggerHub as eight out of ten. It has grown significantly over the years.
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.
SwaggerHub simplifies API development for developers by providing a platform where they can efficiently create APIs without manually creating JSON or visual files. Developers can streamline the process of developing APIs and generating requests. SwaggerHub is a platform used for API design and management. Postman serves as a tool for creating and testing API requests. While Postman offers capabilities for scripting and automation, SwaggerHub focuses on defining APIs using the OpenAPI Specification, facilitating collaboration, and generating documentation automatically. While there may be ways to integrate Postman scripts into other testing tools like JMeter, such integration would typically require manual effort and customization. Overall, I rate the solution an eight out of ten.
I rate SwaggerHub a seven out of ten.
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.
I recommend the solution to others and rate it an eight out of ten.
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.
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.
On a scale from one to ten, I would give SwaggerHub a rating of seven.