02 Rest Constraint Hateoas

title: HATEOAS as a REST Architectural Constraint weight: 12 date: 2026-06-28 lastmod: 2026-06-28 description: Understand HATEOAS as the final REST constraint requiring hypermedia links for API navigation, enabling evolvable APIs and decoupled client-server interactions. tags: [api-development, hateoas]

HATEOAS is the fourth constraint of the Uniform Interface in REST, requiring that servers guide clients through the application state by embedding hypermedia links in responses, enabling API evolution without breaking clients.

```python
# Response WITHOUT HATEOAS (client must know URLs)
{
    "id": 42,
    "name": "Alice",
    "email": "alice@example.com"
}

# Response WITH HATEOAS (client discovers URLs)
{
    "id": 42,
    "name": "Alice",
    "email": "alice@example.com",
    "_links": {
        "self": {"href": "/users/42", "rel": "self"},
        "orders": {"href": "/users/42/orders", "rel": "collection"},
        "update": {"href": "/users/42", "rel": "edit", "method": "PUT"},
        "delete": {"href": "/users/42", "rel": "delete", "method": "DELETE"},
        "profile": {"href": "/users/42/profile", "rel": "related"}
    }
}

Without HATEOAS, clients hard-code URL patterns from documentation. With HATEOAS, clients start at a root endpoint and follow links. This decouples clients from URL structures, allowing the server to reorganize URLs without breaking clients.

What's Next

Now learn about the Richardson Maturity Model in Hypermedia APIs and HATEOAS.