Digital Connect Check-In supports the Inter Airline Through Check-In (IATCI) flights within the check-in flows.

E2E Flow Example

Getting Passenger Details

The POST /dcci/passenger/details service returns itineraryPart/segment/flightDetail/iatci set to 'true' when the given flight is IATCI and the IATCI feature is turned on for a given storefront.

Supplementing the Passenger Details with IATCI Related Information

The Agent facing applications need to collect as many data as possible about the Passenger's details. If a Passenger's travel continues with IATCI segment, then the collecting data, specifically for such segment, needs to be handled in a specific way. Getting the Passenger details for an IATCI segment involves communication outside the Sabre systems using the EDIFACT standards.

Notes   

• The IATCI functionality is enabled for a given Digital Connect Check-In instance.
• The Passenger is checked-in on a given IATCI flight.
• The IATCI flights connects directly or indirectly to at least one hosted flight.

The v2/dcci/passenger/supplement Service

The v2/dcci/passenger/supplement service refreshes Digital Connect Check-In Passenger details stored in the session and additionally can supplement it with requested details (currently only IATCI details are supported). A client can specify a list of Passenger segment IDs for which they would like to get the IATCI details. If no includeIatciDetails is provided, then the service executes the same logic as in the GET v2/dcci/passenger/refresh service. It means calling the POST v2/dcci/passenger/supplement service without any body is equivalent to calling the GET v2/dcci/passenger/refresh service.

Request

If a Passenger is related to an infant, both Passengers' details are supplemented with the IATCI data no matter which passengerSegmentId is given in the request. The IATCI data are fetched only for the unique and eligible passengerSegments specified in the request by a client.

{
    "includeIatciDetails": 
    {
        "passengerSegmentIds": ["p01.01.s2", "p01.01.s3", "p03.01.s2"]      
    }
}

Request Validation

The purpose of the request validation is to check and inform an Agent at the very beginning of the process whether the IATCI functionality is properly configured. In case the IATCI functionality is disabled and the Agent requests for IATCI data, then the request validation error is raised. In the error message the Agent is informed that the IATCI functionality needs to be configured (enabled).

Data Mapping

Results

Level	Type	Message
PASSENGER_SEGMENT	WARNING	Passenger not checked-in on IATCI segment
PASSENGER_SEGMENT	WARNING	PassengerSegment does not refer to an IATCI segment
PASSENGER_SEGMENT	WARNING	Unable to return IATCI flight information due to missing IATCI details in downline response
PASSENGER_SEGMENT	WARNING	Unable to return IATCI flight information due to a communication error
PASSENGER_SEGMENT	WARNING	Unable to return IATCI flight information due to an internal error
RESERVATION	WARNING	An internal error occurred while retrieving IATCI details

Example results in the response

{
    "results": [
        {
          "designator": {
            "value": "p02.01.s3",
            "context": "PASSENGER_SEGMENT"
          },
          "status": [
            {
              "message": "PassengerSegment does not refer to an IATCI segment",
              "type": "WARNING",
              "code": "UNABLE_TO_RETURN_IATCI_DATA"
            }
          ]
        },
        {
            "designator": {
                "value": "p01.01.s2",
                "context": "PASSENGER_SEGMENT"
            },
            "status": [
                {
                    "message": "Passenger not checked-in on IATCI segment",
                    "type": "WARNING",
                    "code": "UNABLE_TO_RETURN_IATCI_DATA"
                }
            ]
        }
    ]
}

Configuration Reference

The following keys are introduced to support this feature:

• s4ci.feature.passengerDetails.iatci.enabled
• s4ci.feature.common
• se.adapter.s4ci.configuration.reservationConfiguration.retrieveDetailedInformationEnabled
• se.adapter.s4ci.configuration.reservationConfiguration.excludedCodes
• s4ci.feature.passengerDetails.paxSegStatus.enabled

For more details refer to the Configuration Index chapter.