REST Architecture - ABO - Reference Guides

Back Office Integration Guide

Reference Guides
Target Audience

The Antidot web services rely on a REST application server.

REST (Representational State Transfer) is more an architectural design rather than a protocol or a language. It is defined with resources which are uniquely identified with URIs (Uniform Resource Identifier). It matches three main conventions:

  • Functions are split into resources.
  • Exchanges are client/server oriented, without any status nor layer.
  • Data can be stored in caches.

A resource designates any object which can be identified, named, and handled through its representations. The RFC 2396 defines a resource as follows:
"A resource can be anything that has identity. Familiar examples include an electronic document, an image, a service (e.g., "today's weather report for Los Angeles"), and a collection of other resources."
For more information, see

Resources are handled (read, modified, created, deleted) with "verbs" describing the action to perform. The client and the server communicate and share a representation of the resources. The representation format can be XML, HTML, JSON, or else.