Skip to content

HATEOAS

HATEOAS makes available application transitions discoverable through hypermedia controls in received representations.

Version
v2 · 2026-10-03 · History
Domain-specific #
13297
Aliases
Hypermedia as the Engine of Application State

Core Idea

HATEOAS is the REST idea that a response offers links or actions the client can use to move to its next application state.

Scope of Application

Web pages use links and forms; APIs can expose typed controls. A client still needs to understand the media and action meanings.

Boundary: Using HTTP or embedding arbitrary URLs does not by itself make an interface hypermedia-driven.

Clarity

Look for controls in the current representation, not merely URL strings or a separate route list.

Manages Complexity

Advertised transitions reduce hard-coded navigation assumptions but require a shared control vocabulary.

Abstract Reasoning

Start at an entry point, read the response's controls, choose one, perform it, and repeat with the new response. If the next page no longer offers an action, do not assume an old memorized route is still the right move.

Knowledge Transfer

Browser links and programmatic action relations share this pattern but use different syntaxes. The parent is Representation by strict presupposition: controls must be carried in a received representation, while the architectural constraint is not itself a kind of representation.

For example, a draft-order page might offer a confirmation form; the receipt page reached after submission offers a receipt link instead. This is an illustration of represented transitions, not a claim about a particular site.

Relationships to Other Abstractions

Local relationship map for HATEOASParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.HATEOASDOMAINPrime abstraction: Representation — presupposesRepresentationPRIME

Current abstraction HATEOAS Domain-specific

Parents (1) — more general patterns this builds on

  • HATEOAS presupposes Representation Prime

    HATEOAS requires received representations to carry discoverable hypermedia controls for next application-state transitions.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

HATEOAS sits in a sparse region of the domain-specific corpus (89th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2551 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08