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

TPA extensions

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

TPA_Extensions

3

O

Only 1 element allowed per Property message.

TPA_Extension

4

R

Required when TPA_Extensions is present.

Only 1 element allowed per Property message.

USWInfo

5

O

Only 1 element allowed per Property message.

Required if brand code and/or property ID differs between HCD and USW.

Chain

R

ZZ

2 to 3 Char

USW Chain Code

PID

R

ZZ1234

10 Char

USW Property ID

EAPInfo

5

O

O

This is only applicable for properties subscribing to

Element

Level

Attribute

R

O

C

G

D

S

Example

Usage

Description

false

assumed.

FactId

R

32 Char

Unique Identifier

Required for HotelFact Element.

GuaranteePaymentExten ded

5

O

Only 1 element allowed per Property message. It is recommended that the

GDSGuaranteePayments element is used instead, as this allows late arrivals to vary by date range and day of week.

lateArrivalsAllo wed

R

O

true false

Defines if late arrivals are allowed at the property.

GDSGuaranteePayments

5

O

O

This is used to define whether late arrivals are allowed at the property. This can vary by date period and days of week.

GDSGuaranteePayment

6

R

R

lateArrivalsAllo wed

R

O

true false

Defines if late arrivals are allowed at the property.

Start

R

R

2009-01-01

Date

The Start Date associated to the Late Arrival policy.

Please see the business rules for more details.

End

R

R

2009-12-31

Date

The End Date associated to the Late Arrival policy.

Please see the business rules for more details.

Mon

R

O

true false

At minimum one Day of Week must be chosen.

Tue

R

O

true false

At minimum one Day of Week must be chosen.

Weds

R

O

true false

At minimum one Day of Week must be chosen.

Thur

R

O

true false

At minimum one Day of Week must be chosen.

Fri

R

O

true false

At minimum one Day of Week must be chosen.

Element

Level

Attribute

R

O

C

G

D

S

Example

Usage

Description

Sat

R

O

true false

At minimum one Day of Week must be chosen.

Sun

R

O

true false

At minimum one Day of Week must be chosen.

GalileoRules

5

C

Required for GDS

Updates to Galileo only.

GalileoRoomDescriptions

6

O

GalileoRoomDescription

7

R

Rule

R

R

Max 5 chars

ID

R

Max 3 chars

Guest Room ID to which the

GalileoRoomDescription rule is associated.

Removal

O

true false

If not specified, false is assumed.

GalileoCancelRules

6

O

GalileoCancelRule

7

R

Required when GalileoCancelRules element is present.

Rule

R

R

Max 5 chars

Galileo Cancel Rule Number

Identifies the associated cancel policy.

ID

R

Max 3 chars

Cancel Policy ID to which

the cancel rule is associated

Removal

O

true false

If not specified, false is assumed.

GalileoDepositGuarantee Rules

6

O

GalileoDepositGuarantee Rule

7

R

Rule

R

R

Max 5 chars

Galileo

Deposit/Guarantee Rule Number

Identifies the associated guarantee or deposit policy.

Start

R

2009-05-01

Date

Start date of

Guarantee/Deposit policy to which the rule number is associated.

Element

Level

Attribute

R

O

C

G

D

S

Example

Usage

Description

End

R

2009-10-31

Date

End date of

Guarantee/Deposit policy to which the rule number is associated.

Mon

R

true false

Day of week corresponding to the Guarantee/Deposit policy to which the rule number is associated.

Tue

R

true false

Weds

R

true false

Thur

R

true false

Fri

R

true false

Sat

R

true false

Sun

R

true false

Removal

O

true false

If not specified, false is assumed.

GalileoReservationRules

6

O

GalileoReservationRuleN o

7

O

Rule

R

R

Max 5 chars

Galileo Reservation Rule Number

Identifies the associated

Payment Methods

Start

R

2009-01-27

Date

Start date of the Method of Payment policy to which the rule number is associated.

End

R

2009-02-05

Date

End date of the Method of Payment policy to which the rule number is associated.

Removal

O

true false

If not specified, false is assumed.

GalileoMethodOfPayme ntRule

6

O

Rule

R

R

Max 5 chars

Galileo Method of

Payment Rule

Identifies the associated Credit Cards that are accepted for payment.

Removal

O

true false

If not specified, false is assumed.

Element

Level

Attribute

R

O

C

G

D

S

Example

Usage

Description

GalileoExtraOptionsRule

6

O

C

This is required in order to transmit the extra charges specified in ExtraPersonChares element to Galileo (for properties subscribing to the GDS content update service).

Rule

R

R

54321

Max 5 chars

Galileo Extra Options Rule

Removal

O

O

false

true false

If not specified, false is

assumed

StayRequirements

5

O

O

Stay requirements should be provided only when the minimum or maximum stay is an exception to the normal stay requirements of a property.

This is optional for properties subscribing to the GDS content update service – however, if one or more are supplied then at least one must have a Start date in the future.

StayRequirement

6

R

R

There can be multiple stay requirements as long as the dates do not overlap.

Start

R

R

2010-09-01

Date

Effective date on which the stay requirements

first take effect

End

R

R

2011-05-31

Date

Last date on which the stay requirements apply

Mon

R

R

true false

Days of week that the stay requirement is active. At least one must be set to “true”.

Tue

R

R

true false

Weds

R

R

true false

Thur

R

R

true false

Fri

R

R

true false

Sat

R

R

true false

Sun

R

R

true false

MinLOS

R

R

2

Integer

Minimum length of stay

Element

Level

Attribute

R

O

C

G

D

S

Example

Usage

Description

MaxLOS

O

O

7

Integer

Maximum length of stay - optional

GalileoLengthO fStayRule

O

C

54321

Max 5 Chars

Required in order to distribute the stay requirement rule to Galileo.

ExtraPersonCharges

5

O

O

This defines the extra person, rollaway and crib charges applied to room- rates. These are transmitted to the GDSs as fixed or free form text areas of the property

description (i.e. for information purposes only). If not supplied for properties subscribing to the GDS content update

service then it will be assumed there are no extra charges.

Adult

6

O

O

20.00

Charge amount

Extra adult charge

Child

6

O

O

5.00

Charge amount

Extra child charge

AdultRollaway

6

O

O

10.00

Charge amount

Adult rollaway charge

ChildRollaway

6

O

O

0

Charge amount

Child rollaway charge

Crib

6

O

O

0

Charge amount

Crib/cot charge

ChildPolicyExtended

5

O

O

Used to extend the child policy information defined in:

HotelDescriptiveContent/ Policies/Policy/PolicyInfo

FreeChildCount

O

O

1

Integer

Number of free children for each

RoomCompanionCount

MaxFreeChildC ount

O

O

2

Integer

Maximum number of free children. If not present then it is unlimited (up to the maximum room/child occupancy for the room).

RoomCompani onCount

O

O

2

Integer

Required number of accompanying guests in the room for the free child policy to apply

RoomCompani onType

O

O

PayingGuest

Values:

“Paying Guest”

or

“Adult”

Type of accompanying guest. Note:

“PayingGuest” may include chargeable children

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">
<TPA_Extensions>
<TPA_Extension>
<USWInfo Chain="ZZ" PID="AA123"/>
<EAPInfo Chain="YY" PID="BB4321" GDSName="The Utell Grand Hotel"/>
<HotelFacts>
<HotelFact Fact="Pool is closed June 12th - 25th." Start="2011-01-27" End="2011-06-26" Removal="false"
     FactID="1234"/>      
</HotelFacts>
<GalileoRules>


<GalileoRoomDescriptions>
<GalileoRoomDescription ID="A1K001" Rule="11111"/>
</GalileoRoomDescriptions> <GDSGuaranteePayments>
<GDSGuaranteePayment Start="2011-01-01" End="2011-12-31" Mon="true" Tue="true" Weds="true" Thur="true" Fri="false" Sat="false" Sun="false" lateArrivalsAllowed="false"/>
</GDSGuaranteePayments>
<GalileoCancelRules>
<GalileoCancelRule ID="CXL02" Rule="22222"/>
</GalileoCancelRules>
<GalileoDepositGuaranteeRules>
<GalileoDepositGuaranteeRule Rule="83628" Start="2011-01-01" End="2011-12-31" Mon="true" Tue="true" Weds="true" Thur="true" Fri="false" Sat="false" Sun="false"/>
</GalileoDepositGuaranteeRules>
<GalileoReservationRules>
<GalileoReservationRuleNo Rule="72636" Start="2010-04-21" End="2010-11-30"/>
</GalileoReservationRules>
<GalileoMethodOfPaymentRule Rule="29372"/>
<GalileoExtraOptionsRule Rule="54321"/>
</GalileoRules>
<StayRequirements>
<StayRequirement Start="2011-02-21" End="2011-09-30" Mon="true" Tue="true" Weds="true" Thur="true"
Fri="false" Sat="false" Sun="false" MinLOS="3" MaxLOS="7" GalileoLengthOfStayRule="16252"/>
</StayRequirements>
<ExtraPersonCharges>
<Adult>20.00</Adult>
<Child>5.00</Child>
<AdultRollaway>10.00</AdultRollaway>
<ChildRollaway>0</ChildRollaway>
<Crib>0</Crib>
</ExtraPersonCharges>
<ChildPolicyExtended FreeChildCount="1" MaxFreeChildCount="1" RoomCompanionCount="2" 
                                     RoomCompanionType="Adult"/>
</TPA_Extension>
</TPA_Extensions>
</HotelDescriptiveContent>
</HotelDescriptiveContents>
</OTA_HotelDescriptiveContentNotifRQ>
PreviousContact informationNextGDS information

Last updated 4 months ago