Passenger Type Codes (2024)

A passenger type code provides the capability to specify fare related classifications for each passenger. By default, air requests assume that all passengers are Adults. However, additional passenger types can be entered. Passenger types can indicate age, companion status, organizational affiliation, private fare eligible, and need for special assistance, among others. Additionally, there is another type of PTCthat includes personal geo-type and geo-code data. Geo-PTCs define fares you may be applicable to based on your residency, nationality,etc. For example, FBB, which used to specify Spanish Resident -1 discounted adult.

Note: You can send the PTC along with the actual Personal Geography information. For example, in an Air Price request,

<com:SearchPassenger Code="ADR" BookingTravelerRef="1" xmlns:com="http://www.travelport.com/schema/common_v48_0">

 <com:PersonalGeography>

 <com:CityCode>PMI</com:CityCode>

 </com:PersonalGeography>

 </com:SearchPassenger>

 <com:SearchPassenger Code="FBB" BookingTravelerRef="2" xmlns:com="http://www.travelport.com/schema/common_v48_0">

 <com:PersonalGeography>

 <com:CityCode>PMI</com:CityCode>

 </com:PersonalGeography>

 </com:SearchPassenger>

 <com:SearchPassenger Code="FGJ" BookingTravelerRef="3" xmlns:com="http://www.travelport.com/schema/common_v48_0">

 <com:PersonalGeography>

 <com:CityCode>PMI</com:CityCode>

 </com:PersonalGeography>

 </com:SearchPassenger>

 <air:AirPricingCommand/>

</air:AirPriceReq>

Typically, IATA PTC values are three characters (ADT, SRC, CNN, INS, etc.) but several of the Low Cost Carriers use non-standard codes that can be up to five characters.

Note: The attribute AccompaniedPassenger in the SearchPassenger element, when perfoming a Low Fare Shop, is not supported.

Some codes combine alphanumeric values to indicate a passenger type, for example:

• S65 - restricted senior age (65 and older)

Note: Suppliers may vary in their usage of passenger types. For example, the minimum age limit of a senior-restricted fare may vary by supplier.

Commonly used PTCs are as follows:

• ADT: adult
• CHD: child
• INF: infant without a seat
• INS: infant with a seat
• UNN: unaccompanied child

For a full list of PTCs, download the Universal API Reference Data file.

Infant and Child Passengers

To identify a child passenger, use the code CNN followed by the child's two-digit age (e.g., CNN08). Although Worldspan identifies child passengers using the code C followed by 2 digits, the CNN code must be used in Universal API transactions.

As a best practice, an infant passenger name should always follow an adult passenger name in the booking.

• If two adults are traveling with an infant and a child, enter names in the following order:

  1. First adult
  2. Infant
  3. Second adult
  4. Child

• If two adults are traveling with two infants and one child, enter names in the following order:

  1. First adult
  2. First infant
  3. Second adult
  4. Second infant
  5. Child

Encode/Decode for Passenger Type Codes

Reference Data is available for Passenger Type Codes. To obtain the Type code values, send ReferenceDataRetrieveReq TypeCode="PassengerTypeCode".

Handling for Invalid Passenger Type Codes for Imported Galileo and Apollo PNRs

• Invalid PTCs are converted to Adult (ADT) to allow a URto be created.
• Universal API does not validate the provider's PTC against Universal API's Reference Data values for PassengerTypeCode. For PNRs with invalid PTC codes:
  • A Universal Record is created.
  • The invalid PTC code is maintained in the PNR.
  • A warning is not returned.

This issue applies only to Galileo (1G) and Apollo (1V), and does not apply to Worldspan (1P), and Airline Content Hub (ACH).