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

Ultradirect transaction sets - XML

Overview

The purpose of this document is to provide detailed descriptions of all the transactions and functionality available in UltraDirect. This includes:

Detailed message formats

Description of all fields (XML elements and attributes) used in the request and response messages. This is particularly useful to developers because it supplements the XML message definitions provided in the UltraDirect HotelML XML Schema Definition (XSD) files.

Examples of each request and response message showing the most commonly used functionality of typical process/transaction flows

A summary of the UltraDirect transactions is provided below:

Standard Multi-Availability

Returns the availability status, minimum & maximum rates for a set of properties identified by their property codes

Enhanced Shopping

Returns detailed information for each available room and rate for a set of properties identified by their property codes

Single Property Availability

Returns detailed information for each available room and rate for one property identified by its property code.

Rate Rules

Returns very detailed information for a specific property, room type, and rate. This is typically used to review the rate and policy information before booking the room.

Booking Request

Makes a new hotel reservation

Modify Booking

Makes changes to an existing (confirmed) hotel reservation

Cancel Booking

Cancels an existing (confirmed) hotel reservation

Session Control

Used to commit or roll-back a new booking, modification or cancellation transaction. Only required when the distributor chooses to participate in session control.

Brand Information

Returns basic details of a hotel brand/chain identified by the brand code.

The definitions of the above transactions are grouped in the following sections of this document:

Rate and availability transactions

This section provides details of all transactions used to obtain information about available rates and room types for one or more properties. It is unlikely that a single distributor will use all these transactions. Instead, they will normally use a subset of the transactions, which will vary depending on their specific business requirements. Therefore, the first part of this section outlines several usage scenarios relating to typical business requirements.

Booking transactions

This describes the transactions for creating, modifying, and canceling reservations. It also describes how the usage of these messages varies depending on whether the distributor chooses to use the session control functionality (also known as ‘transaction control’ or ‘two-phased commit’).

Reference data transactions

This describes the transactions used to retrieve reference data. Currently, this is only brand information.

References

Name Notes

Hotel Content Database (HCD) XML Content Retrieval Interface Specification

Describes the OpenTravel XML web service for retrieving hoteldescriptive content from the RateGain HCD.

XML UltraDirect v1.1 Specification

Provides an overview of UltraDirect, including technical information such as connection options (e.g. HTTP 1.1 with SSL) and errors/warnings etc

XML UltraDirect Error Codes

Lists the error and warning codes

XML UltraDirect v1.1 Codes

List codes used by UltraDirect for countries, currencies, credit card types etc

UltraDirect HotelML XML Schema

Definition Files

XML Schema Definition (XSD) files for the UltraDirect HotelML transactions.

PreviousCertificationNextTransaction header formats

Last updated 2 months ago