REST APIs

What you'll learn

• When REST is the right shape, and when it isn't
• Designing resources and URIs you can live with
• Picking the correct status code, every time
• Idempotency, retries, and safe operations
• Pagination, filtering, and sorting conventions
• Versioning that doesn't haunt you

1. 01
   What 'REST' actually means

   Roy Fielding, 2000, and what most people mean today.
   12 min
2. 02
   Resources and URIs

   Naming things — the half of REST that survives every fashion.
   13 min
3. 03
   The verbs

   GET, POST, PUT, PATCH, DELETE — and why HEAD and OPTIONS matter.
   14 min
4. 04
   Status codes that aren't 200

   201, 204, 301, 304, 400, 401, 403, 404, 409, 422, 429, 503 — when each fires.
   13 min
5. 05
   Idempotency

   Why retries don't have to mean duplicates.
   12 min
6. 06
   Pagination, filtering, sorting

   The conventions everyone copies and nobody documents.
   14 min
7. 07
   Errors that humans can read

   Problem details and how to write them.
   12 min
8. 08
   Caching, ETags, and 304

   The free performance most APIs leave on the table.
   15 min
9. 09
   Versioning without pain

   Header, path, query — and which one you'll regret.
   13 min
10. 10
    When REST is the wrong tool

    GraphQL, RPC, and websockets — honest tradeoffs.
    12 min