Air Availability by Cabin Class

Air Availability requests can be modified to request availability by the cabin class (class of service). Supported cabin classes can vary by provider or supplier. Universal API supports the following cabin classes:

Universal API does not differentiate between preferred and permitted cabin class. Cabin class preferences are supported at the segment level for Air Availability. Also see Air Pricing by Cabin Class for details on pricing a specified cabin class.

Schema

Located in Air.xsd:

Request

  1. Enter the minimum required data for the AvailabilitySearchReq.
  2. Request specific cabin classes using SearchAirLeg/AirLegModifiers:

    3. Requests availability for the selected cabin classes.

    If that class is not available, an alternate cabin may be returned. Depending on availability and processing, either a cabin downgrade or upgrade may be offered.

    Requests availability only for the selected cabin class. A maximum of three cabin classes can be requested.

    If that class is not available, no additional options are returned in the response.

    Note: Universal API does not currently support ProhibitedCabins for Air Availability requests.

Response

The AvailabilitySearchRsp returns a Air Availability response that is filtered for the preferred or permitted cabins. If no cabin class was specified in the request, the default response returns all cabin classes. If the requested class is not available and the PreferredCabins modifier was sent in the request, other classes may be returned. For example, a request for First class, may contain responses for Business or Coach if the segment does not offer First.

Cabin class data for each air availability solution is included in AirSegmentList/AirSegment/AirAvailInfo/BookingCodeInfo@CabinClass.

Universal API references and validates cached cabin class data on the provider and assigns a cabin class for each booking code returned for each carrier in the response.

If a cabin class is not supported by Universal API, the default is 'Economy'.

Note:The cached cabin class reference data will not be validated for ACH carriers.

Exceptions

Galileo supports only one requested cabin class. Only the first cabin class is processed; any additional cabin classes are ignored.

Apollo supports only one requested cabin class. Only the first cabin class is processed; any additional cabin classes are ignored.

  • Worldspan allows only one preferred cabin in the request.
  • Worldspan supports Booking Code modifiers, but does not support direct Cabin Class requests. If a cabin class request is made, the following warning is returned: Best fares for the requested cabin class may not have been returned. Please use booking code search.
  • Worldspan does not support:
  • Premium First class.
  • First Availability search.

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.

  • ACH supports requests by cabin class (First, Business, Economy) at journey level, and the permitted ("Only" modifier) cabin. Many of the Low Cost Carriers (LCCs) that supply ACH do not support preferred cabin classes. If a requested cabin class is not available, the response returns all flight and pricing options, and the following message: May not support the requested cabin class.
  • If multiple CabinClass elements are sent in the request, ACH only uses the first element.
  • If ACH is provisioned, a Low Fare Search request is performed and consolidated into the AvailabilitySearchRsp.
  • ACH does not support "Premium" fields.

Rail Content Service distributor data is not returned in AvailabilitySearchRsp.