As explained in the "Different levels of data" chapter in the beginning of this documentation, the booking rules in Hotel-Spider are managed on 4 different levels. However, since we do not expected from an online booking system to also maintain these 4 levels, the online booking system needs to inform us of which booking rules are maintained on which level.
Warning | ||
---|---|---|
| ||
Only the booking rules agreed on and available on the online booking system at time of the integration testing will be transmitted from the Hotel-Spider system towards the online booking system. |
Tip | ||
---|---|---|
| ||
Aware that establishing and maintaining interfaces with multiple providers can be time-consuming, the Hotel-Spider system disposes of multiple methods to interface with on online booking system. Should an OTA interface with a competitor and/or partner of Hotel-Spider already have been implemented, then it should be easy to re-use that code for interfacing with the Hotel-Spider system. On the other hand, once an interface with the Hotel-Spider system has been developped, it can quite certainly be re-used to connect with our competitors and/or partners. |
Precisely for the reason described above, the Hotel-Spider has several distinct methods to transmit the agreed booking rules for the agreed levels:
- Transmission of the booking rules based on OTA_HotelAvailNotifRQ / OTA_HotelAvailNotifRS
- Transmission of the booking rules based on OTA_HotelBookingRuleNotifRQ / OTA_HotelBookingRuleNotifRS