Skip Navigation

Multi Flight Availability

1.0.0
Air
Inventory
SOAP API
Travel Agency

Not Signed In.

Looks like you may not have access to all of the resources and documentation for this page.
Please log-in or contact your support desk team if you believe you should have access.

The Multi Flight Availability (MultiFlightXmlRQ and MultiFlightEdifactRQ) API is used to request air availability for multiple flights simultaneously.

As defined, the MultiFlight Request can be sent in and EDIFACT request or an XML request. The type of message being sent needs to be identified in the “Action” element of the message header by using corresponding Action Code

Target Audience
Travel Agency
API Version
1.0.0
Authentication
Session or Sessionless Tokens
Service Action Code
MultiFlightXmlRQ / MultiFlightEdifactRQ

Important! A Sabre Account Director must approve the use of this API before credentials can be provided.

This is a flight-specific API that requires the details of each flight (carrier/flight number/date/city pair) in the request. The system will then respond with all booking classes and the availability of each.

Notes:

  • All flights/carriers can be requested.
  • Leg/segment availability or market-based (Origin/Destination) can be requested.
Sample Request
<!--  MultiFlightRQ can be used to request availability for single flight, multiple flights of a single Origin-Destination pair, or multiple flights of multiple Origin-Destination pairs for a specific agency  -->
<MultiFlightRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1" xsi:noNamespaceSchemaLocation="MultiFlightXmlRQ.xsd">
<!--  RequestOriginDestinationItemType – a group of itineraries of the same origin-destination  -->
<!--  1 or more repetitions: -->
<!--  "origin" – optional – defines the first origin of an Itinerary. The location should be IATA notation.     Example: DFW  -->
<!--  "destination" – optional – defines the final destination of an Itinerary. The location should be IATA notation.  Example: KRK  -->
<OriginDestination origin="DFW" destination="FRA">
<!--  RequestItineraryType – defines the itinerary which consists of 1 or more segments from first origin to final destination)  -->
<!--  1 or more repetitions of itineraries of the same origin-destination  -->
<Itinerary>
<!--  1 or more repetitions of Segment in the same Itinerary  -->
<!--  RequestSegmentType – defines flight segment -->
<!--  "origin" – required – defines the board point of the flights being requested. The location should be IATA notation.  Example: DFW  -->
<!--  "destination" – required – defines the off point of the flights being requested. The location should be IATA notation.  Example: KRK  -->
<!--  "carrier" – required – airline code of the flight being requested  -->
<!--  "marketingCarrier" – optional – marketing airline code of the flight being requested if it is different from the carrier  -->
<!--  "departureTime" – required – time when flight departs from the board point in HHMM format  -->
<!--  "arrivalTime" – required – time when flight arrives at the off point in HHMM format  -->
<!--  "flightNumber" – required – flight number 1-4 digits  -->
<!--  "marketingFlightNumber" – optional –  marketing flight number 1-4 digits  -->
<!--  "departureDate" – required – date when flight departs from the board point in YYYYMMDD format  -->
<!--  "arrivalDate" – required – date when flight arrives at the off point in YYYYMMDD format  -->
<!--  "segmentId" – required – sequential segment ID within the itinerary (connection)  -->
<!--  "classCodes" – optional – a list of valid booking classes for the flight schedule segment  -->
<!--  "resolveIndicator" - optional - polling indicator BoolYNType format  -->
<Segment origin="DFW" destination="FRA" carrierCode="AA" departureTime="1610" arrivalTime="0835" flightNumber="70" departureDate="20151220" arrivalDate="20151220" segmentId="1"/>
</Itinerary>
</OriginDestination>
<!--  AgentInfo – required  -->
<!--  "agentCityCode" – required - Agent City Code – location  -->
<!--  "agencyPcc" – required – Agent Pseudo City Code  -->
<!--  "agencyIata" – optional – Agent ARC/IATA Travel Agency Registration Number if not provided default to 99999999 -->
<!--  "crsPartitionCode" – required – Agent GDS e.g. 1S for Sabre; 1U for ITA  -->
<!--  "currencyCode" – optional – Agent currency code – if omitted, it will be determined from Agent location  -->
<!--  "agentCountry" – required – Agent Country code  -->
<AgentInfo agentCityCode="MUC" agencyPcc="3YMB" agencyIata="99999999" crsPartitionCode="1S" currencyCode="EUR" agentCountry="DE"/>
<!--  0 or 1 "PointOfCommencement"  -->
<!--  "cityCode" – required – City/airport of the first origin of the itinerary  -->
<!--  "departureDate" – required – departure date of the first flight of the itinerary – format YYYYMMDD  -->
<!--  "departureTime" – optional – departure time of the first flight of the itinerary = format HHMMT  -->
<PointOfCommencement cityCode="DFW" departureDate="20151220" departureTime="0750"/>
<!--  0 or 1 AssociateItem – requested Sabre hosted carrier - if requesting for multiple airlines (Sabre hosted and non-Sabre hosted) please omit this data  -->
<!--  "carrierCode" – required – single Sabre hosted airline code, e.g. EY if requested for only for EY flights  -->
<AssociateItem carrierCode="AA"/>
</MultiFlightRQ>
Sample Response
<MultiFlightRS version="1" returnCode="0" returnMessage="OK">
<!--  "version" – required – interface version  -->
<!--  "returnCode" - Return Code. Gives information if the request was handled correctly. Success-"0", anything else ERROR.  -->
<!--  "returnMessage" Return Message. Gives detailed information about the error that occurred while processing the request. Returns OK on success.  -->
<!--  ReponseOriginDestinationItemType – a group of itineraries of the same origin-destination  -->
<!--  1 or more repetitions: -->
<!--  "origin" – optional – defines the first origin of an Itinerary. The location should be IATA notation.     Example: DFW  -->
<!--  "destination" – optional – defines the final destination of an Itinerary. The location should be IATA notation.  Example: KRK  -->
<OriginDestination origin="DFW" destination="FRA">
<!--  ResponseSolutionType – defines the itinerary which consists of 1 or more segments from first origin to final destination)  -->
<!--  1 or more repetitions of itineraries of the same origin-destination  -->
<Itinerary>
<!--  1 or more repetitions of Segment in the same Itinerary  -->
<!--  ReponseSegmentType – defines flight segment -->
<!--  "origin" – required – defines the board point of the flights being requested. The location should be IATA notation.  Example: DFW  -->
<!--  "destination" – required – defines the off point of the flights being requested. The location should be IATA notation.  Example: KRK  -->
<!--  "carrierCode" – required – airline code of the flight being requested  -->
<!--  "flightNumber" – required – flight number 1-4 digits  -->
<!--  "departureDate" – required – date when flight departs from the board point in YYYYMMDD format  -->
<!--  "segmentId" – required – sequential segment ID within the itinerary (connection)  -->
<!--  "returnCode" – optional –  -->
<!--  "values" – optional – a list of availability status of the booking classes  -->
<!--  "classes" – optional – a list of valid booking classes for the flight schedule segment  -->
<!--  "polled" - optional - true availability indicator (if the segment was polled) -->
<Segment origin="DFW" destination="FRA" carrierCode="AA" flightNumber="70" departureDate="20151220" segmentId="1" returnCode="0" values="7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7" classes="F,P,A,J,R,D,I,Y,B,H,K,M,L,V,G,S,N,Q,O" polled="Y"/>
</Itinerary>
</OriginDestination>
<!--  0 or 1 ResponseAssociateItem – requested Sabre hosted carrier if present in the request  -->
<!--  "carrierCode" – required – airline code  -->
<!--  "returnCode" – optional  -->
<AssociateItem carrierCode="AA"/>
</MultiFlightRS>