Who Loves your API? Developers want to write software Might
want to use your API Have a different workflow than you Almost
always has other options
Steps to Adoption 1. Found your API 2. Try it out 3. Try to
integrate with you 4. Love or Abandonment Your API wont be used if
not understood
Humanize your API Swagger makes your API Understandable
Testable Discoverable Ready to Integrate
Humans and Machines Simple description structure in JSON Built
as you like Code JSON YAML GUI No pointer chasing Not just Hello
World
Try it out Even your boss can try your API
Build it how you like Its just JSON Host on API server, CDN,
GitHub Discoverable by your process
Your Users can Use your API Generate Clean, Functional SDKs
Your consumers want to use your service How they want Not write
your software
Swagger has a Community Swaggers roots are based on Results
JAX-RS (java) Scalatra (scala) Spring MVC (java) Spray (scala)
Composer (PHP) django (python) Flask (python) Go Maven (JAX-RS)
ServiceStack (.net) Doctrine (PHP) Express (JS) Restler (PHP) Hapi
(JS) Clojure
Where to find out more Google Groups
https://groups.google.com/forum/#!forum/s wagger-swaggersocket IRC
irc.freenode.net Email [email protected] Gluecon Day 2