Skip Navigation

CKI Passenger Update Travel Docs

Basic
Check-In
REST API
Airline Carrier

What is it?

The Update Travel Docs API is part of the Sabre Sonic Check-In product collection, and supports adding, updating, and deleting passenger travel document details. It also supports adding passport and other travel documents that are part of the overall DOCS SSR. Other document types supported include:

  • Visa details
  • Residential address details
  • Contact details
  • Timatic document details
  • Contact information, and more!

Why use it?

Government bodies may require a pre-boarding validation of the passenger by collecting passenger details in advance, and advise the eligibility of the passenger to arrive/depart from their country.

The Update Travel Docs API facilitates this by providing options to accept the passenger's travel document details.

How it works

The Update Travel Docs API supports the following features for a single passenger in a request:

Add, Update, and Delete Travel Documentation

Add, update, and delete passenger travel documentation as required by government authorities:

  • The addition and deletion of documents is managed by the action attribute. This attribute may posses the values EDIT and DELETE for addition and deletion, respectively.

  • Deleting a travel document removes all the associated documents under the same group

Infant and Adult Passenger Options

  • An infant in lap and the associated adult would normally have the same passenger unique identifier (passengerId). However, if the documents are to be submitted for the infant and adult separately, like in the case of a DOCS edit, use the attribute infant, to pass the details of infant. Alternatively, there are some functions where adult and infant requests are triggered together; for example, Timatic Override and Stay Type for Timatic.

  • In the event a passenger is traveling with a lap infant, SSCI assigns the same unique identifier for both. However, if the passenger is traveling with a seat infant, SSCI assigns different unique identifiers for each. In this case, UpdateTravelDocsRQ must be called separately for the passenger and the seat infant. There are some functions where adult and infant requests are triggered together, for example, Timatic Override and Stay Type for Timatic.

  • Travel documents can be added for infants by using the attribute infant. When the value of the attribute is true, the documents are added for the infant.

Other Features

  • Add all travel-related documents and information in a single call (i.e., travel document, visa information, address information, contact information, and information for Timatic clearance)

  • Add up to four (4) travel documents for adult passengers and infants, together

  • Update existing travel document data for a passenger for whom a similar document type was added previously

  • Add up to four (4) visa documents for an adult passenger and infant together

Making a Call

  • If includePassengerDetails is set as true in the request, the response will include the details of all passengers, and details of passenger edits. Otherwise, it will only contain the status of each operation.

  • This API responds with a multi-status HTTP code (207) for error and partial success cases. The status can be identified by the status returned in the response.

How to use

With Update Travel Docs, passengers can add or delete travel documentation through your application.

To update these travel-related documents, passengers must first be able to enter the information below into your application:

  • Flight details:
    • Airline code
    • Flight number
    • Departure city
    • Departure date
  • Passenger details:
    • Passenger ID
    • Last name

Below are some best practices to keep in mind when making calls to this API:

Travel Document List

  • travelDocumentList contains a list of travel document details, along with the EDIT and DELETE action codes. Infants may be included under this option.

Visa Documentation

  • Visa documentation will be overwritten if new and existing country codes are the same.
  • New visa documentation will be created if the country is different.
  • Visas for up to four (4) countries can be added in a single request.

Known Traveler List

Known Traveler numbers refer to the unique IDs assigned to passengers participating in Known Traveler Programs, also known as Trusted Traveler Programs. These can be entered in for passengers using knownTravelerList, and can be added or deleted with the EDIT or DELETE action codes, respectively.

Redress Numbers

  • Request a redress number for a passenger if unfairly delayed, prohibited from boarding an aircraft, or entering a sterile area as a result of a DHS program.
  • You can also delete the existing redress number by setting the action as DELETE.

Destination Addresses and Contact Information

  • Multiple destination addresses can be added or deleted.
  • Passenger contact information can only be added or deleted for adults.

Timatic

The use of Timatic AutoCheck enables airlines and ground handlers to automate passenger travel document compliance for international travelers. Timatic document details for passengers and associated infants can be added together.

Additional information could also be found