Api Design Patterns

A solid reference for REST API design covering 38 rules across resource naming, error handling, security, pagination, versioning, and response formatting. It pushes you toward the standard patterns like using nouns not verbs in URLs, returning consistent error structures with request IDs, and implementing proper rate limiting headers. The examples are concrete and show both wrong and right approaches. Use it when you're designing new endpoints or reviewing existing APIs and want to follow industry conventions from Zalando, Microsoft, and Google. It's prescriptive rather than exploratory, so if you're building something intentionally unconventional, you'll be fighting it.