Inventory and Rate API

Owned by Luke Foxton (Unlicensed)
Last updated: 13, Apr 2023 by Paul Collado Orta
2 min read

 

  • SiteConnect uses OTA_HotelAvailNotifRQ to push Availability and Restrictions.

  • SiteConnect uses OTA_HotelRateAmountNotifRQ to push Rates and Rate settings.

SiteConnect will send the OTA_HotelAvailNotifRQ message first. Only after this message has received a successful response from the booking channel, the OTA_HotelRateAmountNotifRQ message will be sent.

Cancellation Policy, Hotel Policies, Service/Additional Fees and Taxes are not supported by SiteConnect Inventory and Rate API. These policies and fees/taxes should be configured internally within each channel/OTA admin extranet.

Inventory and Rate API Expectations:

  • We expect your endpoint to be able to respond in around 1-2 seconds on average, when looking at the updates sent throughout an hour. A sub 1s response time would be ideal.
    When processing Inventory messages, your endpoint must be able to respond with either a 'Success' or 'Error' response in a reasonable amount of time.
    SiteConnect will timeout any update request after 20 seconds. It is important to note however that the 20 seconds timeout is a failsafe. Timeouts and longer response times should never occur at volume, or present themselves persistently.

  • We urge that you complete stringent performance testing on your production servers/endpoint(s) to ensure they will scale with the number of hotels you will have connected in production.
    It is important to remember the potential for large amounts of data to be pushed out from SiteConnect.
    If a hotel enables their connection, you can potentially receive 750 days worth of Inventory, Restrictions and Rates all within a short space of time.
    If you have several properties go live at the same time or push large updates, the data load can be quite large. 

  • Ensure hotels are aware of any timezone settings that may need to be set within your Booking Channel extranet.
    Keep in mind that SiteConnect will push inventory based on the hotel's local timezone as configured in the Channel Manager (with a server TimeStamp of GMT for EMEA and AEST/AEDT for APAC). You will need to consider this when accepting Inventory push updates from SiteConnect and ensure that you don't create any timezone conflicts when processing the Inventory messages.