Skip to main content

ARI Push - Inventory

10.31
Channel Connect
Inventory
ARI
SOAP API
OTA Integration

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.

The OTA_HotelInvCountNotifRQ message is used to communicate room level inventory values to client systems. Each message contains inventory for one or more room types for one hotel for one channel. 

Target Audience
OTA Integration
API Version
10.31
Authentication
Security Credentials
Service Action Code
OTA_HotelInvCountNotifRQ

The Inventory element will contain physical inventory counts for one room type for a date range. Each InvCounts element contains two InvCount elements. One to communicate the Left To Sell inventory value and one to communicate the Can Sell Up To inventory value. Room inventories with the same value will be consolidated into date ranges.

 

NOTE: Use of PUSH ARI APIs is limited to qualified OTAs with advance permission only.

Sample Request
<OTA_HotelInvCountNotifRQ xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05/OTA_HotelInvCountNotifRQ.xsd" EchoToken="" TimeStamp="2015-10-01T09:41:51.982" ="2.000" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Inventories HotelCode="10001">
        <Inventory>
            <StatusApplicationControl Start="2015-01-01" End="2015-02-28" InvTypeCode="King">
                <DestinationSystemCodes>
                    <DestinationSystemCode>330</DestinationSystemCode>
                </DestinationSystemCodes>
            </StatusApplicationControl>
            <InvCounts>
                <InvCount CountType="2" Count="8"/>
                <InvCount CountType="3" Count="10"/>
            </InvCounts>
        </Inventory>
        <Inventory>
            <StatusApplicationControl Start="2015-03-01" End="2015-03-31" InvTypeCode="King">
                <DestinationSystemCodes>
                    <DestinationSystemCode>330</DestinationSystemCode>
                </DestinationSystemCodes>
            </StatusApplicationControl>
            <InvCounts>
                <InvCount CountType="2" Count="5"/>
                <InvCount CountType="3" Count="5"/>
            </InvCounts>
        </Inventory>
        <Inventory>
            <StatusApplicationControl Start="2015-01-01" End="2015-01-01" InvTypeCode="Queen">
                <DestinationSystemCodes>
                    <DestinationSystemCode>330</DestinationSystemCode>
                </DestinationSystemCodes>
            </StatusApplicationControl>
            <InvCounts>
                <InvCount CountType="2" Count="2"/>
                <InvCount CountType="3" Count="7"/>
            </InvCounts>
        </Inventory>
        <Inventory>
            <StatusApplicationControl Start="2015-01-02" End="2015-01-31" InvTypeCode="Queen">
                <DestinationSystemCodes>
                    <DestinationSystemCode>330</DestinationSystemCode>
                </DestinationSystemCodes>
            </StatusApplicationControl>
            <InvCounts>
                <InvCount CountType="2" Count="4"/>
                <InvCount CountType="3" Count="6"/>
            </InvCounts>
        </Inventory>
    </Inventories>
</OTA_HotelInvCountNotifRQ>
Sample Response
<OTA_HotelInvCountNotifRS xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05/OTA_HotelInvCountNotifRS.xsd" TimeStamp="2015-10-01T09:41:59.982" xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Success/>
</OTA_HotelInvCountNotifRS>