Last updated

Acknowledging new reservations maintains all incoming reservations specific to a provider using a dedicated queue. For OTA implementation, waits until you acknowledge receiving the reservations successfully before removing the acknowledged reservations from the queue. Otherwise, forwards the missed reservations as an email to the property after a specific time period.

By acknowledging reservations, you confirm:

  • Retrieving the most updated reservation details.
  • Processing the retrieved reservation.

To acknowledge new reservations


Use the POST OTA_HotelResNotif endpoint to acknowledge a new reservation. When acknowledging you can send one of the following status:

  • Successfully processed - acknowledges and removes the reservation from the queue.
  • Unsuccessfully processed - keeps the reservations in the queue until you acknowledge successfully or until the timeout period.

Use the POST OTA_HotelResNotif endpoint to acknowledge processing the reservations.

Confirm each reservation

Make sure to confirm every reservation message in separate requests or in one request using the HotelReservationID tag multiple times.

Request body parameters

The following table describes the elements you can add in the request body:

OTA_HotelResNotifRSRoot element.objectrequired
TargetEnumerated stringrequired
> HotelReservationsobjectrequired
>> HotelReservationobjectrequired
>>> ResGlobalInfoobjectrequired
>>>> HotelReservationIDsContains the reservation IDs for acknowledgement.objectrequired
>>>>> HotelReservationIDContains individual reservation ID for acknowledgementobjectrequired
ResID_ValueSpecifies the reservation ID.integer/alphanumericrequiredSee the <HotelReservationIDs> element in the GET OTA_HotelResNotif response.
The following instructions are applicable only when the OTA hotel reservation response token (ota_res_response_token) feature is enabled.
To acknowledge a reservation that was changed since you last retrieved the reservation details, you must provide an additional HotelReservationID element with an alphanumeric value in the ResID_Value.
You can copy and paste both the HotelReservationID elements from the GET call.
ResID_SourceSpecify the reservation source. Only applicable when the OTA hotel reservation response token feature is enabled.objectoptional
ResID_TypeSpecifies the Reservation type. Only applicable when the OTA hotel reservation response token feature is enabled.enumerated stringoptionalMake sure to copy and paste the <HotelReservationID> elements under the <HotelReservationIDs> from the GET response. See the OTA_HotelResNotif endpoint response.
Can contain the following values:
- 14: To acknowledge a new reservation
- 18: To acknowledge a reservation that was modified since the last retrieval. When using this value, make sure to provide both the ResID_Values.
> SuccessSpecifies successful processing of the reservation.objectrequired if Errors is not specified
> ErrorsContains the error details in case of failure to process the reservation.objectrequired if HotelReservations is not specified
>> ErrorContains information about individual errors.object
CodeSpecifies the error code.stringAccepts the value: 193.
RecordIDSpecifies the reservation ID.string
ShortTextSpecifies a short error description.string

Request body example

This section contains request body examples for acknowledging both the successful and unsuccessful processing of reservations.

Acknowledging successful Processing

The following is a request body example to acknowledge successful processing:

<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelResNotifRS TimeStamp="2021-11-13T10:09:55" Target="Production">
                <HotelReservationID ResID_Value="2354004229"/>

Acknowledging unsuccessful Processing

The following is a request body example to acknowledge unsuccessful processing:

<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelResNotifRS TimeStamp="2022-10-03T10:09:55" Target="Production">
        <Error Code="193" RecordID="1568716590" ShortText="Cancellation process failed"/>
<!-- RUID: [UmFuZG9tSVYkc2RlIyh9Yce1+/cI+G+pb7C0OSjMDvMV8eZlQpzLr3zTwMpAkL86fWfi+yaaYNfMbXer+VcX8uSZ5qjAiL7X5e5c3M8PjyY=] -->

Response body example

<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelResNotifRS xmlns="" xmlns:xsi="" xsi:schemaLocation=" OTA_HotelResNotifRS.xsd" TimeStamp="2022-10-03T13:41:45+00:00" Target="Production" Version="2.001">
<Success />

<!-- RUID: [UmFuZG9tSVYkc2RlIyh9YQMydIV8Fx+o2Wqv/rSFjVhPQmNTNQOh0DHFllDlnQOBEtga8499WE8bMlo2GY/YYsGg5ebeklLwRietn9CAsVs=] -->

Response body elements

The following table describes the response elements:

OTA_HotelResNotifRSRoot element.object
> SuccessContains the success status of the request.object
> ErrorsContains the error details.object
>> ErrorContains information about individual errors.object
TypeSpecifies the error type.string
CodeSpecifies the error code.string
StatusSpecifies the reservation's processing status.string
ShortTextSpecifies a short description of the error.string
RUIDSpecifies the RUID string, which is an encoded string used by the staff to trace back any updates made before.objectWhenever the Connectivity Partner wishes the XML-Team to look at any logfiles for debugging or the like; the RUID string needs to be provided. This will enable the technical staff to provide Connectivity Partners with support.

Quick Actions

→ For troubleshooting information, see Troubleshooting and list of error codes.