Versions Compared

Old Version 14

changes.mady.by.user Alvaro Chaparro

Saved on

compared with

New Version 15

changes.mady.by.user Alvaro Chaparro

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Release 2024.04

...

This service is used to get the seat map for the flight segments referenced in the request. Note that depending on whether you request this in the pre-sale or post sale flow you will reference the Offer or the Order accordingly.

Insert excerptAPI Messages with ExamplesAPI Messages with ExamplesnameLegendnopaneltrueWe provide two different methods to request the seat availability:

  • Pre-Sale: Requires a previous OfferPrice

  • Post-Sale: Requires a previously created and paid Order.

The various search parameters are described below:

Insert excerpt
API Messages with Examples
API Messages with Examples
nameLegend
nopaneltrue

Common Sections

Expand
titleHTTP Header

HTTP Header

Insert excerpt
HTTP Header
HTTP Header
nameHTTP Header
nopaneltrue

...

In addition to the Common Sections the main parts of the request message are the following:

Query

Expand
titleCurrency / Metadata
Insert excerptCurrency MetadataCurrency Metadata
Expand
titleQuery

Insert excerpt
Query (Pre-Sale & Post-Sale)
Query (Pre-Sale & Post-Sale)
nameQuery_presale
nopaneltrue

Insert excerpt
Query (Pre-Sale & Post-Sale)
Query (Pre-Sale & Post-Sale)
nameQuery_postsale
nopaneltrue

Metadata / Currency

nameCurrencyMetadata

nopaneltrue

Example SeatAvailabilityRQ:

Expand
titleExample Pre-Sale flow
Code Block
languagexml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.iata.org/IATA/EDIST/2017.2">
   <soapenv:Header/>
   <soapenv:Body>
      <SeatAvailabilityRQ Version="5.000" PrimaryLangID="es" xmlns="http://www.iata.org/IATA/EDIST/2017.2">
         <PointOfSale>
            <Location>
               <CountryCode>ES</CountryCode>
            </Location>
         </PointOfSale>
         <Document>
            <ReferenceVersion>5.000</ReferenceVersion>
         </Document>
         <Party>
            <Sender>
               <TravelAgencySender>
                  <Name>NDC Agency Name</Name>
                  <Contacts>
                     <Contact>
                        <EmailContact>
                           <Address>pruebas@pruebas.com</Address>
                        </EmailContact>
                        <PhoneContact>
                           <Application>MOBILE</Application>
                           <Number CountryCode="+34">666666666</Number>
                        </PhoneContact>
                        <Name>
                           <Surname>Perez</Surname>
                           <Given>Pepe´s</Given>
                        </Name>
                     </Contact>
                  </Contacts>
                  <OtherIDs>
                     <OtherID>XXXXXXXX</OtherID>
                  </OtherIDs>
                  <AgencyID>XXXXXXXX</AgencyID>
               </TravelAgencySender>
            </Sender>
            <Participants>
               <Participant>
                  <AggregatorParticipant SequenceNumber="1">
                     <AggregatorID>XXXXXXXX</AggregatorID>
                  </AggregatorParticipant>
               </Participant>
            </Participants>
         </Party>
         <Query>
            <Offer OfferID="IB378316b7a7924aafad62e2ce8f478942OP" Owner="IB" ResponseID="Qm9va2luZ0BHVy0xNjUxMDYzNTc4MDI5LThQMzQ3">
            <SegmentID>IB310220231018</SegmentID>
            </Offer>
         </Query>
      </SeatAvailabilityRQ>
   </soapenv:Body>
</soapenv:Envelope>

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

Error messages

For further information about all kind of error messages, please go to the following link:

...