Developer Guide - Connectivity Interface
Overview and general information
The goal of the Connectivity Interface from Kurzurlaub.de is the connection as booking channel to OTA partners.
It contains a set of Open Travel Alliance (OTA) compliant messages that allows OTA Partners to query a list of rooms and rates from the connected channel Kurzurlaub.de for a particular hotelier to allow hoteliers to map channels rooms to Kurzurlaub.de rooms for easier setup and processing.
OTA Partners can push availability and rates to the Kurzurlaub.de as the connected channel.
OTA Partners ca pull reservations, modifications and cancellations from Kurzurlaub.de or we can push them too.
Parts of our Developer Guide
General information about the Connectivity API parts
Supported OTA Messages
We recommend the following messages for the standard functions
- OTA_HotelDescriptiveInfoRQ/RS - Used to retrieve a list of active rooms for a hotel
-
OTA_HotelAvailRQ/RS - Used to retrieve a list of active rooms and rates for a hotel
-
OTA_HotelInvCountNotifRQ/RS - Used to update availability and Restrictions
-
OTA_HotelRateAmountNotifRQ/RS - Used to update rates and Restrictions for RoomType/RatePlan Combinations
-
OTA_HotelResNotifRQ/RS - Used to deliver reservations, modifications and cancellations
-
OTA_HotelBookingRuleRQ - Used to retrieve a list of active Restrictions for a hotel
- OTA_HotelBookingRuleNotifRQ - Used to update Restrictions for a hotel
See also - List of all supported OTA messages for each Part - Roadmap - First steps to use our OTA - REST-API
Communications
Communication between both systems is via the exchange of XML or SOAP messages over secure HTTP (HTTPS). Operations are synchronous request/response pairs. A message is considered to be atomic and is either processed entirely or not at all by the Web Service.
Security
Encryption should be provided by the transport layer via HTTPS.
Open Travel Alliance (OTA)
The Connectivity Service is based on the Open Travel Alliance (OTA) specifications for version 2010A / 2010B and some parts of 2017B.
Although this document attempts to be technically comprehensive it is expected that the connecting system’s developers be somewhat familiar with the OTA specifications found here opentravel.org).