ProfileRetrieve 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
<ProfileRetrieveRQ>
Profile retrieve request root element. It will allow to retrieve multiple profiles (Traveler and/or Company profiles)1
@DisplayType
How to return multiple profiles.

U = unmerged
M = merged (default)
[U] [M] 0..1
<ProfileIndex>
The profile index of the desired traveler and/or company profile.

1..N 5251 1234
@PIN
Security ID to access requested profile. Mostly used on agency portals.

0..1 1234
@Type
Type of profile to retrieve. Values are:

C = Company profile
T = Traveler Profile
[T] [C] 0..1
@PseudoCityCode
Pseudo city code. This PCC has ownership of the profile.
0..1 LNJ2
</ProfileIndex>
</ProfileRetrieveRQ>

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