Frank Denbow, Startup Threads
•
0 likes•530 views
This document discusses how to create an API that developers love. It emphasizes the importance of solving developer pain points, using common standards like REST and JSON, providing thorough documentation with code samples in multiple languages, and reliable long-term support. Well-designed APIs at companies like Netflix, Twitter, Foursquare, Stripe and Twilio are used as positive examples. The document encourages aligning business goals with developers' needs, committing to API maintenance, and being available to help developers whenever needed.
Recommended
More Related Content
Viewers also liked
Similar to Frank Denbow, Startup Threads
Similar to Frank Denbow, Startup Threads (20)
More from Mashery
More from Mashery (17)
Recently uploaded
Recently uploaded (20)
Frank Denbow, Startup Threads
- 1. Making an API Developers Love By Frank Denbow @frankdenbow Thursday, October 27, 2011
- 2. Who I Am Developer, Carnegie Mellon Picsicle iOS App StartupThreads Startup Weekend, Startup Digest 15+ hackathons Thursday, October 27, 2011
- 3. Why An API Matters Developer community can bring Creativity New Markets Evangelists Thursday, October 27, 2011
- 4. Netflix: 20 Billion API calls/month http://techblog.netflix.com/2011/02/redesigning- netflix-api.html Thursday, October 27, 2011
- 5. Twitter: 75% of calls in API Developer community vital to the reach http://blog.programmableweb.com/2010/04/15/ Thursday, October 27, 2011
- 6. High Level Topics Solve Developer Pain Incentives Commitment Reliability Thursday, October 27, 2011
- 7. Solve Developer Pain Helping developers build things faster, better Thursday, October 27, 2011
- 8. Thursday, October 27, 2011
- 9. Example: CelebrityTwin.me Face.com: Facial recognition API, used in CelebrityTwin.me Thursday, October 27, 2011
- 10. Example: CelebrityTwin.me Face.com: Facial recognition API, used in CelebrityTwin.me Thursday, October 27, 2011
- 11. 66% Facial Similarity Example: CelebrityTwin.me Face.com: Facial recognition API, used in CelebrityTwin.me Thursday, October 27, 2011
- 12. Incentives Are your business goals in line with the developer’s? Thursday, October 27, 2011
- 13. Commitment Is your API a high priority? Can I count on you to maintain and support the API as needed? Thursday, October 27, 2011
- 14. Reliable Can I count on your API to be available at all times? Thursday, October 27, 2011
- 15. Granular Topics of Interest Simplicity Standards (JSON, REST) Documentation Support Thursday, October 27, 2011
- 16. Simple Easy to understand, predictable resources, speed to hello world Thursday, October 27, 2011
- 17. Example: Foursquare Predictable endpoints, versioning Thursday, October 27, 2011
- 18. Standards Use common standards to make adoption easier and consistent. REST, JSON Thursday, October 27, 2011
- 19. Documentation Example Code, API Explorer (Mashery), Multiple Languages Thursday, October 27, 2011
- 20. Example: Mashery Explorer Thursday, October 27, 2011
- 21. Documentation: Stripe Payments API Code samples in multiple languages Copiable sample code Supplement with live chat Thursday, October 27, 2011
- 22. Example: Stripe Get started page has copiable code Thursday, October 27, 2011
- 23. Example: Stripe Code in multiple languages Thursday, October 27, 2011
- 24. Support Be available whenever you are needed Thursday, October 27, 2011
- 25. Support Example: Twilio SMS and Telephony API Weekend Support Fulltime Evangelists Thursday, October 27, 2011
- 26. Thanks! @frankdenbow Thursday, October 27, 2011