10 practical resources to learn API design (for working devs):
1) API Design Patterns (JJ Geewax, book) Solid mental models for pagination, filtering, idempotency, and long-running ops.
2) Designing Web APIs (O’Reilly, book) Good on resource modeling and linking, plus the boring consistency rules teams fight over.
3) Google Cloud API Design Guide (docs) Opinionated guidelines and naming rules that map well to real orgs.
4) Microsoft REST API Guidelines (docs) Pragmatic conventions for errors, versioning, and compatibility over time.
5) Stripe API docs (docs) Study how they document errors, idempotency keys, expansions, and “do the safe thing by default”.
6) GitHub REST API docs (docs) Great for pagination patterns, previews/deprecations, and public API hygiene under load.
7) Zalando RESTful API Guidelines (docs) Concrete rules for HTTP semantics, problem+json errors, and consistent field naming.
8) OpenAPI Specification + Spectral (spec + tool) Write the contract first, lint it in CI, generate clients, then feel the tradeoffs.
9) Postman API Network collections (practice) Import real APIs, write tests for status codes + schemas, and catch breaking changes early.
10) Build a small public API end to end (project) Auth, rate limits, idempotent POST, cursor pagination, structured errors, and a deprecation plan; ship it and support one “client” you don’t control