REST API design good practices
summary
REST APIs start from business assets: expose resources not RPC actions, keep base URLs simple and use nouns in URLs. Use standard HTTP verbs (GET/POST/PUT/PATCH/DELETE), push complex options into query parameters and support field views so responses return only requested fields. Favor a small, predictable error set (400/500) and version URLs when breaking changes arise; aim for Richardson level 2 rather than hypermedia. Tooling stack examples: OpenAPI v3, Postman, Runscope/loader.io, Apigee and note there are over 20,000 public APIs today.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 7:29REST API as product
- 10:07Design principles
- 17:56HTTP verbs usage
- 20:51Error handling
- 22:18API versioning
- 24:31REST maturity model
- 28:13Design tools
- 32:39API testing
- 36:31API management
- 39:05Q&A
related talks
54mEffective Design of RESTful APIs
52mDesigning and Implementing REST APIs For the Long Haul
41mREST API refactoring.
17mRESTful API Patterns and Practices
53mEffective Design of RESTful APIs
49mWeb APIs that Developers Love
15mHow to Design Effective APIs | Actionable Guide
35mBuilding Your API for Longevity
