Sabre® technologies can be accessed in a Tier 1 layer (a web/presentation layer) that offers capabilities such as configuration management, session management, and cache management.

Digital Connect Check-In offers state of the art services that allow Airline to create a presentation layer of modern applications. By using Digital Connect Check-In Airlines can:

• Build native applications.

• Integrate external content.

• Cross-sell features.

The following principles guide the architecture of the Digital Connect Check-In API:

• Uniform interfaces – the API provides an interface between client side and server side that simplifies and decouples the architecture. This enables the client side and server side to independently evolve.
• Client/server relationship between Digital Connect Check-In services and their consumers - the interfaces are backward compatible which allows both client side and server side actors to be independently developed and replaced.
• Server side state management – it enables greater flexibility since the server is maintaining, updating, or communicating the session state.
• A layered system – adherence to the preceding principles facilitates the use of intermediary (hardware) servers which further improve system scalability by enabling load-balancing and providing shared caches. It also facilitates enforcement security policies.
• Cacheable – it reduces server processing time and improves scalability and performance.

API-first Design with OpenAPI Specification

Digital Connect Check-In uses API-first design with an OpenAPI Specification which is in line with the current, backward compatible Digital Connect Check-In APIs.

By default, Digital Connect Check-In API Specifications are released as OpenAPI Specification 2.0 (known as Swagger v2) with 'allOf'-based composition. On demand they can be also delivered as OpenAPI Specification 3.0.x with the disabled composition in both JSON and YAML formats.

Reservation model

Digital Connect Check-In services refer to the Reservation model that you can find under res.Reservation model.