Hotel Technology Next Generation (HTNG)

Though the interface is developed 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

1. ARIAndReservationPullService

• Non Secure
  • Staging: https://staging-api.hotel-spider.com/soap/htng/ARIAndReservationPullService
  • Production: https://api.hotel-spider.com/soap/htng/ARIAndReservationPullService
• Secure (PCI-DSS certified, allow transmission of Credit Card details)
  • Staging: https://secure-staging-api.hotel-spider.com/soap/htng/ARIAndReservationPullService
  • Production: https://secure-api.hotel-spider.com/soap/htng/ARIAndReservationPullService

2. ARIAndReservationPushService

• Non Secure
  • Staging: https://staging-api.hotel-spider.com/soap/htng/ARIAndReservationPushService
  • Production: https://api.hotel-spider.com/soap/htng/ARIAndReservationPushService
• Secure (PCI-DSS certified, allow transmission of Credit Card details)
  • Staging: https://secure-staging-api.hotel-spider.com/soap/htng/ARIAndReservationPushService
  • Production: https://secure-api.hotel-spider.com/soap/htng/ARIAndReservationPushService

3. SystemReadiness

• Non Secure
  • Staging: https://staging-api.hotel-spider.com/soap/htng/SystemReadinessService
  • Production: https://api.hotel-spider.com/soap/htng/SystemReadinessService
• Secure (PCI-DSS certified, allow transmission of Credit Card details)
  • Staging: https://secure-staging-api.hotel-spider.com/soap/htng/SystemReadinessService
  • Production: https://secure-api.hotel-spider.com/soap/htng/SystemReadinessService

4. Alternative : soap capsule

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

• SOAP
  • Staging: https://staging-api.hotel-spider.com/soap/ota
  • Production: https://api.hotel-spider.com/soap/ota
• SOAP Secure Endpoints if your system is PCI-DSS certified (allow transmission of Credit Card details)
  • Staging: https://secure-staging-api.hotel-spider.com/soap/ota
  • Production: https://secure-api.hotel-spider.com/soap/ota

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>