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

Hotel information request root element

If a BookingCode is given, the rate information details will be returned. If not, only the hotel informations will be returned.

Additional information re usage of CurrencyCode:
At least on Apollo/Galileo systems it might be needed to add CurrencyCode to the request since some hotel system file rates so that the rules/information can only be retrieved when currency is included. Example is chain MC.
Version number. 0..1 1.0
ISO language code. A two letter code as defined by ISO-639-1. This code specifies the requested language for text content. Default value is 'en'.0..1
Sale information group0..1
City code. 0..1 MIA
Country code. 0..1 US
Currency code. 0..1 USD
Decimal position in fare amount. 1 2
Check in date in ISO 8601 format (yyyy-mm-dd). This is the date the customer will arrive (check-in) at the hotel.
1 2002-12-25
Check out date in ISO 8601 format (yyyy-mm-dd). This is the date the customer will depart (check-out) the hotel.
1 2002-12-31
Number of nights.
0..1 5
Total number of persons in party incl. children.
[1] to [9]1 1
Group of child elements defining age and bedding type (optional) for each child.0..1
Child elements - one per requested child.1..N
Age of child in years (allowed values are 0-17).
The age should be specified for the date of the hotel checkin.
[0] to [17]1
Defines if child will need its own bed ('Y') or sleep in parents bed ('N'). If omitted no extra bed is required.[Y] [N] 0..1
Hotel property chain code.
0..1 MC
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.
Specifies whether information comes from vendor system or GDS database.
The value 'CacheOrSource' is generic (not provider-specific). Currently it is used by Amadeus Web Service.

Possible values are:

CacheOrSource .. data from cache or source

ASA .. Amadeus standard access
ACA .. Amadeus complete access
ACP .. Amadeus complete access plus
ADY .. Amadeus dynamic access
AIA .. Amadeus independent access

GIA .. Galileo inside availability link
GIP .. Galileo inside shopper participant
GRM .. Galileo roommaster only participant
GLP .. Galileo link partner

SDC .. Sabre direct connect sell
SOL .. Sabre other link type

WSV .. Worldspan hotel source vendor
WAP .. Worldspan hotel select vendor access plus
WNP .. Worldspan hotel select vendor non-access plus

HRS .. HRS internal hotels
HRSEXT .. HRS external hotels

HBC .. direct access hotels

On systems which support cached results (ex. Pegasus) the source of the results can be determined by the following values:
- Source
- Cache

[CacheOrSource] [ASA] [ACA] [ACP] [ADY] [AIA] [GIA] [GIP] [GRM] [GLP] [SDC] [SOL] [WSV] [WAP] [WNP] [HRS] [HRSEXT] [HBC] [Cache] [Source] 1 ASA
Hotel property code.
1 MIA345
Hotel booking code. 0..1 A1SRA8
Rate amount.
0..1 10000
Currency code. 0..1 USD
Decimal position in fare amount. 1 2
Alternate currency code.
0..1 GBP
CD Number.
0..1 Unknown
Rate access code. This is a special code corresponding to a negotiated rate.
0..N IBM
Rate category. Possible values:
ASN = Association
CLB = Club
CON = Convention
COR = Corporate
DAY = Day room
FAM = Family
GOV = Government
MIL = Military
NEG = Negotiated
PKG = Package
PRO = Promotional
RAC = Standard RAC
SPE = Special
SRS = Senior citizen
STP = Stopover
TUR = Tour
TVL = Travel industry
WKD = Weekend
[ASN] [CLB] [CON] [COR] [DAY] [FAM] [GOV] [MIL] [NEG] [PKG] [PRO] [RAC] [SPE] [SRS] [STP] [TUR] [TVL] [WKD] 0..1 GOV
City code. 0..1 MIA
Only one element per distinct extra bed type allowed0..N
Number of extra beds for this type1
Type of extra bed
[AdultRollAway] [ChildRollAway] [Crib] 1


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