Skip Navigation

Retrieving Regular Reservations

The /dcci/passenger/details service should be used to retrieve the data of the Passenger processed with Digital Connect Check-In services. This service provides information about Passengers, their itinerary and other details of the reservation. The data collected by using the /dcci/passenger/details service can be used to pass a Passenger through a check-in process. Most Digital Connect Check-In services work on the data retrieved by the /dcci/passenger/details service so this service is usually a mandatory step for each flow (as longs as the data are not already stored in cache - refer to Retrieving data from cache).

Reservation Search Criteria

The /dcci/passenger/details service can be called by using several search criteria which allow retrieving desired Passenger or reservation:

  • Record Locator
  • First Name
  • Last Name
  • Email Address
  • Departure Airport
  • Arrival Airport
  • Departure Date
  • Airline
  • Flight Number
  • Phone Number
  • Tour Operator Booking Reference
  • Passenger's identifier (e.g. Passport number, driver's license number, etc.).

To find a reservation all above criteria can be used in any combination. Found reservation can contain multiple Passengers which means that when looking for a reservation using only reservation criteria, all Passengers in this reservation will be returned. To retrieve only particular Passengers from the reservation the following Passenger criteria should be used to narrow the results:

  • First Name
  • Last Name.

Additionally, Airport Agents can use specific identifiers to retrieve Passenger's information:

  • Bag Tag Number
  • SSCI Passenger ID.

Alternate Search Criteria

When the given criteria do not return any results when looking for a reservation, especially when the criteria are very restricted e.g. with Form Of Identification (FOID). It forces the customer to provide less rigorous criteria that gives more chances to find the reservation. To avoid multiple calls to the /dcci/passenger/details service with different criteria, Digital Connect Check-In allows to include alternate search criteria in the request message.

The /dcci/passenger/details service allows to search for the passenger's reservation using multiple criteria. However, using too many criteria or making a typo in one of them might return no search results.

Therefore, Digital Connect Check-In supports a functionality of 'alternate search' when the first-choice criteria do not find any reservation. In such case the 'alternate criterions' are used.

The alternate search can be executed under few circumstances:

  • Basic criteria search ends up with no results
  • Both basic and alternate criteria are defined in the request
  • Alternate criteria are different comparing to the basic criteria

Alternate Search Request

In order to enable the alternate search criteria functionality an additional element alternateReservationCriteria needs to be put in the request. Alternate search criteria can be defined in the same way as the basic criteria e.g. the user can search for a reservation by record locator, passenger first/last name etc.

Example

{
  "reservationCriteria": {
    "passengerIdentification": {
      "number": "300007423344",
      "type": "FREQUENT_FLYER"
    }
  },
  "alternateReservationCriteria": {
    "recordLocator": "YPADXN"
  }
}

 

If the alternate search is applied and successful, then the response contains the appropriate warning notifying about it in the response. The alternate search returns a response which is the same as the response which would be returned by the basic criteria defined in the same way (except the additional warning). Passenger criteria which can also be specified in the request are not impacted by the alternate search functionality.

Example

"results": [
    {
        "designator": {
            "value": "res1",
            "context": "RESERVATION"
        },
        "status": [
            {
                "type": "SUCCESS"
            },
            {
                "message": "Reservation(s) found based on the alternate search criteria.",
                "code": "ALTERNATE_SEARCH_CRITERIA_USED",
                "type": "WARNING"
            }
        ]
    }

 

Alternate Search Criteria Validation

The validation part of the alternate search functionality detects a case where a user puts the alternate search criteria in the request, but the basic search criteria are missing. In this case an appropriate validation error is raised.

Example

{
    "status": "Unknown",
    "type": "Validation",
    "errorCode": "ERR.DCCI.REQUEST_VALIDATION",
    "timeStamp": "2021-01-11T16:32:58",
    "message": "Invalid request: Alternate search criteria should exist along with a basic search criteria."
}

 

There is also another check during the alternate search which detects a case that the basic and the alternate criteria are the same. In this case no warning is returned however the alternate search criteria are ignored.

Search by FOID - Enhancement

Return FOID in / passenger/ details Response

Digital Connect Check-In /passenger/details allows search of the reservation using different criteria. One among them is FOID.
The FOID must be included in the retrieved results as it makes it easier to check the passenger who requested for the document.
This functionality will work whenever /passenger/details response is returned. And, both unique and non-unique lookup will be supported.


Configuration Reference
This feature need is not available by default.
The following key is introduced to support this feature:

  • s4ci.feature.passengerDetails.requestedSearchCriteria.enabled

For more details refer to the Configuration Index chapter.