Digital Connect Stateless services are defined using Remote Procedure Call (RPC), a programming pattern for communicating between two systems in a distributed network. It requires a service operation name as well as request and response objects for remote service invocation. RPC API services perform actions sent by client requests. Applicable results are sent back to the client in the form of a response. Request and Response are JSON objects. 

RPC operations are specified as the last element in the endpoint URL. All API operations are intuitive names, formatted in camel-case notation, and are meant to be self-explanatory of its purposes. 

Examples:

/exchanges/getFlights 
/exchanges/priceAncillaries 
/seats/add 

Sabre RPC API endpoints are implemented by DC Stateless Services with no notion of a client session. The processing state can be handled on the client-side, which means that the client should be responsible for sending any state data to the service whenever needed.