Skip to main content
Definition Website Computer and Technology

Representational State Transfer

Subject: Computer and Technology noun /ˌrɛp.rɪ.zɛnˈteɪ.ʃən.əl ˈsteɪt ˈtræns.fɜːr/ 1 definition

  1. Definition (noun)

    Entry #99 · Updated

    Representational State Transfer (REST) is a software architectural style for distributed hypermedia systems in which clients and servers interact by exchanging self-descriptive representations of addressable resources. Grounded in constraints such as client-server separation, stateless requests, explicit cacheability, layered intermediaries, and a uniform interface, it allows components to scale independently and evolve without breaking existing integrations. Rather than prescribing a specific wire protocol or data format, REST defines an abstract model—most commonly realized over HTTP using URIs, standard methods, and media types like JSON or HTML—to keep distributed interactions loosely coupled and predictable.

    Common Forms

    • Hypertext Web Applications: The original REST model, in which browsers fetch HTML representations over HTTP and follow embedded hyperlinks and form controls to advance application state.

    • Resource-Oriented JSON APIs: Programmatic interfaces that map domain entities to hierarchical URIs and manipulate them with HTTP verbs (GET, POST, PUT, PATCH, DELETE) and status codes.

    • Hypermedia-Driven APIs (HATEOAS): Machine-readable services using formats such as HAL, Siren, or JSON-LD that embed relational links inside payloads so clients discover valid next actions dynamically.

    • Layered and Cached Services: Distributed architectures that route stateless requests through reverse proxies, API gateways, or CDNs using Cache-Control and ETag headers to reuse representations safely.

    Example

    When a customer opens an order page, the client sends a stateless GET /orders/4829 request with an Accept: application/json header and receives a 200 OK JSON representation containing the order details, an ETag cache validator, and hypermedia links for valid actions. To update the shipping address, the client submits a PATCH /orders/4829 request carrying only the updated representation and authorization token, enabling any backend server or intermediary cache to handle the transition without stored session state.