Skip to main content

ARI Sync - Hurdle (OTA)

10.3 Rev A
Hotel
ARI
SOAP API

The ARI Sync - Hurdle (OTA) is used to set the status for an inventory block, a rate plan, or an inventory code.

Not Signed In.

Looks like you may not have access to all of the resources and documentation for this page.
Please log-in or contact your support desk team if you believe you should have access.

Target Audience
Hospitality
API Version
10.3 Rev A
Authentication
Security Credentials
Service Action Code
OTA_HotelAvailNotifRQ

The status messages in the Availability Notification message also communicate inventory (booking) limits set by Yield and Revenue management systems such as the number of reservations that can be taken for a certain day, and the threshold at which the hotel is closed. A Booking Limit Status Message may even define what can be done after a status is set, such as “Take four more reservations after this status is set.” A system may choose not to synchronize with actual inventory numbers, but with a threshold. Nevertheless, it is critical that booking systems are synchronized with common thresholds, regardless of whether they are derived from virtual or real inventory.

By default, the interface only updates the hurdles that are defined in the avail message. Any hurdle not specified in the message will continue to exist in the SynXis CR. If the intent is to recreate all the hurdles, then the Instance attribute of the UniqueID element should be set to ‘FullLoad’. This will cause the system to delete all the hurdles before the update occurs.

The attributes: InventoryCodeType, RatePlanCodeType, and InventoryBlockCodeType determine whether the message involves a single code, or a grouping of codes. The Override attribute allows a reservation system to make a change on controls applied at the level of the Property Management System. For example, a CRS may be allowed to make manual changes while processing bookings during the day, but when full optimization is done, typically during the night, this Boolean attribute determines whether to retain the changes made. This could be applied to override all status messages and is found in the StatusApplicationControl class.

Sample Request
<OTA_HotelAvailNotifRQ TimeStamp="2019-11-27T00:39:07.171" Target="Test" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
    <UniqueID Type="16" ID="123456" Instance="FullLoad"/>
    <AvailStatusMessages HotelCode="504" HotelName="The Breakers Palm Beach" >
        <AvailStatusMessage BookingLimitMessageType="SetLimit" >
            <StatusApplicationControl Start="2019-11-23" End="2019-11-27" InvTypeCode="EK"/>
            <HurdleRate Amount="77.77"/>
        </AvailStatusMessage>
    </AvailStatusMessages>
</OTA_HotelAvailNotifRQ>
Sample Response
<OTA_HotelAvailNotifRS TimeStamp="2019-11-27T00:39:07.171" Target="Test" ="4" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Success/>
</OTA_HotelAvailNotifRS>