SwaggerHub for AWS

What do you like best about the product?

This is the best for API Testing and API visualization. easy to use, easy to maintain. all my apis are easily accessible, easy to visualize.

What do you dislike about the product?

there is nothing to dislike. I like every feature

What problems is the product solving and how is that benefiting you?

earlier using postman its hard to visulize how api is actually working but through smart bear its easy to view and manage also easy to create api documenatation

What do you like best about the product?

API Hub provides good interface for creating the API documentation.

What do you dislike about the product?

It is not free model. They can provide trials to improve this.

What problems is the product solving and how is that benefiting you?

It is so easy for us to make the documentation of the API from the same and after loading the YAML file, it provides us very good UI to check the documentation and test it also.

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.

Positive

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.

Public Cloud

Amazon Web Services (AWS)

What do you like best about the product?

It corrects and thoroughly explains what needs to be understood

What do you dislike about the product?

It doesn't give you different options if paragraphs or languages

What problems is the product solving and how is that benefiting you?

It offers clear direct statements and spelling and grammar

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.