Transmission of the reservations

Every time a reservation is made, modified or cancelled on an online booking system, it needs to be transferred to the Hotel-Spider servers so that it can decrement and/or increment the properties availabilities. The reservations can either be pushed from the online booking system to the Hotel-Spider servers or the Hotel-Spider servers can poll / query the online booking system for newly made, modified or cancelled reservations.

Preferred method

The preferred way to transmit reservations to the Hotel-Spider servers is the PUSH method.

Reservation polling / pulling end-of-life

The polling will be progressively phased out in 2022. As such any new integrations must transmit reservations to the Hotel-Spider servers with the PUSH method.

Re-use of previous implementations

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 two distinct methods to cope with the reservation transmission:

In some cases, additional items can be reserved together with the hotel stay such as breakfasts, massages, ski passes etc. In the OTA vocabulary, they are defined as services. Whatever the choosen method for sending reservations to the Hotel-Spider severs (push or pull), the services are defined using the same format in the XML message. Refer to the page Transmission of the services as part of reservations for more information.