Transmission of the prices based on OTA_HotelAvailNotifRQ / OTA_HotelAvailNotifRS

The OTA_HotelAvailNotifRQ / OTA_HotelAvailNotifRS can be used to transmit exclusively room-based pricing. A request will be send every time a change in the prices has been detected on our system.


Other usages of OTA_HotelAvailNotifRQ / OTA_HotelAvailNotifRS

Beside transmitting room availabilities, the OTA_HotelAvailNotifRQ / OTA_HotelAvailNotifRS message pair can also be used to transmit booking rules (MinLOS, MaxLOS, Closed to Arrival, Closed to Departure, etc..) as well as the room availabilities. Check the corresponding chapters to see use cases

The Hotel-Spider system will send the following request

Use case: OTA_HotelAvailNotifRQ for room-based pricing
<OTA_HotelAvailNotifRQ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.opentravel.org/OTA/2003/05" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_HotelAvailNotifRQ" Version="1.000">
  <POS>
    <Source>
      <RequestorID ID="MASTERUSERNAME" MessagePassword="MASTERPASSWORD" Type="13"></RequestorID>
    </Source>
  </POS>
  <AvailStatusMessages HotelCode="HOTELCODE">
    <AvailStatusMessage>
      <StatusApplicationControl InvCode="00P5519245316dc1" Start="2015-09-25" End="2015-09-28" RatePlanCode="00P551924536469f" />
      <BestAvailableRates>
        <BestAvailableRate Amount="111.33" DecimalPlaces="2" CurrencyCode="CHF" />
      </BestAvailableRates>
    </AvailStatusMessage>
  </AvailStatusMessages>
</OTA_HotelAvailNotifRQ>

Request structure

OTA_HotelAvailNotifRQ

Parent: None (Root element)

Mandatory: yes

Attributes:

Name
Mandatory
Description
TimeStampYesThe format should respect the ISO 8601 2015-11-16T22:23:48+00:00
TargetYes

When sending updates to the staging environment "Test" must be used.

When sending updates to the production environment "Production" must be used.

VersionYesThe default value should be "1.000"
EchoTokenYesThis string should be returned in the response

Child elements: POS (when using POS authentication. See Authentication methods for more information), AvailStatusMessages


AvailStatusMessages

Parent: OTA_HotelAvailNotifRQ

Mandatory: yes

Attributes:

Name
Mandatory
Description
HotelCodeYesThe ID of the hotel on the online booking system

Child elements: AvailStatusMessage


AvailStatusMessage

Parent: Inventories

Mandatory: yes

Attributes: None

Child elements: StatusApplicationControl


StatusApplicationControl

Parent: Inventory

Mandatory: yes

Attributes:

Name
Mandatory
Description
InvCode/InvTypeCode/RoomIDYes

The ID of the room type on the online booking system

By default our system will search for the InvCode attribute. Should you have been using InvTypeCode in a previous development (for example: OTA version of the Booking.com interface ), we can configure our interface to work with InvTypeCode. The same goes for the RoomID attribute.

RatePlanCode/RatePlanType/RatePlanIDNo

The ID of the rate plan on the online booking system

By default our system will search for the RatePlanCode atttribute. Should you have been using RatePlanType in a previous development, we can configure our interface to work with RatePlanType. The same goes for the RatePlanID attribute.

StartYesThe format will respect ISO 8601 2015-11-16
EndYesThe format will respect ISO 8601 2015-11-16
MonNoDoes this update apply to a Monday
TueNoDoes this update apply to a Tuesday
WedsNoDoes this update apply to a Wednesday
ThurNoDoes this update apply to a Thursday
FriNoDoes this update apply to a Friday
SatNoDoes this update apply to a Saturday
SunNoDoes this update apply to a Friday

Child elements: None

RatePlanCode attribute use scenario

The RatePlanCode/RatePlanType/RatePlanID attribute will only be transmitted if the online booking system manages multiple rate plans.

BestAvailableRates

Parent: AvailStatusMessage

Mandatory: yes

Attributes: None

Child elements: BestAvailableRate


BestAvailableRate

Parent: BestAvailableRates

Mandatory: yes

Attributes:

Name
Mandatory
Description
AmountYesThe new price to apply on the online booking system
DecimalPlacesYesThe number of decimal places that have been transferred with the price
CurrencyCodeYesThe currency in which the price has been transmitted

Child elements: None



The online booking system must respond with either of the following formats

Use case 1. OTA_HotelAvailNotifRS confirmation
<OTA_HotelAvailNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" TimeStamp="2015-11-25T17:21:43+01:00" EchoToken="" CorrelationID="" Version="1.0">
  <Success />
</OTA_HotelAvailNotifRS>
Use case 2. OTA_HotelAvailNotifRS error notification
<OTA_HotelAvailNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" TimeStamp="2015-11-25T17:21:43+01:00" EchoToken="" CorrelationID="" Version="1.0">
  <Errors>
    <Error Code="3008" Type="13" Status="NotProcessed" ShortText="Processing error" Tag="/">Hotel ID invalid</Error>
  </Errors>
</OTA_HotelAvailNotifRS>


Response structure

OTA_HotelAvailNotifRS

Parent: None (Root element)

Mandatory: yes

Attributes:

Name
Mandatory
Description
TimeStampYesThe format should respect the ISO 8601 2015-11-16T22:23:48+00:00
TargetYes

When sending updates to the staging environment "Test" must be used.

When sending updates to the production environment "Production" must be used.

VersionYesThe default value should be "1.000"
EchoTokenYesThis string should be returned in the response

Child elements: Success, Errors


Success

Parent: OTA_HotelAvailNotifRS

Mandatory: no

Attributes: None

Child elements: None



Errors

Parent: OTA_HotelAvailNotifRS

Mandatory: No

Attributes: None

Child elements: Error


Error

Parent: Errors

Mandatory: yes

Attributes:

Name
Mandatory
Description
CodeYesThe unique error code assigned by the online booking system
TypeYes
StatusYes

Possible values are:

  • NotProcessed
  • Incomplete
  • Complete
  • Unknown
ShortTextYesA short textual explanation of the error. Max 64 characters.
TagYesIndicates which element and/or attribute provoked the error to occur

Child elements: None