Developer Docs
  • Our Products
    • Channel Manager
      • Integration and Onboarding Flow
      • RG Bridge - Supply (Push)
        • Integration Overview
          • Vision of Integration
            • Commercial value and business case
          • Information Data flow
            • One way integration
            • Two Way integration – ARI Broadcast and Reservation fetch
            • Information delivery mechanism
          • Technical feasibility of integration
            • Test property setup
            • Sample reservation data
          • RG Bridge Setup
          • Contract
          • Project Plan
          • Certification
          • Monitoring and after sales support
          • Integration checklist
        • Interface Specifications – Availability and Rates Notification Service
          • RG Bridge Integration Process
          • Intended Audience
          • Typographical Conventions
          • Technical Overview
          • Operations
            • Availability Notification
              • OTA_HotelAvailNotifRQ
                • Change in Inventory count
                • Change in availability status and Restrictions
              • OTA_HotelAvailNotifRS
              • XML Usage Specification
            • Rate Change Notification
              • OTA_HotelRateAmountNotifRQ
              • XML Usage Description
              • OTA_HotelRateAmountNotifRS
              • XML Usage Specification
            • Points to remember
        • Interface Specifications – Reservation Notification Service
          • RG Bridge integration process
          • Intended audience
          • Typographical conventions
          • Technical overview
          • Operations
            • Reservation Notification
              • OTA_HotelResNotifRQ
              • XML Usage specification
              • Sample Reservation Messages
              • OTA_HotelResNotifRS
              • XML Usage specification
          • Points to remember
          • Code Lists
      • RG Bridge - Reservation Retrieval (Pull)
        • Technical overview
        • Operations
          • Reservation Retrieval
            • OTA_ReadRQ
            • XML Usage specification
            • OTA_ResRetrieveRS
            • XML Usage specification
          • Reservation Confirmation
            • OTA_NotifReportRQ
            • XML Usage specification
            • OTA_NotifReportRS
            • XML Usage specification
        • Code Lists
      • Direct Connect - Demand (Push)
        • Introduction
        • Interface Specifications – ARI Service
          • Technical Overview
          • Operation: Property List
            • HotelPropertyListGetRQ
            • HotelPropertyListGetRS
            • Test Use Cases
            • FAQ
          • Operation: Product List
            • HotelProductListGetRQ
            • HotelProductListGetRS
            • Test Use Cases
            • FAQ
          • Operation: ARI Get
            • HotelARIGetRQ
            • HotelARIGetRS
            • Test Use Cases
            • FAQ
          • Operation: ARI Update
            • HotelARIUpdateRQ
            • HotelARIUpdateRS
            • Test Use Cases
            • FAQ
          • Points to remember
          • Code Lists
        • Interface Specifications – Reservation Notification Service
          • Technical overview
            • Communication protocols
            • General design
            • Authentication
          • Operation: Reservation
            • OTA_HotelResNotifRQ
            • OTA_HotelResNotifRS
            • Test use cases
            • FAQ
    • Smart Distribution
      • Onboarding process
      • Certification - Demand
      • Authentication Method
      • Book and Cancel Reservation
        • Transaction Header Formats
        • Book API
          • Book Reservation
          • Cancel Reservation
          • Booking Reservation Request Message Format
          • Booking Reservation Response Message Format
          • Cancel Reservation Request Message Format
      • Multiavailability (Enhanced Shopping Transaction)
        • Transaction Header Formats
        • Enhanced Shopping (EST) – Detailed Rate Information
          • Requesting Specific Rates
          • UltraDirect Account Author Negotiated Rate Processing
          • Unavailable Properties
          • UltraDirect Cache Processing
          • Enhanced Shopping Transaction Request Header Format
          • Enhanced Shopping Transaction Response Message Format
      • Pre-Book
        • Transaction Header Formats
        • Pre Book API
          • Pre-Book Request message format
          • Pre-Book Response message format
      • Property list and Booking Summary
        • PropertyList API
        • Booking Summary API
  • Content
    • Integration Process
    • Certification - Demand
    • Content Retrieve
      • SOAP/HTTP
        • SOAP Envelop
        • SOAP Body
        • Date and Time
        • Specifications for Currency Amounts
      • Transaction Specifications
      • Content Retrieval Request
      • Content Retrieval Response
    • Content Update
      • Overview
      • Transaction List
      • Transaction Flow
      • Batch processing
        • File naming convention
      • Multi-lingual capabilities
      • Associating media to textual content
      • Managing images
      • GDS content updates
      • Office of Foreign Assets Control (OFAC)
      • Interface requirements
        • SOAP envelope
        • Standard element formats
      • Transaction specifications
        • Data mapping of elements
        • Area Information
        • Affiliation information
        • Media information
        • Contact information
        • TPA extensions
        • GDS information
        • Response message
      • Codes lists
        • Credit Card
        • Error and Warning codes
        • Spoken Language
        • State and Country
      • Supported language codes
      • Client application generation using WSDL tool
  • UltraDirect
    • Integration Process
    • Certification
    • Ultradirect transaction sets - XML
      • Transaction header formats
      • Booking transactions
        • Booking request message format..
        • Request message format - Cancel
        • Request message format - Commit/Rollback
        • Request message format - Modify
        • Response message format - Booking
      • Enhanced shopping (EST)
        • Requesting Specific Rates
        • Request message format
        • Response message format.
      • Rate and availability transactions
        • Standard multi-availability
          • Request & Response message format
      • Rate Rules
        • Request message format
        • Response message format
      • Reference data transactions
        • Request message format..
        • Response message format..
      • Single property availability
        • Request message format
        • Response message format
    • XML ultradirect specifications
      • Overview
        • Transaction list
      • Interface requirements
      • Transaction meta data
    • Error Codes..
    • UltraDirect Transaction Samples and Usage
      • Using UltraDirect (Seamless, a real-time transaction)
      • EST (Enhanced Shopping Transaction)
      • Rate Rules
      • Book Reservation
      • Cancellation
      • Book Reservation with session control
      • Modification
      • Booking Storage and Retrieval
      • List of Test Credit Cards
      • Test properties in UAT
      • Guarantee Type and Method Combinations
    • xml ultradirect codes
  • Get in Touch
    • Questions?
Powered by GitBook
On this page
  1. Content
  2. Content Update
  3. Transaction specifications

Area Information

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

AreaInfo

3

C

Element required when action code is Add or Overwrite = true

Only 1 element allowed per Property message.

Attractions

4

C

Only Required when action code is add or Overwrite = true

Only 1 element allowed per Property message.

Attraction

5

R

Required when

Attractions element is present.

AttractionCat egoryCode

C

R

Refer to the

“HCD OTA

Supported Codes” spreadsheet

for valid codes

Attraction Category Code (ACC).

Only Required when action code is add or Overwrite = true

Same Code can be provided with new ID attribute.

GDS Note: When property’s information is

Element

Level

Attribute

R

O

C

G D

S

Example

Usage

Description

delivered to the GDSs, must have one

Attraction with

AttractionCategoryCo de of “1” (Airport), and one with

AttractionCategoryCo de of “67” (City Center) or “68” (City

Downtown) with

PrimaryIndicator=”tru e”.

AttractionNa me

O

O

Six Flags

64 Char

Max: 128 bytes

The name of the

attraction

AttractionName is a

multi-lingual attribute.

Code

C

R

DFW

3 Char

Airport Code

Attribute is ONLY used and Required when

AttractionCategoryCo de is “1” (Airport).

Removal

O

true false

If not specified, false is assumed.

ID

R

ACC001

32 Char

Unique Identifier

Required for

Attraction element.

Contact

6

O

Only 1 element allowed per Attraction.

Removal

O

true false

If not specified, false is assumed.

URLs

7

O

Only 1 element allowed per Attraction.

URL

8

R

128 Char

Attraction website address

Only one Element per Attraction allowed.

If more than one

Element

Level

Attribute

R

O

C

G D

S

Example

Usage

Description

element is present, an error will be returned.

Required when URLs element is present.

Description

6

O

Only 1 element allowed per Attraction.

ContentID

O

AREA002

64 Char

Image Code

Text

7

O

310 Char

Attraction

description

Only one Element per Attraction allowed.

If more than one element is present, an error will be returned.

Text is a multi-lingual element.

RefPoints

6

O

Only 1 element allowed per Attraction.

RefPoint

7

R

Required when

RefPoints is present.

Only 1 element allowed per Attraction.

Direction

O

R

N

NE

NW

S

SE

SW

E

W

Defines the cardinal direction

Enumerated attributed. Must use one of the values found in the example.

Distance

C

R

12

Decimal 5,2

Distance to/from Reference Point.

Only Required when action code is add or Overwrite = true.

DistanceUnit

Name

C

R

Mile

Km

When provided this attribute will override

Element

Level

Attribute

R

O

C

G D

S

Example

Usage

Description

Block

the

UnitOfMeasureCode

(under

HotelDescriptiveCont ent) attribute for a specific attraction.

Enumerated attributed. Must use one of the values found in the example.

PrimaryIndic ator

C

R

true false

Indicates whether the reference point is considered the main reference point for the specific type Attraction Category Code (ACC).

If NOT populated, will be defaulted to false.

GDS Note: If

AttractionCategoryCo de is “1” (Airport), “67” (City Center) or

“68” (City

Downtown), one must have PrimaryIndicator set to “true”.

Proximity

O

C

3

The valid values are a subset of the LOC code list:

“1” = Airport

(within 5 Mi/8 Km of property)

“3” = City

“10” = Resort

“11” = Rural

“13” =

Suburban “29” = North suburb “30” = South suburb

This is only applicable to “airport” attractions

(AttractionCategoryC ode=”1”).

Mandatory for properties subscribing to GDS content updates via HCD

Element

Level

Attribute

R

O

C

G D

S

Example

Usage

Description

“31” = East suburb “32” = West suburb

CityCode

O

R

DAL

FTW

MIA

3 Char

City Code

Attribute is ONLY used when

AttractionCategoryCo de is “67” (City Center) or “68” (City Downtown).

Removal

O

true false

If not specified, false is assumed.

Transportations

8

O

Only 1 element allowed per RefPoint.

Transportation

9

O

Required with

Transportations

Element is present

Transportati onCode

R

R

Refer to the

“HCD OTA

Supported Codes” spreadsheet

for valid codes

Transportation Code (TRP).

Required for Transportation element.

GDS Note: Must be populated for ACC = 1, 67 or 68 when property’s information is delivered to the GDSs.

Included

O

O

false

Boolean

Specifies whether the transportation method is complimentary – e.g.

Amount

O

10.00

Decimal 12,3

Cost of transportation to/from Reference Point.

ChargeUnit

O

O

CHG code list

Specifies what the Amount applies to –

e.g. one-way, roundtrip etc.

Removal

O

true false

If not specified, false is assumed.

Descriptions

10

O

Only 1 element allowed per Attraction.

Element

Level

Attribute

R

O

C

G

D

S

Example

Usage

Description

Description

11

R

Required when

Descriptions Element is present.

Only 1 element allowed per Attraction.

Text

12

O

R

Most car rental

compani es have counters at OHare Internati onal Airport.

1,024 Char

Max: 2,000 bytes

Transportati on

description

Required when

Description element is present.

Only 1 Element allowed per

AttractionCategoryCo de / ID combination within the Attraction Element.

If more than one is present, an error will be returned.

Text is a multi-lingual

OperationSchedules

10

O

Specifies the hours of operation by days of week for the

OperationSchedule

11

R

Required when OperationSchedules is present.

OperationTimes

12

R

Required when OperationSchedule is present.

OperationTime

13

R

Multiple OperationTime elements can be present as long as they are not effective for the same period/days of week.

At least one of the days of week attributes (e.g. Mon, Tue) must be set to true.

Element

Level

Attribute

R

O

C

G D

S

Example

Usage

Description

Mon

C

O

Tue

C

O

Weds

C

O

Thur

C

O

Fri

C

O

Sat

C

O

Sun

C

O

Start

C

O

08:00:00

End

C

O

23:00:00

Descriptions

8

O

Only 1 element allowed per Attraction.

Description

9

R

Required when

Descriptions Element is present.

Text

10

O

R

30 west to

exit 282,

Main

Street.

Continue straight through light, and the hotel is located 1/4 mile ahead on the left.

1,024 Char

Max: 2,000

bytes

Directions description

Required when

Description element is present.

Only 1 Element allowed per

AttractionCategoryCod e / ID combination within the Attraction Element.

Recreations

4

O

Only 1 element allowed per Property message.

Recreation

5

R

Required when Recreations element is present.

CodeDetail

O

Please contact front desk for tee times.

64 Char

Max: 128 bytes

Recreation Service

Type code detail

This is meant to provide additional detail about the associated RST code.

CodeDetail is a multi- lingual attribute.

Element

Level

Attribute

R

O

C

G D

S

Example

Usage

Description

ExistsCode

C

Refer to the

“HCD OTA

Supported Codes” spreadsheet for valid codes.

Option Type Code (OTC).

Information under Recreation element will only be added when code = 1 or attribute is not present.

Removal

O

true

If not specified, false

false

is assumed.

Code

R

O

Refer to the

“HCD OTA

Supported Codes” spreadsheet

for valid codes

Recreation Service Type (RST).

Required for

Recreation Element.

ProximityCod e

O

O

Refer to the

“HCD OTA

Supported Codes” spreadsheet

for valid codes

Proximity Table (PRX).

Included

O

O

true false

Whether or not the recreation is included with the room rate, or if there is an extra charge.

Value will be defaulted to “false” if attribute is not sent in message.

Description

6

O

Only 1 element allowed per Recreation.

ContentID

O

POOL001

64 Char

Image Code

Element

Level

Attribute

R

O

C

G D

S

Example

Usage

Description

Text

7

O

This is a great recreation

310 Char

Recreation

description

Only 1 Element allowed per recreation.

If more than one is present, an error will be returned.

Text is a multi-lingual element.

RecreationDetails

6

O

Only 1 element allowed per Recreation.

RecreationDetail

7

R

Required when

RecreationDetails is present.

Code

R

O

Refer to the

“HCD OTA

Supported Codes” spreadsheet

for valid codes

Recreation Srvc Detail Code (REC).

Required for RecreationDetail element.

CodeDetail

O

64 Char

Max: 128 bytes

Recreation service

detail detail

This is meant to provide additional detail about the associated REC code.

CodeDetail is a multi- lingual attribute.

ExistsCode

C

Refer to the

“HCD OTA

Supported Codes” spreadsheet for valid codes.

Option Type Code (OTC).

Information under RecreationDetail element will only be added when code = 1 or attribute is not present.

Removal

O

true false

If not specified, false is assumed.

Schema design view

Example transaction

<OTA_HotelDescriptiveContentNotifRQ xmlns="
http://www.opentravel.org/OTA/2003/05
" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance
" Version="4.000" PrimaryLangID="EN">
<HotelDescriptiveContents>
<HotelDescriptiveContent UnitofMeasureCode="1" CurrencyCode="USD" TimeZone="CST" BrandCode="ZZ" HotelCode="AA123" HotelName="Test Hotel" Overwrite="false">
<AreaInfo>
<Attractions>
<Attraction ID="12345" AttractionCategoryCode="50" Removal="false" AttractionName="Dallas Opera">
<Contact Removal="false">
<URLs>
<URL>http://www.dallasopera.com</URL>
</URLs>
</Contact>
<Description ContentID="AREA002">
<Text>Winspear Opera House</Text>
</Description>
<RefPoints>
<RefPoint Direction="West" Distance="30" DistanceUnitName="Mile" Removal="false">
<Transportations>
<Transportation TransportationCode="13" Included="true">  <Descriptions>
    <Description>
<Text>Trans Description scenario #1</Text>     </Description>


<Descriptions>
<OperationSchedules>
        <OperationSchedule>
OperationTimes>
      <OperationTime Sun="true"   
              Start="11:00:00" End="12:00:00"/>
      <OperationTime Start="11:00:00"
              End="12:00:00" Tue="true"/>
      <OperationTime Start="09:00:00"
              End="10:00:00" Weds="true"/>
      <OperationTime Start="09:00:00"
              End="10:00:00" Thur="true"/>
      <OperationTime Start="09:00:00"
              End="10:00:00" Fri="true"/>
      <OperationTime Start="11:00:00"
              End="12:00:00" Sat="true"/>
</OperationTimes>
       </OperationSchedule>
</OperationSchedules>
      </Transportation>
     <Transportation TransportationCode="4" Included="false"
      ChargeUnit="11" Amount="25.00">
<Descriptions>
<Description>
<Text>Trans Description scenario #2</Text>
     </Description>
</Descriptions>
<OperationSchedules>
     <OperationSchedule>
           <OperationTimes>
     <OperationTime Sun="true"
Start="08:00:00" End="09:00:00"/>
     <OperationTime Start="08:00:00"
End="09:00:00" Mon="true"/>
          </OperationTimes>
    </OperationSchedule>
</OperationSchedules>
       </Transportation>
       <Descriptions>
<Description>
       <Text>Head east on Woodall Rogers Freeway and exit south on Pearl St</Text> </Description>
</Descriptions>
</RefPoint>
</RefPoints>
</Attraction>
</Attractions>
          </AreaInfo>
<Recreations>
<Recreation ExistsCode=”1” CodeDetail="Golf" Removal="false" Code="27" ProximityCode="2"
     Included="false">          
<Description ContentID="Rec001">
<Text>Hank Haney's Golf Center</Text>
</Description>
<RecreationDetails>
<RecreationDetail ExistsCode=”1” Code="1" CodeDetail="Driving range" Removal="false"/>
<RecreationDetail ExistsCode=”1” Code="5" CodeDetail="Putting green" Removal="false"/> <RecreationDetail ExistsCode=”1” Code="6" CodeDetail="Golf clubs available for rental or
purchase" Removal="false"/>
</RecreationDetails>
</Recreation>
</Recreations>
</AreaInfo>
</HotelDescriptiveContent>
</HotelDescriptiveContents>
</OTA_HotelDescriptiveContentNotifRQ>
PreviousData mapping of elementsNextAffiliation information

Last updated 3 months ago

www.sixfl

aggs.com