Examples of Representational State Transfer

From Wikipedia, the free encyclopedia

This article is orphaned as few or no other articles link to it.
Please help introduce links in articles on related topics. (October 2006)

The following are public examples of Representational State Transfer interfaces.

Since REST is defined very broadly, it is possible to claim an enormous number of RESTful applications on the Web (just about everything accessible through an HTTP GET request or updateable through HTTP POST). Taken more narrowly, in its sense as an alternative to both Web Services generally and the RPC style specifically, REST can be found in many places on the public Web:

The 'blogosphere' — the universe of weblogs — is mostly REST-based, since it involves downloading XML files (in RSS, or Atom format) that contain lists of links to other resources;
The Atom Publishing Protocol for publishing to blogs is considered the canonical RESTful protocol;
Amazon.com's S3 is their only truly REST offering;
OpenStreetMap offers a REST interface;

There are also examples of interfaces that label themselves 'REST', but are, in fact, using HTTP to tunnel function calls - also known as 'POX/HTTP', or Plain Old XML over HTTP:

Amazon.com offers a 'REST' version of its main 'E-Commerce' developer interface;
eBay offers a 'REST' developer interface;
Facebook offers a 'REST' developer interface;
Yahoo! offers a number of 'REST' developer interfaces.
Youtube offers a number of 'REST' developer interfaces.
Newscloud offers a number of 'REST' interfaces.

Some of these interfaces do not intentionally respect REST's architectural constraints. Some have been called Accidentally RESTful, by a REST expert. The accident of RESTfulness occurs primarily when standalone GETs are appropriate, i.e. when it's not appropriate to navigate through many GETs in hypermedia style, and when those GETs simply retrieve data and do not change it.