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. Our Products
  2. Channel Manager
  3. RG Bridge - Supply (Push)
  4. Interface Specifications – Reservation Notification Service

Typographical conventions

XML Usage Description

RG Bridge utilizes OpenTravel standard XML for information exchange. The XML usage descriptions employ a pseudo-schema description format to specify the usage of XML elements and attributes as they apply to RG Bridge. The actual schema definitions are made available separately and adhere to industry standards, accommodating many use cases beyond what is required by RG Bridge.

Sample XML

Sample XML messages are provided throughout this document to aid in understanding the message usage. These messages are formatted for clarity. In the example message in Table A, the top-level element of the rate update request message is OTA_HotelResNotifRQ. The attributes of this element follow standard conventions.

Sample XML

<OTA_HotelResNotifRQ xmlns="http://www.opentravel.org/OTA/2003/0 " 
 
EchoToken="" 
 
TimeStamp="2011-01-26T10:22:00-05:00" 
 
Target="Production" 
Version="1.003" 
ResStatus="Book"> 
<POS> 
<Source> 
<RequestorID Type="13" ID="473"/> 
<BookingChannel Type="7" Primary="true"> 
<CompanyName>Travel Today</CompanyName> 
</BookingChannel> 
</Source> 
</POS> 
<HotelReservations> 
<HotelReservation> 
<RoomStays> 
<RoomStay> 
<!-- details omitted --> 
</RoomStay> 
</RoomStays> 
<ResGuests> 
<ResGuest> 
<Profiles> 
<ProfileInfo> 
<!-- details omitted --> 
</ProfileInfo> 
</Profiles> 
</ResGuest> 
</ResGuests> 
</HotelReservation> 
</HotelReservations> 
</OTA_HotelResNotifRQ> 

Message Focus and Formatting

Identifiers:

  • To highlight the parts of the message being discussed, those parts have an identifier, like this: OTA_CancelRQ.

Green Values:

  • Values shown in green must be set in a specific way because that is the only use of that element/attribute that RG Bridge can process. For example:

    xml

    <RateTimeUnit>Day</RateTimeUnit>
    • "Day" is the only value that can be passed to RG Bridge, even though the OTA schema allows other values.

Red Values:

  • Values shown in red are specific to the message. For example:

    xml

    <CompanyName>Travel Today</CompanyName>
    • "Travel Today" specifies the channel name. These values are fictitious and used for sample purposes only.

Formatting for Readability:

  • Messages have been formatted with additional new lines and tab characters for better readability. However, these are not part of the actual XML and must not be used in actual messages.

XML Style Comments:

  • XML style comments in the samples are not part of the schema. They have been added to indicate incomplete sections in the XML, helping focus on the important parts and show the general pattern. For example:<!— Content omitted-->

Last updated 3 months ago