Specify NDC schema message version. Always pass 17.2
Note: This is a mandatory attribute in NDC schema. The service will not validate what is being passed in this attribute
Specifies the agent’s preferred language. Service response will be returned in this language
Note: 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 OfferPrice 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
To get a price quote using long sell, the client should use this tag to provide details.
As it is mandatory in the schema, the client should pass any text to this element. BA is not validating this value.
Should be always set to 'BA'
Offer item type
Details for all the flight items
Origin and destination (O&D) details. This must be repeated for each O&D. If the request is for EDI-AMS return then this must be repeated twice once for EDI-AMS and once for AMS-EDI
List of flights within an O&D. If the request is for EDI-AMS return with each O&D containing 2 flights (EDILHR and LHRAMS; AMSLHR and LHREDI) then for each O&D Flight should be repeated twice once for EDILHR and once for LHRAMS
Departure airport IATA code
Local Departure date i.e. local to the departure location
Arrival airport IATA code
Marketing carrier information
Marketing carrier code
Marketing flight number
Booking/Selling class details
Reference to a fare basis code for all passenger types for this flight segment
The service expects the client to provide fare basis code in OfferPriceRQ in order to quote correct fare product
It is recommended that the same reference returned in AirShoppingRS is provided in OfferPriceRQ
More than one fare basis code should be separated by a space
To request OfferPrice with particular Fare preference
For long sell scenarios the Fare preference should be set to the desired Fare code so that the agent gets the Upsell fare products of choice returned in the OfferPrice response, instead of the Cheapest fare currently returned. If there is no FarePreference set, the cheapest fare will be returned.
Fare type with a preference level
Should be set with the code for Fare type
Example: 759 or 758 or 70J or 70G
When an agent asks for 70J or 70G or 758, he would get the priced offer and upsell offers for the same fare product type in the OfferPrice response.
This should always be set in case of Leisure Fare type
Tour Operator Deferred
Tour Operator Semi-Deferred
Private Fare Adult
As part of the ongoing commitment to improving British Airways New Distribution Capability, we are pleased to announce an enhancement to our Tour Operator fares. From April 2019, British Airways will offer two separate Tour Operator products:
Tour Operator Deferred – Longer Ticketing Time Limit
Tour Operator Semi Deferred – Shorter Ticketing Time Limit
The earlier-ticketing, Semi-Deferred fares will be differentiated only by their name from the Deferred Fares in NDC. In line with the existing process, agents who wish to book a British Airways Leisure fare product must specify the name as part of the AirShopping request. To book one of the new products agents must use either “Tour Operator Deferred” or “Tour Operator Semi Deferred” in the Fare Preference section of the API.
This change only impacts the AirShopping and OfferPrice APIs. No further changes are required in order to book the products.
List of all passengers with Passenger type code (PTC)
If applicable, FQTV detail is required to determine lead in seat price
Young adult DOB is required as UK Air Passenger Duty (APD) is not applicable to “young adults” aged 12 to 15 years inclusive for travel after 1 March 2016
Specify ResidenceCountryCode if known as it would help decide the applicable payment cards. Applicable payment cards are decided based on the agent’s country and customers billing country. If the customer’s billing country is not specified then applicable payment cards will be returned based on agents country only