OTA_ReadRQ / OTA_HotelResNotifRQ or OTA_ResRetrieveRS

Response format

Depending on the preferences of the third party software provider, the Hotel-Spider system will either reply to an OTA_ReadRQ with an OTA_HotelResNotifRQ (asynchronous usage) or with an OTA_ResRetrieveRS response.  By default, our system will reply with the OTA_HotelResNotifRQ format. For other formats, please contact us.

Confirming successful import

Disregarding which response format the Hotel-Spider system will return the third party software client needs to confirm every reservation/modification/cancellation it has imported via an OTA_HotelResNotifRS / OTA_HotelResNotifRS or an OTA_NotifReportRQ / OTA_NotifReportS call.

Reservation are automatically flagged as exported after 5 reads

After any reservation has been returned 5 times (with SelectionType set to Undelivered) it will be marked as exported, and thus will not be returned in the subsequent responses to OTA_ReadRQ requests.

Credit-card information specifics

If your system is PCI-DSS compliant and you are using the secure endpoints, please be aware that credit-card number is returned in clear text in response to the first read request only

The next responses will contain only the masked card number.

Regarding the CVC code, please be aware that it can be exported only one time, either on the extranet or through the API. If the CVC code as been shown in the extranet, it will be be present in the response.

Retrieving a specific reservation/modification/cancellation

When using Type="22", the value of the ID attribute need to be the reservation confirmation number of the booking channel from which the reservation originated. So should a reservation originate from Booking.com, their reservation confirmation should be used. Should a reservation originate from Expedia.com, their reservation confirmation should be used, etc.

Note on Start and End date limitations

• 'Start' date and 'End' date are both required on request. If only one of them is missing the response will be an error message.

• The distance between 'Start' and 'End' date must not exceed 30 days. Otherwise it will change End date to 30 days from Start.

• If both 'Start' and 'End' date are missing then a default date will be assigned:
  'Start' =  today
  'End' = today + 30 days

Use case 1: Query the Hotel-Spider system for new reservations, modifications and cancellations

 <?xml version="1.0" encoding="utf-8"?>
<OTA_ReadRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_ReadRQ.xsd" TimeStamp="2003-03-17T09:30:47-05:00" Target="Test">
  <POS>
    <Source>
      <RequestorID ID="USERNAME" MessagePassword="PASSWORD" />
  </Source>
  </POS>
  <ReadRequests>
    <HotelReadRequest HotelCode="" HotelName="">
      <SelectionCriteria SelectionType="Undelivered" />
    </HotelReadRequest>
  </ReadRequests>
</OTA_ReadRQ>

Use case 2: Query for reservations created between Start and End date

<?xml version="1.0" encoding="utf-8"?>
<OTA_ReadRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_ReadRQ.xsd" TimeStamp="2003-03-17T09:30:47-05:00" Target="Test">
  <POS>
    <Source>
      <RequestorID ID="USERNAME" MessagePassword="PASSWORD" />
   </Source> 
  </POS>
  <ReadRequests>
    <HotelReadRequest HotelCode="" HotelName="">
      <SelectionCriteria SelectionType="All" DateType="CreateDate" Start="2015-11-01" End="2015-11-30" />
    </HotelReadRequest>
  </ReadRequests>
</OTA_ReadRQ>

Use case 3: Query for reservations with modification date between Start and End

<OTA_ReadRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_ReadRQ.xsd" TimeStamp="2003-03-17T09:30:47-05:00" Target="Test">
  <POS>
    <Source>
      <RequestorID ID="USERNAME" MessagePassword="PASSWORD" />
  </Source>
  </POS>
  <ReadRequests>
    <HotelReadRequest HotelCode="" HotelName="">
      <SelectionCriteria SelectionType="All" DateType="LastUpdateDate" Start="2015-11-01" End="2015-11-30" />
    </HotelReadRequest>
  </ReadRequests>
</OTA_ReadRQ>

Use case 4: Query for reservations with arrival date between Start and End

<OTA_ReadRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_ReadRQ.xsd" TimeStamp="2003-03-17T09:30:47-05:00" Target="Test">
<POS>
    <Source>
      <RequestorID ID="USERNAME" MessagePassword="PASSWORD" />
  </Source>
  </POS>
  <ReadRequests>
    <HotelReadRequest HotelCode="" HotelName="">
      <SelectionCriteria SelectionType="All" DateType="ArrivalDate" Start="2015-11-01" End="2015-11-30" />
    </HotelReadRequest>
  </ReadRequests>
</OTA_ReadRQ>

Use case 5: Query for reservations with departure date between Start and End

<OTA_ReadRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_ReadRQ.xsd" TimeStamp="2003-03-17T09:30:47-05:00" Target="Test">
<POS>
    <Source>
      <RequestorID ID="USERNAME" MessagePassword="PASSWORD" />
  </Source>
  </POS>
  <ReadRequests>
    <HotelReadRequest HotelCode="" HotelName="">
      <SelectionCriteria SelectionType="All" DateType="DepartureDate" Start="2015-11-01" End="2015-11-30" />
    </HotelReadRequest>
  </ReadRequests>
</OTA_ReadRQ>

Use case 6: Query for a specific reservation using the Hotel-Spider ID

<OTA_ReadRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_ReadRQ.xsd" TimeStamp="2003-03-17T09:30:47-05:00" Target="Test">
<POS>
    <Source>
      <RequestorID ID="USERNAME" MessagePassword="PASSWORD" />
  </Source>
  </POS>
 <UniqueID Type="14" ID="005LDSDFD0134687321" />
</OTA_ReadRQ>

Use case 7: Query for a specific reservation using the channel's ID

<OTA_ReadRQ xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_ReadRQ.xsd" TimeStamp="2003-03-17T09:30:47-05:00" Target="Test">
<POS>
    <Source>
      <RequestorID ID="USERNAME" MessagePassword="PASSWORD" />
  </Source>
  </POS>
 <UniqueID Type="22" ID="87654321" />
</OTA_ReadRQ>

Root element

Depending on the response format requested by the third party software provider, the response will either contain the OTA_HotelResNotifRQ or the OTA_ResRetrieveRS as the root element.

HotelReservation parent element

Depending on the response format requested by the third party software provider, the response will either contain the HotelReservations or the ReservationsList as the container for all the reservations to be exported.