Air Pricing with Passenger Types
Air Pricing requests (LFS) can be modified to return fares for specific passenger types using Passenger Type Codes (PTC).
By default, air requests assume that all passengers are Adults. However, additional passenger types can be entered. Passenger types can indicate a number of circumstances, including age, companion status, organizational affiliation, and need for special assistance. For some age-related passenger types, such as Child, Infant, or Senior, a corresponding Age attribute may also be required.
Typically, IATA PTC values are three characters (ADT, SRC, CNN, INS, etc.) but several of the Low Cost Carriers use non-standard codes that could be up to five characters.
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.
Request
Passenger Types are identified through attributes of the AirPriceReq/SearchPassenger.
The following attributes of SearchPassenger indicate the passenger type and usage.
- Code is the Passenger Type Code (PTC) specified by IATA. If no PTC is specified, the default is Adult ('ADT').
-
A corresponding Age value may be required for certain age-related passenger types, such as Child, Infant, or Senior.
-
An optional PricePTCOnly attribute indicates whether the request for a specific PTC can be relaxed in the response.
-
'True' returns flight options and prices only for the passenger type(s) specified in the request.
Note: Some suppliers do not support unrelaxed passenger types. In this case, an error indicating one or more suppliers is returned.
- 'False' (default) may return default ADT fares if no fares for the requested PTC exist, or if the ADT fare is lower.
-
-
AccompaniedPassenger allows children, infants, and any other accompanied passenger types to be accurately priced separately. For example, if passengers are paying with separate forms of payment, the fares need to be filed individually to support paying with separate forms of payment.
Note: Worldspan and ACH do not support AccompaniedPassenger, and it is ignored if it is sent in the request.
-
AirReservationLocatorCode allows the ability to price an already existing Reservation. When sending a request with an AirReservationLocatorCode, the PTC code in your AirPrice request must match the PTC code that is in the PNR.
Response
A standard Air Pricing response is returned for flights and price options that are valid for the specified PTCs. The Passenger Type is indicated in AirPriceRsp/AirPriceResult/AirPricingSolution/AirPricingInfo/PassengerType and is tied to a specific flight segment. If multiple passengers are reflected in the PTC FareBreakdown, a SearchPassenger element is returned for each passenger, even though they are exactly the same.
The AirPricingSolution reflects the total of all passengers for that flight segment and is calculated by taking the fares for each passenger type and multiplying the fare by the number of SearchPassenger elements for that PTC. If a fare basis code is missing for the child or infant, the fare basis code for the adult within that AirPricingSolution is used.
If the PricePTCOnly attribute is set to 'True' in the request, only the specified PTCs are priced. However, if the PricePTCOnly attribute is set to 'False' in the request, flights and price options for the default Adult ('ADT') passenger type may also be returned.
Exceptions
ACH
For a more complete list of functionality available from various ACH carriers, see ACH Carriers Functionality. Because functionality for carriers may be subject to change, always confirm functionality directly with the ACH carrier before implementation.
- Most Low Cost Carriers via ACH do not support the PricePTCOnly attribute. If PricePTCOnly is set to 'true' for an LCC, a warning message may be returned.
- Most Low Cost Carriers via ACH support only adult (ADT), child (CHD or Cnn), and infant (INF) passenger types.
- Some ACH suppliers support only the ADT passenger type and map CHD, CNN, and INF to ADT.
- When an unsupported passenger type is mapped to ACH as 'ADT', the type is reflected as one of the types in the ADT PricingInfo.
- Depending on the supplier, child passenger types CNN, Cnn (for example, C13), and INS may be mapped to CHD with a warning message.