Guide: look up HTTP status codes and when to use them
REST APIs should return 201 on create, 204 with no body, 409 on conflict — not only 200/500. Reviews often blur 422 vs 400 or 502 vs 503.
The reference loads as a static in-browser catalog — no search tracking. Each entry summarizes meaning, when to use it, and client cache/retry impact.
Use when writing OpenAPI, Express/Fastify handlers, or explaining why retry fits 503 but not 400. Pair with the API tester to see real responses.
Step by step
- Search by code or name — Type `418`, `unauthorized`, or 4xx to filter quickly.
- Read semantics and examples — Confirm verb fit — GET rarely returns 201.
- Set service error policy — Standardize JSON error bodies with an internal `code` plus HTTP status.
- Apply in handlers — Return the right status and `Retry-After` on 429/503 per docs.