SeatAvailability RQ - SeatAvailability 17.2 Request Specifications
Technical Documentation

 SeatAvailability RQ Definition

DATA MODEL

Request Definition

<SeatAvailabilityRQ> 
<SeatAvailabilityRQ 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

This is a mandatory attribute in NDC schema. The service will not validate what is being passed in Version.

 M 
PrimaryLangID attr

Specifies the agent’s preferred language. Service response will be returned in this language
Example: EN

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

 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> - ShortSell (Offer Storage)
 
<-- SeatAvailability request for all flights -->
<Offer OfferID="OF-056566c1-ea06-4e8c-acf0-bbc49dc08e65" Owner="BA" ResponseID="tx-08-201-f7e19798-c640-48e4-ae73-b2d5b66cc649"/>
<-- 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">
    <SegmentID>BA610</SegmentID>
    <SegmentID>BA611</SegmentID>
</Offer>
Element Details optional 
<Query>
  

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

 M 
<Offer>

Offer details

 M 
OfferID attr
 Reference to the OfferID of the selected Offer returned in a previous OfferPrice response. M 
Owner attr
 Example: BA M 
ResponseID attr
 Reference to unique shopping session response ID, as returned in the airline's previous OfferPrice response. M 
<SegmentID>

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		 O
<Query> - LongSell (No OfferStroage) 
<!-- SeatMap by OrderID -->
<Order OrderID="SCMZYO" Owner="BA">
        <SegmentID>BA031</SegmentID>
        <SegmentID>BA036</SegmentID>
</Order>

<!-- SeatMap by Flight -->
<FlightSegment>
    <AirlineID>BA</AirlineID>
      <Departure>
        <AirportCode>JFK</AirportCode>
            <Date>2018-04-30</Date>        
       </Departure>
       <Arrival>
            <AirportCode>LHR</AirportCode>         
        </Arrival>
    <FlightNumber>1511</FlightNumber>
      <ClassOfService>
        <Code>N</Code>
        <!--Agent to pass FBC for Adult-->
        <FareBasisCode>NKN8F7S5</FareBasisCode>
       </ClassOfService>
</FlightSegment>
Element Details optional 
<Query>
  

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 client must specify Flight segments details when the service is called during initial booking flow, as the booking is not created at this stage

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

 M 
<Order> 

PNR/Booking Reference

 

This is an optional element in NDC schema but this must be specified when the service is called in a post-sale scenario.

   
OrderID attr
 The airline-assigned unique Order ID.   
Owner attr
 Will always be “BA”   
<SegmentID>
  

When flight segment details are specified in a post-sale scenario, the service will return priced seat map(s) only for the requested flight segments.

<SegmentID> passed here should match the SegmentKey in FlightSegmentList.

   
<FlightSegment>
  

Prime Sale- Flight segment details for which the seat map(s) are requested. 

 M 
<AirlineID>

Marketing carrier code

Example: BA		 M 
<Departure>
 Departure information 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 information M 
<AirportCode>

Arrival airport IATA code

Example: AMS		 M 
<FlightNumber>

Marketing flight number

Example: 0428		 M 
<ClassOfService>
   M 
<Code>

Booking/Selling class

Example: O		 M 
<FareBasisCode>

Fare basis code

Example: VZ0RIN

 

 O
 
<DataLists>
Element Details optional 
<PassengerList>
  • 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. 
     

 O 
<FlightSegmentList>

If priced seat map(s) is required for specific flight segments in the PNR then Flight segment details to be specified in the request with the following details:

  • Departure Airport code
  • Departure Date
  • Arrival Airport code

  • Flight Number.

     Note: This list is applicable only for the Long Sell request.

 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