Resta saysREST is the dominant API style — model everything as resources accessed via HTTP methods.
REST (Representational State Transfer) organizes an API around resources (nouns like /users, /orders) acted on by HTTP methods (the verbs). A URL names a thing; the method says what to do with it. It leans on HTTP's own features — status codes, caching, statelessness — rather than inventing its own. Most web APIs you'll use are RESTful.
Power-ups you unlock
Resources (nouns) + HTTP methods (verbs)
URLs name things; methods act on them
Leverages HTTP status/caching/statelessness
The default web API style
The 401 Bandit attacks — common mistakes
Verbs in URLs (/getUser) instead of nouns
Ignoring HTTP status codes
Stateful endpoints that break statelessness
Boss battleDesign REST endpoints for listing, reading, creating, and deleting orders.
Example code
<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#e6e0ff;font-family:monospace;padding:20px"><pre>GET /orders list
GET /orders/42 read one
POST /orders create
DELETE /orders/42 remove</pre></body></html>