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. UltraDirect
  2. Ultradirect transaction sets - XML
  3. Enhanced shopping (EST)

Request message format

Element Path

Attribute

Occ

Type

Notes

HotelML/Head/Process

1

DataPath

1

Char

Set to "/HotelML/Form/MultiAvailability”

Function

1

Char

Set to “TI_MultiAvailabilityV1_1”

Token

1

Char

Unique ID for the transaction generated by the system sending the transaction.

Timeout

0..1

Integer

Specifies the maximum time (in milliseconds) that UltraDirect should wait for responses from the CRSs before returning a response to the affiliate. If the timeout expires before the rates and availability has been obtained for all properties then UltraDirect will return details to the affiliate of all properties that have responded. UltraDirect will also return a second response for all remaining properties if requested (by using the AcceptMultipartResponse attribute – see below). If the attribute is omitted, the standard UltraDirect timeout value will be used. If the requested timeout is greater than the UltraDirect standard timeout, the standard timeout will be used.

AcceptMultipart Reponse

0..1

Boolean

Specifies whether the requesting system will accept a response in multiple parts – i.e. the results for an initial set of properties after the affiliate- specified timeout expired, followed by the results for the remaining properties. This is implemented as a ‘chunked’ transfer-encoded HTTP response. If multi-part responses are not requested (i.e. the value is false or the attribute is omitted) then only one response will be returned. This attribute is only applicable when the Timeout attribute is supplied. It will be ignored if Timeout is omitted.

HotelML/Head/Route

1

Source

1

Char 2-3

Identifies the organization sending the transaction. The value to use will be provided during the implementation project.

Destination

1

Char 2

Always set to “00” (i.e. zero zero).

RequestedAccuracy

0..1

Enum

This specifies whether the response can be generated from the UltraDirect transaction cache. Note: this is a preference, since it can be overridden by the hotel chain. Valid values are: “CacheOrSource” (default if attribute is omitted) - First attempt to respond with data from the cache, but if data is not available, deliver the request to the source (hotel CRS) for processing. “SourceOnly” - Bypass the cache and return availability from the source (hotel CRS) only. “CacheOnly” - Only return data from the cache. If data is not available in the cache for the requested parameters, then an availability status of “Unknown” will be returned. It is strongly recommended to set this to “CacheOrSource”.

HotelML/Form/MultiAvailability/ Property/Locale

0..1

This is used to request the room/rate information is returned in a specific language from the CRS (if available).

Language

1

Char 2

Language code – e.g. “FR”

Country

0..1

Char

Optional country name – e.g. “France”.

HotelML/Form/MultiAvailability/ Property

1..200

Repeated for each property.

Code

1

Char

Chain and property code, separated by a semi-colon – e.g. “UI;AB1234”

HotelML/Form/MultiAvailability/ RateCriteria

1

Specifies rate selection criteria.

VersionCompliance

1

Enum

Must be set to “Enhanced_V1”.

Usage

0..1

Enum

Values are: “PreBook” – re-check the rate and/or availability status prior to making a booking “CacheShopping” – availability transactions that are automatically generated by the demand partner’s system to fill and/or refresh a local cache. “ProductDetails” – availability transaction to obtain additional information about a room/rate during the booking flow “UserShopping” – availability transaction generated by an end-user event (e.g. searching on a website) “Shop2Push” (RateGain Internal Use Only)

MatchingQualifier

0..1

Enum.

Valid only when at least one rate plan code (RateCriteria/RateSearch/@RatePlanCode) is included in the request. If “ExactAndPublic” the CRS should return the requested rate plans (if available) plus the public rates. If “Exact” the CRS should return rates for the requested rate plans only. If “ExactOrPublic” the CRS should return rates for the requested rate plans when available, or return public rates if requested rate plans are not available.

CalculationMethod

0..1

Enum.

Specifies the preferred rate calculation method to use when a rate change occurs across the length of stay. Valid values are: “First” – rate for the first night “Highest” – highest nightly rate “Average” – average nightly rate “Frequent” – most frequently occurring rate When this element is not included on the request, the CRS will apply their default method to calculate the rate range.

Commissionable Status

0..1

Enum.

Specifies whether commissionable and/or non-commissionable rate are required. “Commissionable” = Return commissionable rates only “NonCommissionable” = Return non-commissionable rates only “Both” = Return both non-commissionable and commissionable rates. This is the default if not sent.

ReturnUnavailable

0..1

Boolean

If “true”, closed properties will be included in the response. If “false”, closed properties will not be included in the response.

NumberOfAdults

1

Integer

This attribute is deprecated – should use GuestCount element instead.

NumberOfChildren

0..1

Integer

This attribute is deprecated – should use GuestCount element instead.

NumberOfRooms

1

Integer

Total number of rooms required, which is used when checking availability. The prices in the response will be per room.

NumberOfBeds

0..1

Integer

Preferred number of beds per room

BedType

0..1

Enum

Indicates the preferred bed type. Values are: Single, Twin, Double, King, Queen, Futon, MurphyBed, SofaBed, TatamiMats, Rollaway, Crib

ReturnRateChanges

0..1

Boolean

Preference for whether response should include each distinct rate if it changes during the stay.

RoomCategory

0..1

Enum

Indicates the preferred quality of room. The following values are most commonly used: Deluxe, Superior, Standard, Moderate, Economy, Premium The attribute also supports the following values but these are generally not used in this context: FirstClass, Budget, Upscale, Luxury, MeetingConvention, ResidentialApartment, Resort, CorporateBusinessTransient, AllSuite, ExtendedStay, Tourist, Efficiency

HotelML/Form/MultiAvailability/ RateCriteria/GuestCount

0..M

This element specifies the number of adults and children (optionally including child counts by age). GuestCount must occur once (and only once) with Type=”Adult”. It can also occur once with Type=”Child” if no Age attribute is supplied. Alternatively, it can multiple times for Type=”Child” when an Age attribute is specified. It should be used instead of the NumberOfAdults and NumberOfChildren attributes of PropertyRate because it allows the age of each child to be specified.

Type

1

Enum

Values “Adult” or “Child”

Count

1

Integer

Number of guests of this type

Age

0..1

Integer

The optional age of the guest. Only applicable when Type=”Child”.

HotelML/Form/MultiAvailability/ RateCriteria/ExtraBed

0..1

This is used to request rollaway beds or cots/cribs. The element can occur up to three times - once for each type of extra bed – as defined by the Type attribute.

Type

Enum

Type of extra bed required. Valid values are: AdultRollAway, ChildRollAway, Crib

Number

Integer

The number of beds of this type

HotelML/Form/MultiAvailability/ RateCriteria/AgentInfo

0..1

Number

1

Char 8

Travel agent identifier – often the IATA number.

Type

1

Enum.

Identifies the type of travel agent identifier. Values are: “ARC” , “IATA”, “TIDS”, “CLIA”, “AAA”, “GDS”, “Other”.

City

0..1

Char 3

Originating Agent’s City. Not normally required.

Country

0..1

Char 2

Originating Agent’s Country Code (ISO Standard Codes). Not normally required.

HotelML/Form/MultiAvailability/ RateCriteria/Amenity

0..6

This is used to request specific room or rate features, such as breakfast (“BRKFST”) or a non-smoking room (“NSMK”) etc.

Code

1

Char 6

The list of codes can be obtained using the AmenityInformation transaction.

HotelML/Form/MultiAvailability/ RateCriteria/DateRange

1

InDate

1

Date

The arrival date in format “2011-12-24”

OutDate

1

Date

The departure date in format “2011-12-27”

HotelML/Form/MultiAvailability/ RateCriteria/PriceRange

0..1

Specifies the required maximum and/or minimum rate (per room per night). Rarely used.

Currency

1

Char

ISO currency code – e.g. “USD”

Max

0..1

Decimal

Maximum required daily rate per room - e.g. “150.00”

Min

0..1

Decimal

Minimum required daily rate per room - e.g. “150.00”

HotelML/Form/ MultiAvailability/ RateCriteria/RateSearch

0..M

The RateSearch element is used to request one or more specific rate plan codes. This is used in conjunction with PropertyRate/@MatchingQualifier to specify whether the CRS should return the requested rate plans and/or public rates. If this element is not present, the CRS may return any available rate plan codes it wishes to promote. A maximum of 15 rate plan codes can be supplied in the RateSearch element for each hotel chain.

RatePlanCode

0..1

Char 10

Rate access code. This can be used to request special types of rate, such as specific negotiated or corporate rates. If this functionality is required, the actual RatePlanCode and RatePlanType to send will be provided to the affiliate by the hotel chain or RateGain as part of the UltraDirect implementation project. Also, many hotels recognize the following standard (generic) rate plan codes. These all require RatePlanType=”Standard”. "PRO" = Promotional "COR" = Corporate "WKD" = Weekend "RAC" = Rack "SNR" = Senior "GOV" = Government "MIL" = Military "PKG" = Package “WEB” = Web/Internet “CLB” = Club “FAM” / “FPM” = Family “CVN” or “CNV” = Convention "TVL” = Travel Agent "TUR" = Tour

RatePlanType

0..1

Char

Specifies the type of RatePlanCode. Values are: Corporate, Negotiated, NetRate, Standard

BrandCode

0..1

Char 6

If BrandCode is specified then the information in the RateSearch element (such as rate plan code, corporate customer number, frequent guest number etc.) would only be included in transactions to the specified chain’s Central Reservation System (CRS). If the BrandCode is not supplied then the information will be included in transactions to all hotel chains’ CRSs. It should therefore be used when information in the RateSearch element is specific to a hotel chain.

HotelML/Form/MultiAvailability/ RateCriteria/RateSearch/AutoInfo

Code

0..1

Char 25

Auto Frequent Traveler Number

HotelML/Form/MultiAvailability/ RateCriteria/RateSearch/CorpInfo

Code

0..1

Char 25

Corporate Account Number. This should only be sent when RateSearch/@RatePlanType=”Corporate”.

HotelML/Form/MultiAvailability/ RateCriteria/RateSearch/FlyerInfo

Code

0..1

Char 25

Frequent Flyer Number

HotelML/Form/MultiAvailability/ RateCriteria/RateSearch/FreqGuest

Code

0..1

Char 25

Frequent Guest Number

PreviousRequesting Specific RatesNextResponse message format.