hypermedia
Links placed inside representations so clients discover related resources and available actions instead of building addresses themselves.
In more detail
Each link pairs a target with a relation that explains its meaning, such as next or author. Links can change with state: an open task can offer completion and a done task need not. Clients that follow supplied links are less coupled to routing details.
Related terms
- HATEOAS — Short for Hypermedia as the Engine of Application State: the REST constraint that clients move through an API by following links the server supplies.
- link relation — The name that says what a link means, such as next, author or self, written as rel in a Link header.
- Link header — The response header that carries typed links to related resources, such as Link: </tasks/1/owner>; rel="author".
- next link — The link a paginated response gives to the following page, which the client should follow exactly as supplied.
Taught in
- The REST Constraints — Modern API Architecture: REST, GraphQL & gRPC
- HATEOAS And Hypermedia — Modern API Architecture: REST, GraphQL & gRPC