This is a mandatory attribute in NDC schema. The service will not validate what is being passed in Version.
Specifies the agent’s preferred language. Service response will be returned in this language
If the requested language is not supported by BA or if this is not passed in the request then the default language will be used, which is English
Specifies the preferred language in which the mail to be sent. eTicket receipt email and any other communication emails from BA will be sent in this language
Note: AltLangID will not be used even if it was passed in the SeatAvailability request, as there is no email sent at the shopping stage. If the requested language is not supported by BA or if this is not passed in the request then the default language will be used, which is English
<-- SeatAvailability request for specific flight segments -->
<Offer OfferID="OF-cb5944be-ec20-40a3-8e96-ab39a80f0edb" Owner="BA" ResponseID="tx-08-201-6cdf9c20-2a01-44ce-8b12-05fab6aad26e">
Core Service Price query parameters.
This section will vary based on when the service is called
Initial booking flow [Purchase Seat along with Flight]
The clients can pass only the OfferID and ShoppingResponseID and the service will retrieve the corresponding details from the offer storage system. The seat map for specific flight segments can also be requested with a short sell request
Post-Sale [Purchase Seat after the booking is created]
The client can either query just with OrderID/PNR/Booking Reference [OR] with OrderID/PNR/Booking and specific flights in the booking
Reference to the OfferID of the selected Offer returned in a previous OfferPrice response.
Reference to unique shopping session response ID, as returned in the airline's previous OfferPrice response.
Reference to the segment for which seat maps are required. The absence of this element is equivalent to an all-segments request.
Requested flight segment needs to be part of the offer stored in the offer storage system
Traveller’s details (FQTV) may be used in determining the seat price. Service will validate the FQTV’s provided and will consider FQTV details to determine seat price only if it is valid.
If a service receives a request for more than one passenger with various FQTV tier status, the service will work out the highest tier status amongst them and return seat price based on the highest tier.
Service return warning message for each FQTV that is not valid with an FQTV number.
For Short Sell Only
The Service will validate the Traveller’s details provided with that of the OfferPrice. It is necessary to pass all travellers details for whom the seat map is requested. The number of passengers and the passenger type in the request needs to match with the number of passengers and passenger type passed in the OfferPrice.
FQTV details will not be accepted when the service is called in a post-sale scenario.
For Post-Sale scenario, this section may not be required, as the service will work out the passenger details from the booking.