What is Swagger UI?
Who uses Swagger UI?
Swagger UI Integrations
Here are some stack decisions, common use cases and reviews by companies and developers who chose Swagger UI in their tech stack.
We use Swagger Inspector in conjunction with our universal REST-API "Charon". Swagger Inspector makes testing edge-cases hassle-free and lets testing look easy. Swagger Inspector was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.
We previously used Postman but decided to switch over to Swagger Inspector because it also integrated seamlessly into Swagger UI, which we use for displaying our OpenAPI specification of said REST-API.
Our whole Node.js backend stack consists of the following tools:
- Lerna as a tool for multi package and multi repository management
- npm as package manager
- NestJS as Node.js framework
- TypeScript as programming language
- ExpressJS as web server
- Swagger UI for visualizing and interacting with the API’s resources
- Postman as a tool for API development
- TypeORM as object relational mapping layer
- JSON Web Token for access token management
The main reason we have chosen Node.js over PHP is related to the following artifacts:
- Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
Swagger UI's Features
- The UI works in any development environment, be it locally or in the web
- Allow end developers to effortlessly interact and try out every single operation your API exposes for easy consumption
- Quickly find and work with resources and endpoints with neatly categorized documentation
- Cater to every possible scenario with Swagger UI working in all major browsers