NameList 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
<NameListRQ>
Name list request root element1
@version
Version number. 0..1 1.0
@Begin
Specifies the position of the first PNR in the item list returned, for which a complete PNRViewRS should be automatically returned as part of the NameListRS.

NOTE: This attribute has to occur in conjunction with the End attribute below.
0..1
@End
Specifies the position of the last PNR in the item list returned, for which a complete PNRViewRS should be automatically returned as part of the NameListRS.

NOTE: This attribute has to occur in conjunction with the Begin attribute above.
0..1
@ActiveOnly
Specifies whether only active PNRs should be displayed (default value is 'Y' - active PNRs only). [Y] [N] 0..1
<Surname/>
Traveler family (last) name. 1 SMITH
<GivenName/>
Traveler given (first) name. 0..1 JANE
<Date>
The travel date.0..1
<Day/>
The day of travel in format DD0..1
<Month/>
The Month of travel in format MM1
<Year/>
The year of travel in format YYYY1
</Date>
<CRS/>
Specifies Central Reservation System the request should be executed against. This parameter makes sense only on Apollo or Galileo because these systems allow cross system searches.0..1
<OfficeCode/>
0..3
<Source/>
Identifies the source of this element. In other words where the content oroginates. Not limited to GDS, applicable to direct conect as well. 0..1 1A, 1V, or other.
</NameListRQ>

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