Hayk Simonyan on YouTube · Open on YouTube
Core skills: building for the web · Advanced beginner · Lesson 22 of 98 · 1 h 23 min video, then about 6 hours of practice
Designing REST APIs other people can use
After this you can design resource-oriented endpoints with sensible URLs, methods, status codes, validation and error responses.
Why it matters
An API is a contract other people (and your own frontend) build against. Good design makes it predictable: nouns in URLs, HTTP methods with their real meaning, consistent error shapes, pagination for lists, and validation at the edge. Focus on the REST section and the authentication overview. Validate every request body with a schema library such as Zod so bad input is rejected with a 400, not a crash. Trap: designing endpoints around your database tables instead of around what the client needs to do.
How to use this resource
Watch the API design fundamentals and REST sections first; the GraphQL section is optional at this stage.
Go further
Go deeper
Practice