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.
| Node | Description | Values | Occurs | Example |
|---|---|---|---|---|
<NameListRS> | Name List response root element | 1 | ||
@ActiveOnly | Y=Display Active PNR's only N=Display all PNRs | [Y] [N] | 0..1 | |
<InfoGroup> | Error and information group | 0..1 | ||
<ForInfo> | Information group | 0..N | ||
@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. | |
@SourceRef | PNR Record Locator associated to Source attribute. | 0..1 | ||
@Code | A code to uniquely identify a specific type of ForInfo message. Currently not returned for most ForInfo messages. | 0..1 | I00001 | |
@Lang | ISO language code. A two letter code as defined by ISO-639-1. | 0..1 | de | |
<Text/> | Information text or error text. | 1..N | Free flow text. Example: Invalid flight number | |
</ForInfo> | ||||
<Error> | Error group | 0..N | ||
@ErrorType | Type of error. | 1 | Air | |
@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. | |
@SourceRef | PNR Record Locator associated to Source attribute. | 0..1 | ||
<Code/> | Error code or equipment type code. | 1 | 0104 (error code), 747 (equipment code) | |
<Text/> | Information text or error text. | 1..N | Free flow text. Example: Invalid flight number | |
<UnderlyingError> | Errors of the backend system can be returned here. | 0..N | ||
@Code | error code of the backend system. | 0..1 | ||
<Text/> | Information text or error text. | 0..N | Free flow text. Example: Invalid flight number | |
</UnderlyingError> | ||||
</Error> | ||||
<BackOffice> | Generic back office response container. Serves as a placeholder for any context specific content. | 0..1 | ||
</BackOffice> | ||||
</InfoGroup> | ||||
<ListHeader> | Request data mapped into the response (required only for Sabre). | 0..1 | ||
@ActiveOnly | [Y] [N] | 0..1 | ||
<Surname/> | Traveler family (last) name. | 1 | SMITH | |
<GivenName/> | Traveler given (first) name. | 0..1 | JANE | |
<Date> | Date in ISO 8601format (yyyy-mm-dd). | 0..1 | 2001-12-15 | |
<Day/> | 0..1 | |||
<Month/> | 1 | |||
<Year/> | 1 | |||
</Date> | ||||
<CRS/> | 0..1 | |||
<OfficeCode/> | 0..1 | |||
</ListHeader> | ||||
<ListRS> | List of Responses | 1..N | ||
<Index> | Group of PNR-Items | 1 | ||
@ItemCount | Count of Items returned | 1 | ||
<Item> | PNR-Item | 1..N | ||
@Status | Status, if Item is active or cancelled | [A] [X] | 0..1 | |
<Number/> | Item number in the index | 1 | ||
<Name> | Namegroup | 1 | ||
<Surname/> | 1 | |||
<GivenName/> | 1 | |||
</Name> | ||||
<ItineraryStartDate/> | Itinerary start date in ISO 8601 format. | 0..1 | 2001-12-25 | |
<DepartureCode/> | 3LC for Departure in first segment | 0..1 | ||
<ArrivalCode/> | 3LC for Arrival in first segment | 0..1 | ||
<Vendor> | Vendor data for first segment | 0..1 | ||
<Code/> | Vendor Code e.g. LH=Lufthansa | 1 | ||
<FlightNumber/> | Flight number when vendor type = A (Airline) | 0..1 | ||
<Name/> | Vendor Name e.g. United Airlines | 1 | ||
<Type/> | Vendor Type: A=Airline, C=Car, H=Hotel, X=Unrecognized | [A] [C] [H] [X] | 1 | |
</Vendor> | ||||
<RecordLocator/> | RecordLocator of the PNR Item. Will be returned for all CRS except Sabre. For Sabre, the RecordLocator will not be returned except for those PNR, which are at the same time retrieved as a whole as /NameListRS/PNRViewRS elements (because they lie within the range specified with /NameListRQ/@Begin and /NameListRQ/@End). This is a Sabre system limitation. | 0..1 | ||
</Item> | ||||
</Index> | ||||
</ListRS> | ||||
<PNRViewRS/> | Please see PNRViewRS or TicketImageRS documentation for further details. | 0..N | ||
</NameListRS> |
| Column | Description |
|---|---|
| Node | Name 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. |
| Description | Description of meaning and usage of the node. |
| Values | List of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema. |
| Occurs | Minimum 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. |
| Example | Example value for the node. |
XML Schema documentation generated with XX/1 server