Hotel Technology Next Generation (HTNG)

Thoug the interface is developped according to the specifications, it has not been certified officially by the association that fosters the HTNG guidelines. At this point in time the Hotel-Spider system has implementations taken from the Product Distribution. For this the following services are available

4. Alternative : soap capsule

If you prefer, you can use simple OTA Port in SOAP :

Staging : https://staging.hotel-spider.ch/soap/OTA/OTAService/wsdl

Production : https://extranet.hotel-spider.ch/soap/OTA/OTAService/wsdl

Authentication with SOAP HTNG

Contrary to OTA messages, we don't use the OTA POS node.

Authentication is done via the standardized WSSE :

<soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:oas="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
    xmlns:oas1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
    xmlns:ns="http://www.opentravel.org/OTA/2003/05">
    <soapenv:Header>
        <oas:Security>
            <oas:UsernameToken>
                <oas:Username>LOGIN</oas:Username>
                <oas:Password>PASSWORD</oas:Password>
            </oas:UsernameToken>
        </oas:Security>
    </soapenv:Header>
    <soapenv:Body>
        <ns:OTA_ReadRQ >
            <ns:ReadRequests>
                <ns:HotelReadRequest HotelCode="" HotelName="">
                    <ns:SelectionCriteria SelectionType="Undelivered" DateType="" Start="" End="" />
                </ns:HotelReadRequest>
            </ns:ReadRequests>
        </ns:OTA_ReadRQ>
    </soapenv:Body>
</soapenv:Envelope>

Hotel Technology Next Generation (HTNG)

1. ARIAndReservationPullService

2. ARIAndReservationPushService

3. SystemReadiness

4. Alternative : soap capsule

Authentication with SOAP HTNG