REST

An architectural style for networked software built on named resources, representations of their state, stateless requests and a uniform interface.

In more detail

REST stands for Representational State Transfer and was described by Roy Fielding in 2000. It is a family of constraints, not a route template: having JSON and URLs does not make an API RESTful. Its strengths are that caches, proxies and ordinary HTTP tools understand it, which is why it fits broad public web boundaries.

Related terms

Taught in

References

Certification courses