OfferPrice RQ - OfferPrice 17.2 Request Specifications
Technical Documentation

OfferPrice RQ

DATA MODEL

Request Definition

<OfferPriceRQ> 
<OfferPriceRQ Version="17.2" PrimaryLangID="EN" xmlns="http://www.iata.org/IATA/EDIST">
Element Details optional 
Version attr

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

 M 
PrimaryLangID attr

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
Example: EN

 O 
AltLangID attr

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

 O
<Document>
Element Details optional 
<Document>
 NDC Message Document information M 
<Name>
 Document name will be always "BA" O
<Party>
Element Details optional
<Party> Party & Sender Definition M
<Query> (Long Sell)   
<OrderItem>
    <OfferItemID Owner="BA">Offer1</OfferItemID>
    <OfferItemType>
        <DetailedFlightItem>
            <OriginDestination>
                <Flight>
                    <Departure>
                        <AirportCode>HEL</AirportCode>
                        <Date>2018-08-11</Date>
                    </Departure>
                    <Arrival>
                        <AirportCode>LHR</AirportCode>
                    </Arrival>
                    <MarketingCarrier>
                        <AirlineID>BA</AirlineID>
                        <FlightNumber>0799</FlightNumber>
                    </MarketingCarrier>
                    <ClassOfService refs="FBCODE1ADT">
                        <Code>N</Code>
                    </ClassOfService>
                </Flight>
            </OriginDestination>
        </DetailedFlightItem>
    </OfferItemType>
</OrderItem>
Element Details optional 
<OrderItem>
 To get a price quote using long sell, the client should use this tag to provide details. M 
<OfferItemID>

As it is mandatory in the schema, the client should pass any text to this element. BA is not validating this value.

Example: Offer1

M

 
Owner attr

Should be always set to 'BA'

 M 
<OfferItemType>
 Offer item type M 
<DetailedFlightItem>
 Details for all the flight items M 
<OriginDestination>
 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 M 
<Flight>
 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 M 
<Departure>
 Departure details M 
<AirportCode>

Departure airport IATA code

Example: LHR		 M 
<Date>

Local Departure date i.e. local to the departure location

Example: 2015-07-01		 M 
<Arrival>
 Arrival details M 
<AirportCode>

Arrival airport IATA code

Example: AMS		 M 
<MarketingCarrier>
 Marketing carrier information M 
<AirlineID>

Marketing carrier code

Example: BA		 M 
<FlightNumber>

Marketing flight number

Example: 0428		 M 
<ClassOfService>

Booking/Selling class details

 M 
refs attr

Reference to a fare basis code for all passenger types for this flight segment

Examples: FBCODE1ADT

FBCODE1CHD

FBCODE1INF

Notes:

  1. The service expects the client to provide fare basis code in OfferPriceRQ in order to quote correct fare product
  2. It is recommended that the same reference returned in AirShoppingRS is provided in OfferPriceRQ
  3. More than one fare basis code should be separated by a space
 M 
<Code>

Booking/Selling class

Example: O		 M
<Query> (Short Sell) 
<Query>
      <Offer OfferID="OF-3749b7c1-ddcb-455c-9f46-394e64307387" Owner="BA" ResponseID="tx-08-201-d3d410b5-e707-4469-8b24-b747531ea9a0">
         <OfferItem OfferItemID="OF-3749b7c1-ddcb-455c-9f46-394e64307387-OI-1">
            <PassengerRefs>T1 T2</PassengerRefs>
         </OfferItem>
         <OfferItem OfferItemID="OF-3749b7c1-ddcb-455c-9f46-394e64307387-OI-2">
            <PassengerRefs>T3</PassengerRefs>
         </OfferItem>
      </Offer>
</Query>
Element Details optional 
<Offer>

To get a price quote using short sell, the client should use this tag to provide details.

M

 
OfferID attr

This is the OfferID returned in AirShoppingRS for the offer the client wishes to book

M

 
Owner attr

This should be always passed as ‘BA’

M

 
ResponseID attr

This is the ResponseID returned in AirShoppingRS for the offer client wish to book

M

 
<OrderItem>

This will contain the OfferItem associated with Offer returned in AirShoppingRS.

M

 
<OfferItemID>

The client should pass the OfferItemID that is returned in AirShoppingRS for the selected offer
Example: OF-3749b7c1-ddcb-455c-9f46-394e64307387-OI-1

   
<OfferItemID>

The client should pass the OfferItemID that is returned in AirShoppingRS for the selected offer
Example: OF-3749b7c1-ddcb-455c-9f46-394e64307387-OI-1

M

 
<PassengerRefs>

Should be a reference to Passenger (s) for the selected OfferItemIDExample – P1 P2
Note – Number of passenger and passenger type should match to the ones passed in AirShopping.

 M
<Preferences> 
<Preference>
    <FarePreferences>
        <Types>
            <Type PreferencesContext="Contract Bulk">758</Type>
        </Types>
    </FarePreferences>
</Preference>
Element Details optional
<Preference> To request OfferPrice with particular preference O
<FarePreferences> To request OfferPrice with particular Fare preference O
<Types> Fare type with a preference level O
<Type>

Should be set with the code for Fare type
Example: 759 or 758

 M 
PreferencesContext attr

This should always be set in case of Leisure Fare type

Example:

  1. Tour Operator Deferred
  2. Tour Operator Semi-Deferred 
  3. Contract Bulk
  4. Private Fare Adult
  5. Marine
  6. Humanitarian
 

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:

  1. Tour Operator Deferred – Longer Ticketing Time Limit
  2. 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.  

Here is an XML sample for the two products:

<Type PreferencesContext="Tour Operator Deferred">758</Type>
<Type PreferencesContext="Tour Operator Semi Deferred">758</Type>

The Leisure Fare is assigned to the 'PreferencesContext' attribute within the 'Type' element.

 

 

 

 O
<DataLists>
Element Details optional 
<PassengerList>

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
 O 
<FareList>

Fare basis code for each passenger type for each flight  segment should be provided in this section

Notes:

  • It is recommended that the same reference returned in AirShoppingRS is provided in OfferPriceRQ
Long Sell 
  • The service expects the client to provide fare basis code in OfferPriceRQ in order to quote correct fare product
 O






 

Working on it ...

Subscribe to Notifications

Get notified when this page gets updated, subscribe to our page notifications service.

email Address Invalid eMail address
Frequency

Subscribe to Notifications



Thank you. Please confirm your subscription by clicking the link in the email we have just sent.

If you have not received the confirmation email click here to Resend