REST

HTTP + resource-oriented conventions (verbs, status codes, URIs) — the default for public APIs.

Why we need this / what value this brings

Universally supported, cacheable, human-debuggable — the safest default for a public API.

When to use this

Public-facing APIs, and internal APIs where GraphQL/gRPC's added complexity isn't justified.

How to use or implement this

Use resource-oriented URLs, correct HTTP verbs/status codes, and keep it stateless (see APIDesign/ for contract details).

Research questions

• What HTTP status code conventions does Localz's API currently follow consistently vs not?

---

Empty folder — drop notes, links, and findings here as you research.