Advanced API design: how an awesome API can attract friends...
summary
A clear checklist: an API uses REST conventions and HTTP status codes, offers versioning, returns structured validation errors and parsing hints, and supports both JSON and XML; provide client libraries, docs generated from a simple DSL, request logging, rate limiting, and caching. For long work, the system accepts a job, returns asynchronous jobs with job id and callbacks and a file location, so processing never blocks. Examples include Zencoder (video/audio transcoding), Twilio, AWS and the claim that cloud lowers costs by ~100x.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:20The basics
- 3:50API history
- 6:40How to make a good API
- 8:35Versioning your API
- 12:45Smart validation
- 16:35JSON vs XML
- 19:00Documentation
- 20:50Provide libraries
- 25:45Rate limiting
- 26:25Log requests
- 27:04API request builder
- 27:54What makes a good API
- 35:38How can API help you make friends
- 38:41Software is eating the world
- 40:01API to something
- 44:53API can change the world
- 45:51Linux
- 47:11Revolution of the next 10 years
