Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Ensure to pull reservations every 2-5 minutes. In other words, reservations / modifications / cancellations should never be requested more often than every 2 minutes and less often that every 5 minutes.

3.2 - Steps involved

Make sure to cover all the steps involved in the Reservation API for each reservation / modification / cancellation (if applicable):

...

Make sure to confirm the reservation delivery and send us back the affected availability as fast as possible, preferably under 1 minute.

3.3 - Availability pass back request

This is a delta update meaning that only the affected availability should be sent through. Note, The Channel Manager does NOT top up the availability after a modification / cancellation delivery. As a result, ensure the following:

...

  • Check-in: 13th of December 2018

  • Check-out: 16th of December 2018

Expected - the availability has been topped up for the 12th of December as BDC-856972 modified reservation does NOT cover this date anymore, hence the availability goes back to “3”. However, there’s a new check-out date (16th of December 2018) and therefore 15th of December has to be reduced to “2”. There’s no change for the 13th and the 14th of December.

...

The modified reservation BDC-856972 has been cancelled. 

Expected - availability top up back to “3” for all dates affected by this cancellation:

Code Block
languagexml
<AvailStatusMessages HotelCode="ABC">
	<AvailStatusMessage BookingLimit="3">
		<StatusApplicationControl Start="2018-12-13" End="2018-12-15" InvTypeCode="DBL"/>
	</AvailStatusMessage>
</AvailStatusMessages>

3.4 - OTA_NotifReportRQ

Confirmation request specification:

...

Code Block
languagexml
<HotelNotifReport>
	<HotelReservations>
		<HotelReservation LastModifyDateTime="2018-06-21T11:45:05+04:00" ResStatus="Modify">
			<UniqueID Type="16" ID="3123457"/>
			<ResGlobalInfo>
				<HotelReservationIDs>
					<HotelReservationID ResID_Type="14" ResID_Value="BDC-856972"/>
				</HotelReservationIDs>
			</ResGlobalInfo>
		</HotelReservation>
	</HotelReservations>
</HotelNotifReport>

3.5 - Error handling

If a reservation cannot take place (for instance, your PMS doesn’t support overbookings and there’s no availability), ensure to be as specific as possible in your error response. Hoteliers receive this message, so being as specific as possible in your error response will help them to troubleshoot without having go through our or your support teams.

...