The Hooroo API will post a cancellation notification message to notify to Channel Managers of cancellations to reservations made on the Hooroo booking channel. The Hooroo API will expect a message response as a synchronous operation.
The Hooroo API expects that Channel Managers will provide an HTTP endpoint that can receive the notification request as an XML payload.
The Following tags are used but left empty.
| Field | Required | Notes |
|---|---|---|
| CancelType | Y | Always "Cancel" |
| UniqueID | Y | The reservation ID that is being cancelled by this message. |
| HotelCode | Y | The code that uniquely identifies a single hotel property. |
| HotelName | N | The name of the hotel. |
| Verification | Y | Details of the person making the cancellation |
Cancellation requests will be posted to the channel manager's configured endpoint URL, for instance:
POST https://api.hotelchannelmanager.com.au/Hooroo
Body:
Channel Managers should return a response to a cancellation notification message as follows. Hooroo will store the UniqueID values provided for correlation purposes, however the values they contain can be defined by the sender. As some properties will be able to provide a PmsConfirmNumber, the CancelInfoRS element is optional.
Cancellation successfully received and confirmed:
HTTP Status Code: 200 OK
Body:
Cancellation successfully received with warnings:
HTTP Status Code: 200 OK
Body:
<?xml version="1.0" encoding="UTF-8"?>
<OTA_CancelRS TimeStamp="2009-01-15T16:53:23+08:00" Status="Cancelled" xmlns="http://www.opentravel.org/OTA/2003/05">
<Warnings>
<Warning Type='1'>Warning text</Warning>
</Warnings>
<UniqueID Type="14" ID="13353000007" ID_Context="CrsConfirmNumber"/>
<CancelInfoRS>
<UniqueID Type="14" ID="" ID_Context="PmsConfirmNumber"/> </CancelInfoRS>
</OTA_CancelRS>
HTTP status code 400 Bad Request (client error)
HTTP status code 500 Internal Server Error (server error)
Body: