Open

Seats can be included in an OrderCreate (with or without payment), and held (on hold) with the flights until the PaymentTimeLimit (applicable to the seats) expires, which may be more restrictive than the PaymentTimeLimit for the flights.

Seats can be booked for any individual flight in the Order, but only for those that are operated by Iberia, Iberia Express, AirNostrum and Level.

Previously validated Iberia Plus information is used when getting the seat availability and any advantages or discounts would be applied.

For more information on Iberia Seating product, please see our Early Seat Booking page.

The SeatAvailabilityRQ can be made in the pre-sale flow, before creating the Order with the payment, simply referencing the OfferID in the previous OfferPriceRS, or in the Servicing flow having already booked and paid for the flights, as per the following example:

Note that, unlike other Ancillaries services, the OfferItemID is obtained once the Order has been created. Thus, in the OrderCreateRQ, as shown in the example below:

The SeatAvailabilityRS contains the OfferItems with the price for the referenced passengers and flight segment.

In addition it contains the cabin layout, which tells you how many rows and columns of seats the aircraft has, together with status/occupancy and characteristics of each individual seat linked to the applicable OfferItem with its price.

(The only difference between the messages in Pre-Sale and Post-Sale is that the latter refers to Orders instead of Offers)

The following is a Seats purchase scenario.

There is an OfferItem for each different Seat price applicable to the passenger(s) and flight(s) referenced.

Please note the TimeLimits section that contains the PaymentTimeLimit for any seats booked (on hold). Remember this is independent for the PaymentTimeLimit for the flights. If there is no PaymentTimeLimit for any ALaCarteOfferItem then all of the OfferItems in the Order must be paid for at time of reservation (instant purchase).

Within the SeatMap section you have the CabinType and CabinLayout.

And the Row information with the Status/Occupancy and characteristics of each seat. This references the seats applicable price in the above OfferItem.

For a comprehensive source of codes from the SeatAvailability Messages section, please see the Seat Codes - IATA PADIS Codeset page.

The Ancillaries are included in the OrderCreate using their OfferItemIDs from the previous messages. In this case, two Seats have been booked.

Since these samples are being extracted from the same Flow, we can see that the OfferID is the same reported in the SeatAvailabilityRQ section but related to the OrderCreateRQ (OfferID="IB534dba9c3b8143e19cd453929c4f1720OC"), and so is the OfferItemID (OfferItemID="IB534dba9c3b8143e19cd453929c4f1720OC_01").

The Ancillaries will then be returned in the OrderViewRS as OrderItems with their prices, and with a PaymentTimeLimit when applicable.

And the ServiceDefinition, where we can observe all Ancillaries that are included in this specific example, according to their ServiceDefinitionID, where you can find the details of the Ancillary.

Here is where we put URLs that can be used to link to additional information such as rich media and other useful information for the customer.

Examples of messages with complete flows can be downloaded from here.

Open