This article is part of an Essential Guide, our editor-selected collection of our best articles, videos and other content on this topic. Explore more in this guide:
3. - Must-know: Key API terms : Read more in this section
- REpresentational State Transfer
Explore other sections in this guide:
- 1. - API management: What you need to know
- 2. - The latest with APIs: Trends and effective use cases
REST (REpresentational State Transfer) is a simple stateless architecture that generally runs over HTTP.
REST involves reading a designated Web page that contains an XML file. The XML file describes and includes the desired content.
REST is often used in mobile applications, social networking Web sites, mashup tools and automated business processes. The REST style emphasizes that interactions between clients and services is enhanced by having a limited number of operations (verbs). Flexibility is provided by assigning resources (nouns) their own unique universal resource indicators (URIs). Because each verb has a specific meaning (GET, POST, PUT and DELETE), REST avoids ambiguity.
As described in a dissertation by Roy Fielding, REST is an "architectural style" that basically exploits the existing technology and protocols of the Web, including HTTP (Hypertext Transfer Protocol) and XML. REST is simpler to use than the well-known SOAP (Simple Object Access Protocol) approach, which requires writing or using a provided server program (to serve data) and a client program (to request data).