Api Conventions

It covers the practical stuff: plural nouns for resources, kebab-case naming, a consistent response envelope with data/error/meta fields, proper HTTP status codes, and Bearer token auth by default. The two-level nesting limit is smart, pushing you toward query params instead of deep URL hierarchies. What's nice is having versioning and the public endpoint annotation pattern documented. Use this when building new APIs or during code review to keep your team's endpoints consistent. The response format alone will save arguments about error handling.