Protocols
Saved & recent

REST

Also called: Representational State Transfer, RESTful architecture

REST is an architectural style for distributed hypermedia systems, rather than a single wire protocol or a synonym for JSON APIs. Its constraints include client–server separation, stateless interaction, cacheability, a uniform interface and layers; executable code sent to clients is optional. Resources are manipulated through representations.

A hypothetical order representation can include its current status and a link to the available cancellation action. The client follows that advertised transition using the interface’s defined semantics. Merely naming paths /orders and exchanging JSON does not establish every REST constraint. Statelessness concerns request context; it does not prohibit storing resource data.

Read first
HTTP
Related
HTTP, Remote procedure call, Content negotiation
Further reading
Roy Fielding — REST architectural style
client origin cache / layer boundary retrieve order order representation received representation status: pending cancel action link follow advertised cancel action representation · status cancelled stored order resource state hypermedia-guided interaction
A hypothetical order representation advertises an available cancellation transition. The client uses that link and receives a new representation. This illustrates hypermedia within REST’s broader architectural constraints, not a full definition of REST.

View in the full Protocols collection