Swagger UI logo

Swagger UI

A Collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation
948
541
+ 1
136

What is Swagger UI?

Swagger UI is a dependency-free collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation and sandbox from a Swagger-compliant API
Swagger UI is a tool in the Documentation as a Service & Tools category of a tech stack.
Swagger UI is an open source tool with 16.6K GitHub stars and 7K GitHub forks. Here’s a link to Swagger UI's open source repository on GitHub

Who uses Swagger UI?

Companies
297 companies reportedly use Swagger UI in their tech stacks, including Banksalad, Zalando, and Hootsuite.

Developers
611 developers on StackShare have stated that they use Swagger UI.

Swagger UI Integrations

Node.js, Git, Google Chrome, Sandbox, and SQueaLy are some of the popular tools that integrate with Swagger UI. Here's a list of all 12 tools that integrate with Swagger UI.

Why developers like Swagger UI?

Here’s a list of reasons why companies and developers use Swagger UI
Swagger UI Reviews

Here are some stack decisions, common use cases and reviews by companies and developers who chose Swagger UI in their tech stack.

Noah Zoschke
Noah Zoschke
Engineering Manager at Segment · | 29 upvotes · 216K views
atSegmentSegment
Postman
Postman
Markdown
Markdown
ReadMe.io
ReadMe.io
Swagger UI
Swagger UI
#Documentation
#Api
#QA

We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

See more
Jeyabalaji Subramanian
Jeyabalaji Subramanian
CTO at FundsCorner · | 12 upvotes · 366.1K views
atFundsCornerFundsCorner
Amazon SQS
Amazon SQS
Python
Python
Flask
Flask
MongoDB
MongoDB
Swagger UI
Swagger UI
Vue.js
Vue.js
Vuetify
Vuetify
vuex
vuex
Zappa
Zappa
AWS Lambda
AWS Lambda
Netlify
Netlify
Google Compute Engine
Google Compute Engine
Slack
Slack
GitLab CI
GitLab CI
Sentry
Sentry

At FundsCorner, we are on a mission to enable fast accessible credit to India’s Kirana Stores. We are an early stage startup with an ultra small Engineering team. All the tech decisions we have made until now are based on our core philosophy: "Build usable products fast".

Based on the above fundamentals, we chose Python as our base language for all our APIs and micro-services. It is ultra easy to start with, yet provides great libraries even for the most complex of use cases. Our entire backend stack runs on Python and we cannot be more happy with it! If you are looking to deploy your API as server-less, Python provides one of the least cold start times.

We build our APIs with Flask. For backend database, our natural choice was MongoDB. It frees up our time from complex database specifications - we instead use our time in doing sensible data modelling & once we finalize the data model, we integrate it into Flask using Swagger UI. Mongo supports complex queries to cull out difficult data through aggregation framework & we have even built an internal framework called "Poetry", for aggregation queries.

Our web apps are built on Vue.js , Vuetify and vuex. Initially we debated a lot around choosing Vue.js or React , but finally settled with Vue.js, mainly because of the ease of use, fast development cycles & awesome set of libraries and utilities backing Vue.

You simply cannot go wrong with Vue.js . Great documentation, the library is ultra compact & is blazing fast. Choosing Vue.js was one of the critical decisions made, which enabled us to launch our web app in under a month (which otherwise would have taken 3 months easily). For those folks who are looking for big names, Adobe, and Alibaba and Gitlab are using Vue.

By choosing Vuetify, we saved thousands of person hours in designing the CSS files. Vuetify contains all key material components for designing a smooth User experience & it just works! It's an awesome framework. All of us at FundsCorner are now lifelong fanboys of Vue.js and Vuetify.

On the infrastructure side, all our API services and backend services are deployed as server less micro-services through Zappa. Zappa makes your life super easy by packaging everything that is required to deploy your code as AWS Lambda. We are now addicted to the single - click deploys / updates through Zappa. Try it out & you will convert!

Also, if you are using Zappa, you can greatly simplify your CI / CD pipelines. Do try it! It's just awesome! and... you will be astonished by the savings you have made on AWS bills at end of the month.

Our CI / CD pipelines are built using GitLab CI. The documentation is very good & it enables you to go from from concept to production in minimal time frame.

We use Sentry for all crash reporting and resolution. Pro tip, they do have handlers for AWS Lambda , which made our integration super easy.

All our micro-services including APIs are event-driven. Our background micro-services are message oriented & we use Amazon SQS as our message pipe. We have our own in-house workflow manager to orchestrate across micro - services.

We host our static websites on Netlify. One of the cool things about Netlify is the automated CI / CD on git push. You just do a git push to deploy! Again, it is super simple to use and it just works. We were dogmatic about going server less even on static web sites & you can go server less on Netlify in a few minutes. It's just a few clicks away.

We use Google Compute Engine, especially Google Vision for our AI experiments.

For Ops automation, we use Slack. Slack provides a super-rich API (through Slack App) through which you can weave magical automation on boring ops tasks.

See more
Tim Nolet
Tim Nolet
Founder, Engineer & Dishwasher at Checkly · | 7 upvotes · 65.4K views
atChecklyHQChecklyHQ
JavaScript
JavaScript
Node.js
Node.js
hapi
hapi
Vue.js
Vue.js
Swagger UI
Swagger UI
Slate
Slate

JavaScript Node.js hapi Vue.js Swagger UI Slate

Two weeks ago we released the public API for Checkly. We already had an API that was serving our frontend Vue.js app. We decided to create an new set of API endpoints and not reuse the already existing one. The blog post linked below details what parts we needed to refactor, what parts we added and how we handled generating API documentation. More specifically, the post dives into:

  • Refactoring the existing Hapi.js based API
  • API key based authentication
  • Refactoring models with Objection.js
  • Validating plan limits
  • Generating Swagger & Slate based documentation
See more
Julien DeFrance
Julien DeFrance
Principal Software Engineer at Tophatter · | 5 upvotes · 14.1K views
atSmartZipSmartZip
Swagger UI
Swagger UI
Ruby
Ruby

Use case: Keeping all API endpoints documented.

Swagger UI is slick. Not only details the specifications of all input/output parameters are there, but the interface also is interactive and allows sample requests to be sent to the actual endpoints.

With the help of Ruby gems such as https://github.com/richhollis/swagger-docs, the JSON files can automatically be generated for you for every controller you want to appear on the documentations page.

See more
Andrey Kurdyumov
Andrey Kurdyumov
Sr. Software developer · | 5 upvotes · 11.7K views
Swagger UI
Swagger UI

I use Swagger UI because it integrated nicely with my .NET Core MVC APIs. I just add Swashbuckle and I have documented my API. Since I usually comment all public methods, that almost instantly give me ability to generate clients for my APIs, which lead to API-frist design without any additional effort from my side. Same pleasure to work as WCF, eariler.

See more
Jadenko
Jadenko
| 2 upvotes · 10.7K views
atEuropean CommissionEuropean Commission
Swagger UI
Swagger UI
Postman
Postman

I use Swagger UI because it's an easy tool for end-consumers to visualize and test our APIs. It focuses on that ! And it's directly embedded and delivered with the APIs. Postman's built-in tools aren't bad, but their main focus isn't the documentation and also, they are hosted outside the project.

See more

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

Swagger UI Alternatives & Comparisons

What are some alternatives to Swagger UI?
Postman
It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide.
Apiary
It takes more than a simple HTML page to thrill your API users. The right tools take weeks of development. Weeks that apiary.io saves.
ReadMe.io
Collaborative Developer Hubs
jsdoc
JSDoc 3 is an API documentation generator for JavaScript, similar to JavaDoc or PHPDoc. You add documentation comments directly to your source code, right along side the code itself. The JSDoc Tool will scan your source code, and generate a complete HTML documentation website for you.
Gitbook
It is a modern documentation platform where teams can document everything from products, to APIs and internal knowledge-bases. It is a place to think and track ideas for you & your team.
See all alternatives

Swagger UI's Followers
541 developers follow Swagger UI to keep up with related blogs and decisions.
Carlos Hernandez-Vaquero
ip999
11arn11
태화 정
Vamsi Krishna  JS
Nils Peuser
Żaneta Jażdżyk
Shekhar Tanwar
Tom Bazarnik
ayoshing