The making of a great API
summary
Explains concrete rules and tools: decouple DB models from JSON using transformers like Fractal, include hypermedia links (HAL) so clients follow an invoice link instead of hard‑coding endpoints, follow HTTP RFCs (notably RFC 7231 for methods and status codes), return machine‑readable errors with RFC 7807 fields (type, instance, detail) and pretty‑print for humans, use OpenAPI to write specs first and generate validators, prefer OAuth2 for auth and expose X‑RateLimit headers for throttling.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:18API design pitfalls
- 2:53API malleability and decoupling
- 8:47HTTP correctness
- 12:31Error handling best practices
- 15:51API versioning strategies
- 19:09Error handling priority
- 25:12Documentation that developers love
- 32:02Security and auth basics
- 36:58Rate limiting
- 39:14Great API principles
related talks
35mBuilding Your API for Longevity
38mThe Secret to Brewing up a Good API
41mA bird's eye view on API development
35mPrinciples of Awesome APIs and How to Build Them
27mBuilding Great Web APIs
49mWeb APIs that Developers Love
22mThe dirty secrets of building large HTTP APIs
01h 18mAPI design: Lessons Learned