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 - Reservation Retrieval (Pull)
  4. Operations
  5. Reservation Confirmation

XML Usage specification

Reservation confirmation request; XML Usage

Element/@Attribute

Parent XPath

Description

@TimeStamp

/OTA_NotifReportRQ

Time of the transaction in xml schema date-time format.

@Version

/OTA_NotifReportRQ

The OTA schema version. Mandatory. Use “3.000”.

@Target

/OTA_NotifReportRQ

Set to “Production”.

NotifDetails

/OTA_NotifReportRQ

Details of the notification.

HotelNotifReport

/OTA_NotifReportRQ/NotifDetails

HotelReservations

/OTA_NotifReportRQ/NotifDetails/HotelNotifReport

Contains the reservations.

HotelReservation

/OTA_NotifReportRQ/NotifDetails/HotelNotifReport /HotelReservations

One for each reservation retrieved.

POS

/OTA_NotifReportRQ/NotifDetails/HotelNotifReport

/HotelReservations/HotelReservation

Element for including the channel from which booking had been received. This information was provided in /OTA_HotelResNotifRQ/POS

A simple source record would look like this:

<POS>

<Source>

<BookingChannel>

<CompanyName Code=”LTA1”> Famous OTA

</CompanyName>

</BookingChannel>

</Source>

This indicates that the reservation was retrieved from the OTA “Famous OTA” whose CG Bridge code is LTA1.

ResGlobalInfo

/OTA_NotifReportRQ/NotifDetails/HotelNotifReport

/HotelReservations/HotelReservation

HotelReservationIDs

/OTA_NotifReportRQ/NotifDetails/HotelNotifReport /HotelReservations/HotelReservation/ResGlobalInfo

Reservations IDs. Both the PMS and RGBridge Booking IDs should be included.

HotelReservationID

/OTA_NotifReportRQ/NotifDetails/HotelNotifReport

/HotelReservations/HotelReservation/ResGlobalInfo/ HotelReservationIDs

Reservations ID element.

@ResID_Type

/OTA_NotifReportRQ/NotifDetails/HotelNotifReport

/HotelReservations/HotelReservation/ResGlobalInfo/

HotelReservationIDs/HotelReservationID

3 for PMS Confirm ID and 14 for RGBridge ID

@ResID_Value

/OTA_NotifReportRQ/NotifDetails/HotelNotifReport

/HotelReservations/HotelReservation/ResGlobalInfo/

HotelReservationIDs/HotelReservationID

Reservation ID.

Errors

/OTA_NotifReportRQ

Included in response only if there are errors in processing. If there are errors in the processing of reservations, it is suggested that an OTA_NotifReportRQ message is sent for each reservation that could not be processed. The RGBridge reservation ID must also be set in the HotelReservationIDs node under NotifDetails.

Error

/OTA_NotifReportRQ/Errors

Response will include as many Errors as required. At least one Error element must be present if the response contains Errors

@Type

/OTA_NotifReportRQ/Errors/Error

Error Type. Should be one of the codes listed in Error Types below.

@Code

/OTA_NotifReportRQ/Errors/Error

Error code. Should be one of the codes listed in Error Codes below.

@ShortText

/OTA_NotifReportRQ/Errors/Error

Free Text

@Status

/OTA_NotifReportRQ/Errors/Error

Should be set to String “NotProcessed”

Success

/OTA_NotifReportRQ

Presence of this element indicates a successful Response and in case of a Success Response the Error element should not be present.

Warnings

/OTA_NotifReportRQ

Response may include warnings along with a Success response. Warnings are not allowed with a response that contains Errors.

Warning

/OTA_NotifReportRQ/Warnings

Response may include as many Warning as required. At least one Warning element must be present in a response that contains Warnings.

@Code

/OTA_NotifReportRQ/Warnings/Warning

All Warnings will have the code set as “3000”

@ShortText

/OTA_NotifReportRQ/Warnings/Warning

Free Text

@Status

/OTA_NotifReportRQ/Warnings/Warning

Should be set to “Processed”.

Last updated 4 months ago