SeatMap 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
<SeatMapRQ>
Seat availability request root element1
@version
Version number. 0..1 1.0
<FlightData>
Flight Details 1..N
<AirlineCode>
Airline code. 1 AA
@Source
Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. 0..1 1A, 1V, or other.
</AirlineCode>
<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>
<ClassOfService/>
Class of service. 1 B
<DepartureDate/>
Date in ISO 8601 format (yyyy-mm-dd). 1 2002-02-22
<DepartureCityCode/>
Departure city code. 1 MIA
<ArrivalCityCode/>
Arrival city code. 1 JFK
<NumberInParty/>
Number of passengers. 1 2
<FareRefKey/>
Unique fare reference key. If present in pricing response messages, must be included here.0..1
</FlightData>
<PNR>
Use this section to request seat map based on a PNR (booked itinerary). Segment selection is mandatory.1
<RecordLocator/>
PNR record locator (alphanum). On GDS 6 alphanumeric identifier.
1 ABC123
<SegmentIDRef/>
ID reference used to associate this item to a segment. No comma separated lists and no ranges supported. 1..N F1
</PNR>
<CurrencyCode/>
Requested currency for seat prices.

0..1 USD
</SeatMapRQ>

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