Skip to content

HATEOAS

Hypermedia As The Engine Of Application State

Spicy — senior dev territoryBackend

ELI5 — The Vibe Check

HATEOAS is the REST principle that nobody actually follows. The idea is that API responses should include links telling the client what it can do next, like a 'choose your own adventure' book. In theory it's beautiful. In practice, everyone just reads the API docs.

Real Talk

HATEOAS is a constraint of REST architecture where responses include hypermedia links that describe available actions and state transitions. A HATEOAS-compliant API allows clients to navigate the entire API by following links rather than hardcoding URLs. While theoretically ideal for decoupling clients from servers, it's rarely implemented fully in practice.

Show Me The Code

{
  "id": 1,
  "name": "Alice",
  "_links": {
    "self": { "href": "/users/1" },
    "orders": { "href": "/users/1/orders" },
    "delete": { "href": "/users/1", "method": "DELETE" }
  }
}

When You'll Hear This

"Our API is RESTful but not HATEOAS — we use docs instead of hypermedia links." / "HATEOAS sounds great in theory but adds complexity nobody asked for."

Made with passive-aggressive love by manoga.digital. Powered by Claude.