SwaggerHub

SwaggerHub is used in our organization to document our APIs and build out the models for them. This helps our entire team, by keeping them updated and know which resources we have and what to expect back from them. My favorite problem that this addresses is our testing. We can easily import the API into ReadyAPI and build out our tests directly from that, without having to build out an API at that step.

We use SwaggerHub across the organization to design API endpoint and documentation for our microservices architecture. It's works well in collaborating more easily on developing API in our team. It also can be used to test our API endpoint which makes an integration test easier when we deploy changes to the API. And it is also user-friendly that any other developer/QA can easily understand the service contract and error handling structure etc when testing in it.

Ours is a small startup; our product is still under development. We use SwaggerHub to document all our APIs. Try & execute the APIs from the console instead of using CURL or something. Always helps in checking our backend APIS calls and see how the APIs are functioning. A very handy tool.

We use SwaggerHub to design our micro service APIs prior to development starting. Our Solution Architect's and Technical Business Analysts are able to collaborate and define the APIs based off user stories. Our Swagger API definitions are a core part of our customer facing documentation, so we put a lot of effort into that design phase to make sure we have consistent naming standards and have great descriptions and examples for each endpoint. Our customers can read our API documentation to understand what each API does, and they can also import the Swagger definitions and code stubs into their IDEs to give them a head start on the development process.