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
  5. Operations
  6. Reservation Notification

OTA_HotelResNotifRQ

Reservation Message:

  • RG Bridge will send reservations using the OTA_HotelResNotifRQ message.

  • Each message will contain only one reservation record.

PMS Processing:

  • The PMS should process the message synchronously and respond with the confirmation of receipt and PMS confirmation number.

OpenTravel Hotel Reservation Record:

  • It is a complex data structure with many elements possible as per the schema.

  • The PMS Service should be designed to accommodate the maximum amount of data elements, ensuring flexibility and comprehensive handling.

  • RG Bridge can include more information where the data is available from the OTA.

Reservation request; Sample XML

<OTA_HotelResNotifRQ xmlns="http://www.opentravel.org/OTA/2003/05" 	EchoToken="354" 
TimeStamp="2011-01-26T10:22:00-05:00" Target="Production" Version="1.003" 
ResStatus="Commit"> 
<POS> 
 
<Source> 
 
<RequestorID Type="13" ID="473"/> 
 
<BookingChannel  Type="7"  Primary="true"> 
 
<CompanyName>Travel  Today</CompanyName> 
 
</BookingChannel> 
 
</Source> 
 
</POS> 
 
<HotelReservations> 

<HotelReservation CreateDateTime="2015-12-15T00:00:00" CreatorID="RateGain"
ResStatus="Cancel">
<POS>
<Source>
<RequestorID Type="13" ID="473" />
<BookingChannel  Type="7"  Primary="true">
<CompanyName Code="GHRS" />
</BookingChannel>
</Source>
</POS>
<UniqueID Type="14" ID="THVHSCERT007" />
<BasicPropertyInfo HotelCode="RGBRTEST" />
<RoomStays>
<RoomStay PromotionVendorCode="" RoomStayStatus="Book" WarningRPH="">
<RatePlans>
<RatePlan RatePlanCode="1311" />
</RatePlans>
<RoomRates>
<RoomRate RoomTypeCode="STD" NumberOfUnits="1" RatePlanCode="BAR"
PromotionVendorCode="">
<Rates>
<Rate EffectiveDate="2016-01-10" ExpireDate="2016-01-11"
RateTimeUnit="Day"  UnitMultiplier="1">
<Base AmountAfterTax="110" CurrencyCode="EUR" />
</Rate>
<Rate EffectiveDate="2016-01-11" ExpireDate="2016-01-12"
RateTimeUnit="Day"  UnitMultiplier="1">
<Base AmountAfterTax="110" CurrencyCode="EUR" />
</Rate>
</Rates>
</RoomRate>
</RoomRates>
<GuestCounts>
<GuestCount AgeQualifyingCode="10" Count="2" />
</GuestCounts>
<TimeSpan Start="2016-01-10" Duration="P2D" End="2016-01-12" />
<Total AmountAfterTax="220" CurrencyCode="EUR" />
<ResGuestRPHs />
<Comments>
<Comment>
<Text>Cab for Airport will be provided</Text>
</Comment>
</Comments>
<Memberships>
<Membership AccountID="" BonusCode="" PointsEarned="" ProgramCode=""
TravelSector="" />
</Memberships>
<SpecialRequests>
<SpecialRequest>
<Text>Non-Smoking Room</Text>
</SpecialRequest>
</SpecialRequests>
</RoomStay>
</RoomStays>
<Services>
<Service>
<ServiceDetails>
<GuestCounts>
<GuestCount AgeQualifyingCode="10" Count="2" />
</GuestCounts>
</ResGuest>
</ResGuests>
<ResGlobalInfo>
<TimeSpan Start="2016-01-10" Duration="P2D" End="2016-01-12" />
<CancelPenalties  />
<Total AmountAfterTax="220" CurrencyCode="EUR" />
<HotelReservationIDs>
<HotelReservationID ResID_Type="16" ResID_Value="THVHSCERT007" />
<HotelReservationID  ResID_Type="13"  ResID_Value="THVHSCERT007#1(1/2)"  />
<HotelReservationID ResID_Type="14" ResID_Value="00060850/001" />
</HotelReservationIDs>
</ResGlobalInfo>
</HotelReservation>
</HotelReservations>
</OTA_HotelResNotifRQ>

Last updated 3 months ago