The encyclopedia · Software & IT · Technical decision · 2000–2026
REST made web APIs by reusing HTTP instead of inventing a protocol
Fielding's REST applies a uniform interface over HTTP's own verbs and resources, so anything that already speaks HTTP can call it.
World Wide Web Consortium
the move
Before REST, distributed APIs often meant SOAP and WSDL: heavy XML envelopes, custom schemas and code generators, with every service re-inventing the interface.
In his 2000 dissertation Roy Fielding distilled what made the web scale into an architectural style: resources identified by URI, manipulated through a uniform set of verbs, with self-descriptive messages and no server-held session state.
The decisive move was that the interface was HTTP itself. A browser, a script, a network appliance, anything that already speaks HTTP could talk to a REST service, which is why REST became the default for public APIs.
why it works
- A uniform interface means every resource uses the same verbs, cutting special cases.
- Stateless requests scale, because a server holds nothing between calls.
- Self-descriptive, cacheable messages let intermediaries speed things up for free.
what transfers
When incumbent infrastructure already solves most of the problem, define your interface in its terms instead of building a parallel protocol.
what came after
REST and its HTTP semantics became the default for public APIs, and JSON, itself a subset of JavaScript, became the common payload. The range of meanings people attach to RESTful shows how deeply the idea saturated web development, and it displaced the heavyweight SOAP stack almost everywhere.
references
spotted an error? The archive wants to know.