SwaggerHub includes multiple tools such as Swagger Editor, Swagger UI, and Swagger Codegen. We use SwaggerHub mainly to test our APIs, build and support, extend the APIs, and we generally test them with our applications or tools to determine if we can fetch something or perform activities towards our company's portal.

We use this mainly on SwaggerHub where we build APIs, test them, publish them, and we let developers and other users use it for their internal automations or whatever they want to use.

We have a third-party tool called IP management and operations where we wanted to get the list of IPs and allocate to the servers to determine the available IPs we have and how much capacity we can assign to individual servers. Using that IPAM tool or the IP tool, we created an API using SwaggerHub where we added some scripts and tasks to get the relevant details and we published that API integrating with that tool.

Once we completed that publishing, the developers can access the list of available IPs from the IPAM tool using that API and then they can fetch how many available IPs exist in that particular pool and what next available IP they can allocate to their servers which they want to spin up or create anything.

Being a DevOps engineer, we don't do end-to-end things on SwaggerHub, but we mainly interact with fixing things, implementing things, and working with SwaggerHub and using their APIs or publishing the APIs and doing documentation. The recent use case that I have interacted with where our SSL certificate had gone haywire, so we wanted to fix something on SwaggerHub, and we followed their documentation in order to fix it, and we finally were able to achieve it. That is the last thing that we worked on SwaggerHub because our SwaggerHub is running on an AWS server, which is a standalone server.

There are multiple features, but the main feature that I appreciate about SwaggerHub is their documentation part, where you can easily get the documentation for any API you have created. You can easily publish the documentation and share it with your developers or team members.

The second feature is their UI, which is very easy to use and very interactive. You can easily drag and drop things, create APIs, test APIs, and publish APIs. The third feature is their integration part. You can easily integrate SwaggerHub with other third-party tools or applications, as we have integrated with the IPAM tool.

Most companies mainly rely on automations to get things done better rather than doing it in a manual way. SwaggerHub provided us an interface to interact with other tools and collaborate and work with the developers and the cross teams.

That is where all teams can combine and work productively and effectively and reduce many man-hours to fix things and make things easier and quicker. In this way, SwaggerHub plays a crucial role in order to bring teams and automate things faster and also reduce the man-hours and increase the work efficiency.

By building the collective APIs and endpoints, SwaggerHub has roughly downgraded the user operations by about 40% of manual needs by bringing the automations and interacting the APIs and open API endpoints.

This part has saved many hours of fixing the errors and going through every part and understanding where exactly this has caused. SwaggerHub plays a crucial role here by giving crisp solutions where we can interact with other tools and technologies using the API ecosystems. This can reduce around 40 to 50% of man-hours using their tool and automation.

Documenting SwaggerHub has a standard and consistent structure of API definitions, and it automatically generates interactive documentation which helps the developers to understand everything. There are certain areas where SwaggerHub can go beyond here as formatting options for documentation pages are restricted, and the import and export options of API collections are complex in SwaggerHub. It provides various collaboration tools where we can work and do it.

The strong validation against the API maintains conformity and reduces errors. That part is very great in SwaggerHub. Overall, scalability and stability-wise, it varies high compared to the competitors, but there are still certain areas where competitors are providing various customizations. SwaggerHub can understand those aspects and implement them as well.

The complex import and export of API calls and collaborations can be challenging in SwaggerHub. If they can make it easier for us, that would be great. Their performance is degraded if there is too much load on the API. The customization and doc formatting options for documentation pages are restricted in SwaggerHub. A few of my teammates have complained that they find the UI unintuitive where it requires multiple clicks for simple tasks. SwaggerHub is a great tool, but these limitations can be addressed to make things better and easier.

I have used SwaggerHub for over two years, where we usually create and manage APIs in SwaggerHub, company-level APIs where we interact with some other tools, the third-party tools where we wanted to integrate and test them.

I have used SwaggerHub for around two to three years and my last interaction with SwaggerHub was around six months back, where I hosted SwaggerHub on an AWS server.

If they wanted to build or customize anything related to APIs or whatever they wanted to achieve, SwaggerHub is the best option and I feel they can absolutely go for it compared to the other tools which are existing in the market.

SwaggerHub stands great at the enterprise level. The way it is performing right now is solid and great. I rate SwaggerHub 8.5 out of 10.

I have worked for Arden University, University of Sheffield, and Nanyang Technological University. For those institutions, I used Amazon AppStream for backend validations.

When working for Prolifics, I used it for backend validations and data creation. In our testing, we had different sets of environments, such as Test, FT, UAT, and sometimes the Dev instance, where we performed validations.

My recent project, DDI (Direct Device Interface), involved a client, Thermo Fisher Scientific, which is a product-based company. In this project, there was a Tune application they had already developed in the desktop version, and they were planning to switch it to the cloud. There, I performed API testing using Swagger and API testing.

I have used automated validations and testing features to support API quality control in my projects.

Automation, using Swagger validations in CI/CD tools, has helped catch schema mismatches early. In one of my recent projects, the backend team made changes to a response object by adding a new required field without updating the Swagger specification. Because we had Swagger CLI validations integrated into our Jenkins pipeline, it caught the mismatch immediately, thereby preventing breaking changes and facilitating faster feedback with automated Postman.

SwaggerHub has significantly improved how my organization designs, documents, and manages APIs, centralizing API management so that all API definitions are stored in one location, which makes it easy for stakeholders, developers, QA, DevOps, and products to access the latest version. It has improved collaboration through role-based access tools, streamlined API design, and review processes, and accelerated development cycles while reducing errors and reworking through automated validations that catch issues early.

One of the best features I appreciate about Swagger is the interactive API documentation it offers, which has saved me a lot of time during validations and exploratory API testing as a QA engineer.

For Swagger, I used it primarily for the API design and documentation as it is integrated into the SmartBear ecosystem. It supports open API specifications and helps create clear, machine-readable documentation. With Swagger UI, developers and testers can view the API endpoints with alternative web interfaces. Additionally, Swagger can generate server stubs and client SDKs in various programming languages automatically, saving a lot of time and reducing manual errors.

In SwaggerHub, I appreciate that it is a powerful platform for API design and collaboration, but currently, the access control is somewhat limited. I would love to see enhanced permissions allowing a user to comment without edit access or granting edit access to specific sections of the API specification. Better integration with CI/CD pipelines would also be beneficial, making the integrations more native and streamlined, especially for managing API specifications across different environments while avoiding manual duplications or workarounds.

My experience with the AppStream is more than a year.

During my experience with SwaggerHub, it has been quite stable overall. I have not encountered any major performance issues, crashes, or unplanned downtimes. The cloud-hosted version we used was reliable and responsive, even with multiple users collaborating on the same API simultaneously. However, there were brief lags or slow loading times when working with very large or complex open API specs, but these occurrences were rare and didn't disrupt our work.

SwaggerHub has proven scalable, especially in a team environment with growing API definitions and multiple collaborators. We worked with several large and complex open API specifications, including multiple endpoints, schemas, and reusable components, that it handled smoothly. While we noticed slight performance lags when loading very large specs, it never became a blocker.

I have not had to reach out to SwaggerHub technical support directly, as most issues we faced were either minor or could be resolved internally through documentation and forums.

I have not worked with any other API management solutions, as I had limited opportunities to perform API testing, having used only Swagger and Postman in my previous organization.

I wasn't directly involved in the initial setup or deployment process of SwaggerHub. However, once it was integrated into our development workflow, I became deeply involved with it.

While I haven't been directly involved in the procurement process, I do have a general understanding of SwaggerHub's pricing model from my experience using it in enterprise environments, but I can't provide specific details.

I am not aware of the pricing, licensing cost, or setup cost of SwaggerHub.

I did not evaluate any other options or solutions available on the market for API management.

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.