Air Booking with Price Adjustments

Air bookings are created using the results from an Air Pricing response. In an Air booking, the total price can be adjusted by a flat amount or a percent. The adjustment can be applied at both the PTC level and the per passenger level. A Traveler association to the adjustment must be provided, or the adjustment is assumed for all travelers of that PTC.

Schema

Located in Universal.xsd:

How To

  1. Include the minimum required information for creating an air booking.

  2. Add one or more price adjustments using AirCreateReservationReq/AirPricingSolution/AirPricingInfo/Adjustment and AirCreateReservationReq/AccountingRemarks.

    Include the following information:

    • Adjustment @AdjustedTotalPrice

    • Adjustment/Amount or /Percent. Both values can be positive or negative. A negative amount or percent means that the Total Price has been discounted.

    • Adjustment @BookingTravelerRef

      Single Passenger PNR

      For a single passenger PNR request with a stored fare, BookingTravelerRef is not required. However, if BookingTravelerRef is provided in AirPricingInfo/PassengerType, it must also be provided in AirPricingInfo/Adjustment, or an error is returned.

      Multi-passenger PNR

      For a multi-passenger PNR request with one or more stored fares, BookingTravlerRef must be provided in AirPricingInfo/PassengerType. In this case, if AirPricingInfo/Adjustment is present:

      • But Adjustment/BookingTravelerRef is not present, Universal API processes the same adjustment for all passengers associated to that AirPricingInfo element. The BookingTravelerRefs in PassengerType indicate the passengers for which the adjustment is applicable.
      • And BookingTravelerRef(s) is present, the user must check if BookingTravelerRef(s) is a subset or all of the BookingTravelerRef(s) in PassengerType. If there is one or more BookingTravelerRef in the Adjustment element which is not specified in the PassengerType element, an error is returned: Some or all of the BookingTravelers specified in Adjustment do not belong to the AirPricingInfo.

      Multiple Adjustments

      Multiple Adjustments without BookingTravelerRef are not allowed because Universal API can have a single Adjustment applicable for all travelers through AirPricingInfo.

      Multiple Adjustments for a single AirPricingInfo (some with BookingTravelerRef and some without BookingTravelerRef) are mutually exclusive. For example, APInfo1 without BookingTravelerRef with 10% AND APInfo with BookingTravelerRef with 5% are not allowed together. If given, a validation error is returned: Adjustments with and without Traveler association to an AirPricingInfo are mutually exclusive.

      If more than one adjustment is given for the same booking traveler at the time of booking, an error is returned: Multiple adjustment for a Booking Traveler is not allowed.

  3. The values are saved to the Universal Record (UR), then Universal API calculates the approximate adjusted total price based on the default currency from the agency profile, saves the amount in the UR, and returns it in the Air Booking response.