1. Love your API with Swagger
@fehguy

2. 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

3. Steps to Adoption
1. Found your API
2. Try it out
3. Try to integrate with you
4. Love or Abandonment
Your API won’t be used if not
understood

4. Humanize your API
Swagger makes your API
• Understandable
• Testable
• Discoverable
• Ready to Integrate

5. Humans and Machines
• Simple description structure in JSON
• Built as you like
– Code
– JSON
– YAML
– GUI
• No “pointer chasing”
Not just
Hello
World

6. Try it out
“Even your boss can try your API”

7. Build it how you like
• It’s just JSON
– Host on API server, CDN, GitHub
• Discoverable by your process

8. Your Users can Use your API
• Generate Clean, Functional SDKs
• Your consumers want to use your service
– How they want
– Not write your software

9. 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

10. Swagger is FOSS
• Apache 2 License
https://github.com/wordnik/swagger-spec
https://github.com/wordnik/swagger-core
https://github.com/wordnik/swagger-codegen
https://github.com/wordnik/swagger-ui
https://github.com/wordnik/swagger-node-express
https://github.com/scalatra/scalatra

11. Where to find out more
Google Groups
• https://groups.google.com/forum/#!forum/s
wagger-swaggersocket
IRC
• irc.freenode.net
Email
• apiteam@wordnik.com
Gluecon
Day 2