...
Just like the rest of the interfaces of the Hotel-Spider system, the SpiderConnect interfaces are based on the OTA (Open Travel Alliance) protocol. In order to make the integration work easier for an online booking solution, the Hotel-Spider system can either PUSH the inventories, prices and stay restrictions via HTTP RAW POST or via SOAP.
The reservations/modifications/cancellations must can be PUSHED from the online booking solution to the Hotel-Spider system. The Hotel-Spider system will then immediately confirm that the reservation/modification/cancellation has correctly been imported and will return the unique ID the reservation will have received in the Hotel-Spider system.
Otherwise the reservations/modifications/cancellations can be PULLED by the Hotel-Spider system from the online booking solution. The Hotel-Spider system when then, in a second call, confirm that the reservation/modification/cancellation has correctly been imported with the unique ID the reservation will have received in the Hotel-Spider system.
Disregarding which communication scheme is used for transferring reservations/modifications/cancellations from the online booking system to the Hotel-Spider system, the online booking solution must store this confirmation number with the transmitted reservation.
...