A bird's eye view on API development
summary
Explains concrete rules and examples: when to return 201 and 202 status codes, how PUT differs from PATCH and why to send a Location header on POST rather than a body, and why use UUIDs for public IDs. Compares pagination strategies (page/offset/cursor), shows a JSON:API-style HATEOAS example (Star Wars API), walks through auth choices including JWT and OAuth with refresh tokens, and recommends versioning via the Accept header, Swagger/Blueprint/Apiary and tooling like Fractal/Dingo/Laravel or Django REST Framework.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:26Who has built an API
- 2:51HTTP verbs
- 8:20HTTP codes
- 11:48HTTP headers
- 17:42JSON API
- 22:44Discoverable API
- 31:23Versioning
- 34:33Documentation
related talks
49mWeb APIs that Developers Love
41mThe making of a great API
27mBuilding Great Web APIs
37mAPI Design: It's Not Rocket Surgery
38mThe Secret to Brewing up a Good API
42mLet’s Have Some Effective REST!
47mBuilding APIs your users will want to use
40mGive It a REST – Tips for Designing and Consuming Public API’s