Skip to content

OTA_HotelAvailNotifRQ

Maximum payload restriction of 6 MB (Megabytes)

The OTA_HotelAvailNotifRQ can become very large, depending on how many updates you push. The system currently has a payload restriction of 6 MB (Megabytes). It is recommended to keep the requests small, but execute multiple requests. You should ideally push updates as soon as they happen in your system or as soon as you receive them.

The hotel availaiblity notification request updates the property availability for the property for which the hotel code was provided in the request.

<?xml version="1.0"?>
<soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
        <AccessHeader>
            <UserName>MyUserName</UserName>
            <Password>MyPassword</Password>
        </AccessHeader>
    </soap:Header>
    <soap:Body>
        <OTA_HotelAvailNotifRQ EchoToken="wuemxniopt" 
            Version="1" MessageContentCode="3" 
            xmlns="http://www.opentravel.org/OTA/2003/05/beta">
            <AvailStatusMessages HotelCode="my-hotel-code">
                <AvailStatusMessage>
                    <StatusApplicationControl 
                        Start="2021-09-17" End="2022-10-19" 
                        RatePlanCode="standard-2568" InvTypeCode="suite" />
                    <LengthsOfStay>
                        <LengthOfStay Time="1" MinMaxMessageType="SetMinLOS" />
                        <LengthOfStay Time="0" MinMaxMessageType="SetMaxLOS" />
                    </LengthsOfStay>
                    <RestrictionStatus Restriction="Master" Status="Open" />
                </AvailStatusMessage>
            </AvailStatusMessages>
        </OTA_HotelAvailNotifRQ>
    </soap:Body>
</soap:Envelope>

Multiple AvailStatusMessage nodes

The request can contain multiple AvailStatusMessage nodes in the AvailStatusMessages node.

Available AvailStatusMessage nodes

Each AvailStatusMessage node can contain the nodes specified below with their child nodes and attributes. Other than the payload restriction, there is no limitation on how many nodes an AvailStatusMessage can contain.

Available nodes for an AvailStatusMessage

This element defines the rate, room/unit and timespan of this inventory application.

Field Description Example
Start Start date of the status application 2022-05-05
End End date of the status application 2022-05-18
RatePlanCode Code of the rate plan this application is for suite-standard
InvTypeCode Code of the room/unit this application is for suite

This element defines the minimum and maximum length of stay for this application.

Field Description Example
Time Length of stay as number 1
MinMaxMessageType Type of length of stay (min or max) SetMinLOS or SetMaxLOS

This element defines the availability of the room and rate combination for the date application.

Field Description Example
Restriction Type of restriction to apply Master, Departure or Arrival
Status Type of length of stay (min or max) Open or Close

Response contents

The response is simple and will only contain a <Success /> node when the operation was successfully completed by the system.

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <OTA_HotelAvailNotifRS EchoToken="wuemxniopt" 
            Version="1" TimeStamp="2021-09-29T18:57:39.207Z" 
            PrimaryLangID="en-US" 
            xmlns="http://www.opentravel.org/OTA/2003/05/beta">
            <Success />
        </OTA_HotelAvailNotifRS>
    </soap:Body>
</soap:Envelope>