Flight Details

Flight Details, also known as Flight Service or In-Flight Services, returns scheduled flight information, including origin, destination, departure time, arrival time, flight time, travel time, meals, and additional information.

Flight Details is an optional, stand-alone transaction that is typically performed after a Low Fare Shopping or Air Pricing request to obtain additional information about the flights in an itinerary.

Schema

See the following transactions for Flight Details:

• FlightDetailsReq
• FlightDetailsRsp

How To

1. Use FlightDetailsReq to make a Flight Details request. The request should include the following Air Segment data:

• Key

• Group

• Carrier

• FlightNumber

• Origin

• Destination

• DepartureTime

2. FlightDetailsRsp returns a Flight Details response. The availability and types of Flight Details returned vary by carrier and segment. The availability of real-time data versus scheduled data may also vary by carrier and segment. Available response data may include:
   • Departure and arrival times for direct flights and non-stop flights for all segments.

   If an airline does not support this, a message is returned in the response: "Airline not supported".

   Note: These details are returned when available regardless of whether the request contains a date.

   • Flight details for each leg in the flight itinerary:
     • If an air segment has two or more legs, the Flight Details for each leg are returned.
     • If the air segment has a single leg, Flight Details for the single segment are returned.
   • Universal API provides the ability to include ALL in-flight services in the Flight Details response.

   • Prior to Air v48.0, the flight service information display did not return the codeshare operating carrier and flight number in the flight service response, preventing agents from understanding the carrier on which the Minimum Connect Time (MCT) was based. Release 19.1

     • Air v48.0 provides users with the carrier code and flight number for the operating carrier of a codeshare agreement (DEI 50).

       • The DEI 50 carrier code is used as the default carrier for MCT processing and is found in the *SVC response.

       • By allowing the codeshare carrier and flight number in the flight service response, users can respond to questions and problems both pre- and post-departure without having to call Travelport to obtain the data.

       • FlightDetailsRsp/AirSegment @CodeshareInfo

         • OperatingCarrier

         • OperatingFlightNumber

     • Prior to Air v48.0, the CodeshareInfo attribute contained within the FlightDetails element had a Max Occurrence of 0. Thus, when the FlightDetailsReq is sent for a flight, which has multiple legs and different operating carrier for each leg, the response was unable to show all operating carriers.

       • With Air v48.0, in order to show the CodeshareInfo for each leg for flights where multiple legs exist, customers must request the legs individually until such a time that the system is updated to return codeshare information at a segment level.

       • Segment-level codeshare is expected in a future release.

       • Codeshare and operating carrier information returns in the Flight Details Response for Air.xsd v49 and above in FlightDetailsRsp/AirSegment @CodeShareInfo. Release 23.4 For example:
         <air:CodeshareInfo OperatingCarrier="MH" OperatingFlightNumber="611">MALAYSIA AIRLINES BERHAD</air:CodeshareInfo>

   • FlightDetailsRsp indicates whether automated check-in is allowed and if a flight is a TSA-secured flight: Release 21.2

     • If the FlightDetails element returns @AutomatedCheckIn="true", the flight allows automated check-in. Default is "false".

     • Prior to Universal API release 21.2.2, the InFlightService list returns a value of TSA SECURED FLIGHT if a flight was a TSA-secured flight, and used exclusively for flights to, from, within, and over the United States (US).

     • With Universal API release 21.2.2 and later, the Secure Flight Indicator may be used by airlines globally when there is a government mandate to collect additional passenger information.

     • The enhancement with Release 21.2.2 improves the accuracy of the Transportation Security Administration (TSA) informational message by replacing the specific United States based text, "TSA Secured Flight," with a general statement, "ADDITIONAL PASSENGER DATA REQUIRED," and is now allowed to be used by any airline on any flight.

   • Air.xsd returns carbon emissions data in FlightDetailsRsp/CO2Emissions.

   • The @InFlightServices may include:

     IATA Code	New Description
     1	Movie
     2	Telephone
     3	Telex
     4	Audio Programming
     5	Television
     6	Reservation Booking Service
     7	Duty Free Sales
     8	Smoking
     9	Non-smoking
     10	Short Feature Video
     11	No Duty Free Sales
     12	In-seat Power Source
     13	Internet Access
     14	E-Mail
     15	In-seat Video Player/Library
     16	Lie-Flat seat
     17	Additional service(s) exist
     18	WI-FI
     19	Lie-Flat seat first
     20	Lie-Flat seat business
     21	Lie-Flat seat premium economy
     99	Amenities subject to change

Exceptions

Worldspan

Worldspan does not support ClassOfService in the request.

ACH

ACH does not support the Flight Details transaction.