Relativity REST API architecture

Using RESTful architectural conventions, the REST API provides you with the ability to access functionality available through the Services API. The REST API passes requests to the Services API, which handles all interactions with the Relativity business engine. You must set up and configure the Services API before you can use the REST API. For information about supported services, see Relativity Server APIs.

The REST API uses named pipes to communicate with the Services API. This communication method offers a fast, in-memory service connection designed to minimize latency in calls made between the two services. Since the system uses named pipes on a localhost, the REST and the Services endpoints must be located on the same machine. Relativity has made significant performance improvements to Services API ensuring that a fast and efficient connection exists between the services. The following diagram illustrates the interconnections between the REST and Services APIs.

In addition, the REST API requires a connection to the Relativity (EDDS) database, which it uses only to load configuration data.