Skip to main content

Change Discovery

10.18
Hotel
ARI
SOAP API
Hospitality

The OTA_HotelCacheChangeRQ message allows partners to query SynXis CR to identify rate and availability changes in SynXis CR, so that the partner can send a targeted shop to SynXis to get the updated availability. 

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.18
Authentication
Security Credentials
Service Action Code
OTA_HotelCacheChangeRQ

OTA and Metasearch partners that shop SynXis to cache rates and availability experience reduced shopping volumes and more accurate and up to date availability by implementing Change Discovery Service.

The OTA_HotelCacheChangeRQ/CacheSearchCriteria/@CacheFromTimeStamp is populated with a time and date that occurs in the past. This value is the starting point for which rate and availability changes are requested, ending with the current time of the request. Requests return a value for a maximum of two weeks in the past until the present. Partners are advised to work with Sabre Hospitality Solutions to determine the correct interval of time to use for their needs.

The following attributes are required to define the parameters that are being sent in the query in OTA_HotelCacheChangeRQ/CacheSearchCriteria/

  • CacheSearchCriterion/@HotelCode - contains the valid SynXis Hotel ID.
  • CacheSearchCriterion/@CacheStartDateTime - contains the start date of the range being queried. The earliest possible date is the current date and latest supported date is 3 years from the current date.
  • CacheSearchCriterion/@CacheEndDateTime - contains the end date of the range being queried. The earliest possible date is the current date and latest supported date is 3 years from the current date.

Multiple instances of the CacheSearchCriterion may be used in a message to request different HotelCode instances or different date ranges.

Sample Request
<OTA_HotelCacheChangeRQ EchoToken="EchoMessage" TimeStamp="2018-08-17T06:00:00+00:00" Version="3.000">
 <CacheSearchCriteria AvailabilityInd="true" RatesInd="true" HotelContentInd="false" CacheFromTimestamp="2018-11-10T12:00:00:+01:00">
  <CacheSearchCriterion HotelCode="65561" CacheStartDateTime="2018-11-16T00:00:00Z" CacheEndDateTime="2018-11-25T00:00:00"/>
  <CacheSearchCriterion HotelCode="65355" CacheStartDateTime="2018-12-05T00:00:00" CacheEndDateTime="2018-12-12T00:00:00"/>
 </CacheSearchCriteria>
</OTA_HotelCacheChangeRQ>
Sample Response
<OTA_HotelCacheChangeRS EchoToken="EchoMessage" TimeStamp="2018-11-15T07:44:51+00:00" Version="3.000" xmlns="http://www.opentravel.org/OTA/2003/05">
 <Success/>
 <CacheChangeInfo HotelCode="65561" AvailabilityInd="true" RatesInd="true" HotelContentInd="false">
  <TimeSpan Start="2018-11-16" End="2018-11-18" ChangeDateMask="101"/>
 </CacheChangeInfo>
 <CacheChangeInfo HotelCode="65355" AvailabilityInd="true" RatesInd="true" HotelContentInd="false">
  <TimeSpan Start="2018-12-05" End="2018-12-12" ChangeDateMask="11110011"/>
 </CacheChangeInfo>
</OTA_HotelCacheChangeRS>