Skip to content

Hypermedia as Engine of Application State (HATEOAS)

When responses include links to valid next actions, clients can navigate APIs without hardcoded URL knowledge, enabling server-driven workflow evolution and reducing client-server coupling.

Tension Addressed

Discoverability vs. Coupling

Recognizable As

Links in responses (next, prev, self, related), embedded related resources, discoverable actions, clients that follow links rather than construct URLs

Canonical Sources

Fielding, REST dissertation (2000); Richardson Maturity Model (Level 3)

Transfers To

Web navigation (hyperlinks), Workflow engines, State machines, Wizard interfaces, Progressive disclosure

HATEOAS is REST's most ambitious and least adopted principle. In practice, most APIs settle for partial hypermedia (pagination links) while hardcoding business-critical paths. The principle remains valuable even if full implementation is rare.