API Information

Response Format
XML
Service Action Code
AirSchedulesAndAvailabilityRQ
Current Version
5.3.1
Target Audience
TN
Environment
Production
Documentation
Go to the Air Schedules And Availability documentation

What's New

  • The request now contains a new element providing calendar search for the same market for 1 to 40 consecutive days.
  • The request now contains additional element providing the option to search for specific flights (pairs of carrier code and flight number).
  • The response now includes the base date of each response block.
  • The interpretation of format date has changed from only the same day (as per current UTC time at time of receiving the request) to allowing up to three last days to be interpreted as current year.

Business Value

  • Customer can now perform calendar search for the same market for 1 to 40 consecutive days.
  • Customer can now perform calendar search for specific flights.

New Features

In the Request

Optional

Parameter: Calendar

Type:

Description: Enables calendar search functionality

Sample Value:

<Calendar origin="JFK" destination="LAX" startDate="2020-02-20" days="14" />
Note: If this element is used, the same request cannot contain any //OriginDestination elements - this is reflected in the schema. Use of this element does not change the response layout.
Parameter: SpecificFlight

Type:

Description: Restricts the results to contain segments with specific marketing carrier and flight number pairs

Sample Value:

<SpecificFlight><Segment marketingCarrier="1S" flightNumber="1234" /><Segment marketingCarrier="1S" flightNumber="2345" /></SpecificFlight>
Parameter:

Type:

Description:

Sample Value:

In the Response

Required

Parameter: baseDate

Type: string

Description: Contains the base search date of that specific OriginAndDestination.

Sample Value:

baseDate="2020-02-20"

Resolved Issues

In the Request

Required

The service will now interpret the short date format falling on the last three days to be on current year, instead of defaulting them to next year. As an example if a request is sent on 2019-08-15, the service will interpret short date formats "08-13", "08-14", as 2019-08-13 and 2019-08-14. The previous functionality would interpret the short dates as first future date which would mean "08-13", "08-14" to be interpreted as year 2020. This change was made to alleviate issues with client time-zones.

Optional