Affiliation information
Last updated
Last updated
Although OpenTravel allows unlimited occurrences of each element within the OTA_HotelDescriptiveContentNotifRQ message, Enterprise Connectivity has elected to set limits for many of these elements. Unless specified under the Usage column below, ENTERPRISE CONNECTIVITY only allows one instance of each element per property message.
Element
Level
Attribute
R
O
C
G
D
S
Example
Usage
Description
AffiliationInfo
3
O
Only 1 element allowed per Property message.
Awards
4
C
Required when
AffiliationInfo element is present and LoyalPrograms element is not present.
Element
Level
Attribute
R
O
C
G
D
S
Example
Usage
Description
Only 1 element allowed per Property message.
Award
5
R
Required when Awards element is present.
Removal
O
true false
If not specified, false is assumed.
Date
O
2004-10-15
Date
Reflect the date the award was given.
Provider
R
Dallas
Chamber of
Commerce
100 Char
Max: 200 bytes
Name of provider who gave award.
Required for Award element.
Rating
C
4 Stars
100 Char
Max: 200 bytes
Hotel rating.
Example: “3 Stars – Star
Magazine, 2 Circles - Circle
Magazine”
Note: Input of the
American Auto Association (AAA) trademarks and references to diamond ratings is prohibited by AAA. If found an error will be returned.
Only Required when action code is add or Overwrite = true
Only 1 rating per provider attribute allowed. If more than one is present, an error will be returned.
Rating is a multi-lingual attribute.
LoyalPrograms
4
C
Required when
AffiliationInfo element is present and Awards element is not present.
LoyalProgram
5
R
Can repeat more than once if the property participates in more than one program (but the ProgramName must be unique).
ProgramName
O
64 Char
Max 128 bytes
Loyal programs name, e.g. “La Quinta Returns”
HotelLevel
O
16 Char
Max 32 bytes
The level/tier that the hotel participates in the loyalty program. This may affect the number of ‘points’ received for a stay or the number of points required to redeem free nights.
Examples:
B” (level B)
“2” (Level 2)
“Tier 2”
Schema design view
Example transaction