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.
Director/Enterprise Solutions Architect, Technology Advisor at Kyndryl
Real User
Top 5
Feb 5, 2025
I started using SwaggerHub in its previous version, SmartMiner, with a tool called SoapUI. I used it to create mock web services to test web services and create test scripts and mock APIs. This usage began in 2009 or 2010. Later, I adopted SwaggerHub as the platform evolved into Swagger and now OpenAPI, to create APIs.
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.
SwaggerHub securely saves API calls, thereby ensuring the confidentiality of secrets. Additionally, it facilitates the validation of APIs, making them safer to use on the server.
The company I work for purchased SwaggerHub with the intent to use it for a certain period of time. I use SwaggerHub in my company for testing purposes, especially testing the APIs.
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.
We hope to use it for the design of the API and for the entry point of the documentation to help the consumers of the API in understanding the API and specifications.
IT Manager at a insurance company with 10,001+ employees
Real User
Aug 23, 2020
We use SwaggerHub to publish our APIs. We also integrate SmartBear ReadyAPI with Swagger. We use it to manage our APIs. When we develop an API, we then integrate it with SwaggerHub. Centene is a large corporation with plenty of automation so there are various development teams across Centene who use this solution for various use cases. Normally, they publish their APIs on SwaggerHub for seamless integration with SmartBear and ReadyAPI. This allows us to perform detailed end-to-end automation testing.
SwaggerHub is an integrated API Development platform, built for teams, that brings the core capabilities of the Swagger framework to design, build, document and deploy APIs. SwaggerHub enables development teams to collaborate and coordinate the entire lifecycle of an API with the flexibility to integrate with the toolset of your choice.
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.
I started using SwaggerHub in its previous version, SmartMiner, with a tool called SoapUI. I used it to create mock web services to test web services and create test scripts and mock APIs. This usage began in 2009 or 2010. Later, I adopted SwaggerHub as the platform evolved into Swagger and now OpenAPI, to create APIs.
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.
SwaggerHub securely saves API calls, thereby ensuring the confidentiality of secrets. Additionally, it facilitates the validation of APIs, making them safer to use on the server.
The company I work for purchased SwaggerHub with the intent to use it for a certain period of time. I use SwaggerHub in my company for testing purposes, especially testing the APIs.
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.
We use the solution to develop and test the APIs.
We hope to use it for the design of the API and for the entry point of the documentation to help the consumers of the API in understanding the API and specifications.
We use SwaggerHub to publish our APIs. We also integrate SmartBear ReadyAPI with Swagger. We use it to manage our APIs. When we develop an API, we then integrate it with SwaggerHub. Centene is a large corporation with plenty of automation so there are various development teams across Centene who use this solution for various use cases. Normally, they publish their APIs on SwaggerHub for seamless integration with SmartBear and ReadyAPI. This allows us to perform detailed end-to-end automation testing.