ItineraryPrice 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.

Prices booked (present in PNR) air segments.
Applicable to GDS only at this time. 3 types of pricing are supported:
- as booked (with the same classes of service as booked)
- Best Buy - cross class low fare pricing
- Alternate itineraries - suggests (where possible) alternate itineraries for the journey booked in PNR (in this case the response will also show the recommended flights in the ItineraryPriceRS/FareGroup/OriginDestination section). Corresponding GDS equivalents are Sabre - WPNI, Apollo - $BBQ, Worldspan - 4PLI

Restrictions: Can only be used with systems as listed below:
Amadeus, Sabre, Apollo, Worldspan.
Version number. 0..1 1.0
PNR record locator. If provided here PNR will be retrieved by this value as the first step in the internal process.0..1
Allows the tailor the search and pricing parameters. If omited - defaults are used where applicable. For instance default pricing is - based on the classes of service as booked, all passengers in PNR and all air segments.0..1
Restricts the type of fare being requested. If omited system defaults will be used as defined on the respective GDS. Values are:
PUBL = published fare
NEGO = negotiated/private fare
BOTH = published and negotiated fares

This flag controls the behavior of the pricing logic.
Possible values are:
A = get Alternate itineraries for the one booked on the PNR.

Y = get the best fare available in the same cabin class
C = get the best fare available across all cabin classes (not supported on Sabre and Worldspan)

N = price accordingly to the other parameters in the PricingInfo group (regular pricing with classes as booked).

Default = N

[A] [N] [C] [Y] 0..1 Y
For systems which support alternative fare / ticketing flows for low cost carriers (such as LightTicketing on Amadeus), specifies whether alternative flows shall be suppressed.

Values are:
Y = Yes,
N = No.
[Y] [N] 0..1 Y Default: N
Reference to a Traveler element this PricingInfo is to be applied to.

If no TravelerIDRef is specified, the PricingInfo is applied to all Traveler.

0..N T1
ID reference used to asscociate this item to a segment. No comma separeted lists and no ranges supported. 0..N F1
Pricing restrictions group0..1
Allow fares with minimum stay requirement. Values are:
Y = Yes
N = No
Default: Y
[Y] [N] 0..1 N
Allow fares with maximum stay requirement. Values are:
Y = Yes
N = No
Default: Y
[Y] [N] 0..1 N
Allow fares with advance requirement. Values are:
Y = Yes
N = No
Default: Y
[Y] [N] 0..1 N
Allow fares with penalty restrictions. Values are:
Y = Yes
N = No
Default: Y
[Y] [N] 0..1 N
Corporate information group1
Specifies the corporate account number to use to price private fares. 1 000243
Requests Account Code fares. Values are:
Y = Request Account Code only
N = Request Account Code and Published Fares
[Y] [N] 0..1 Y


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