TimeTable request message

Tabular overview of all nodes, which may occur in this message. See legend below for description of table columns.
Note: Some sibling elements or complete sub-trees of the hierarchy may be defined as mutually exclusive alternative choices. This information cannot be expressed in this tabular overview. Please refer to schema diagram for a graphical representation of the message schema.

NodeDescriptionValuesOccursExample
<TimeTableRQ>
TimeTable RQ1
@version
Version number. 0..1 1.0
<GeneralFlight>
General flight group for non airline or flight specific TimeTable requests1
<Preferences>
Preferences group0..1
<Airline>
Airline preference group1
<Include/>
Airline code for carriers to be included in the search. Maximum 3 or ATA/IATA airline codes to use as connection. 1 airline code: AF
<Exclude/>
Airline code for carriers to be excluded in the search. Maximum 3 or ATA/IATA airline codes to use as connection. 1 airline code: AF
</Airline>
</Preferences>
<DepartureCityCode/>
Departure city code. 1 LHR
<ArrivalCityCode/>
Arrival city code. 1 JFK
<DateWindow>
Date window group for time table search by date range Note: Not all GDS support this feature - see GDS limitations section1
<StartDate/>
Time table date range start date in ISO 8601 format (yyyy-mm-dd).
1 2001-12-25
<EndDate/>
Time table date range end date in ISO 8601 format (yyyy-mm-dd).
1 2001-12-30
</DateWindow>
<TimeWindow>
Time window group for time table search by time range. Note: Not all GDS support this feature - see GDS limitations section1
<StartTime/>
Time table time. Range start time in ISO 8601 format (hh:mm). 1 09:00
<EndTime/>
Time table time. Range end time in ISO 8601 format (hh:mm). 1 17:00
</TimeWindow>
<DayOfWeek/>
Day of week. Valid values are: 1, 2, 3, 4, 5, 6, 7 for each day of the week starting 1=Monday, 2=Tuesday, 3=Wednesday, 4=Thursday, 5=Frinday, 6=Saturday, 7=Sunday. Note: Not all GDS support multiple DayOfWeek requests. Check GDS Limitations section. 1 237 or 1234567
</GeneralFlight>
<SpecificFlight>
Specific flight group for airline specific and/or flight specific Time table requests. Some GDS do not support flight number specific requests - check GDS limitations.1
<Carrier>
Carrier group for airline and flight number1
<AirlineCode/>
Airline code. 1 UA
<FlightNumber>
Flight number - an integer value within the range of [0,9999].

1 1234
@Suffix
Flight number alpha qualifier.
Values are:
A
B
C
D

[A] [B] [C] [D] 0..1 A
</FlightNumber>
</Carrier>
<Departure>
Departure group for specific time table request1
<CityCode/>
City code. 1 LHR
<Date/>
Time table specific request date in ISO 8601 format (yyyy-mm-dd).
1 2001-12-25
<Time/>
Departure or arrival time in ISO 8601 twenty-four hour clock format. 0..1 14:00
</Departure>
<Arrival>
Arrival group for specific time table group1
<CityCode/>
City code. 1 LHR
<Date/>
Time table specific request date in ISO 8601 format (yyyy-mm-dd).
0..1 2001-12-25
<Time/>
Departure or arrival time in ISO 8601 twenty-four hour clock format. 0..1 14:00
</Arrival>
<ClassOfService>
Specific CRS may require a valid class of service to be specified to be able to retrieve the time table for specific flight.

0..1 Y
</ClassOfService>
</SpecificFlight>
<MoreFlightsToken/>
Token used to request more flights following a previous response. This token is sent back in the previous response while in other cases it could contain the Y (yes) or N (no) indicator.
1 124523467899 or Y
</TimeTableRQ>

Legend

ColumnDescription
NodeName of message node (element or attribute). Nodes in bold type are mandatory, if their parent element occurs in the message. Point mouse cursor at table cell to view complete XPath.
DescriptionDescription of meaning and usage of the node.
ValuesList of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema.
OccursMinimum and maximum number of times the node must/may occur, if its parent element occurs in the message. Examples:
0..3 Node is optional and may occur up to 3 times.
1..N Node must occur at least one (mandatory) and may occur any number of times.
2 Node must occur exactly twice.
ExampleExample value for the node.

XML Schema documentation generated with XX/1 server