# Acknowledging new reservations Booking.com maintains all incoming reservations specific to a provider using a dedicated queue. For OTA implementation, Booking.com waits until you acknowledge receiving the reservations successfully before removing the acknowledged reservations from the queue. Otherwise, Booking.com 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 ```http POST https://secure-supply-xml.booking.com/hotels/ota/OTA_HotelResNotif ``` Use the `POST OTA_HotelResNotif` endpoint to acknowledge a new reservation. When acknowledging you can send one of the following status: - Successfully processed - Booking.com acknowledges and removes the reservation from the queue. - Unsuccessfully processed - Booking.com keeps the reservations in the queue until you acknowledge successfully or until the timeout period. 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: | Element | Attribute | Description | Type | Required/Optional | Notes | | --- | --- | --- | --- | --- | --- | | `OTA_HotelResNotifRS` | | Root element. | object | required | | | | `TimeStamp` | | datetime | required | | | | `Target` | | Enumerated string | required | | | **>** `HotelReservations` | | | object | required | | | **>>** `HotelReservation` | | | object | required | | | **>>>** `ResGlobalInfo` | | | object | required | | | **>>>>** `HotelReservationIDs` | | Contains the reservation IDs for acknowledgement. | object | required | | | **>>>>>** `HotelReservationID` | | Contains individual reservation ID for acknowledgement | object | required | | | | `ResID_Value` | Specifies the Booking.com reservation ID. | integer/alphanumeric | required | See the `` element in the matching `GET` response: [`OTA_HotelResNotif` for new reservations](/connectivity/docs/reservations-api/retrieving-new-reservations-ota#hotelreservationids) or [`OTA_HotelResModifyNotif` for modified or cancelled reservations](/connectivity/docs/reservations-api/retrieving-modifcancel-reservations-ota#hotelreservationids). The following instructions apply only when the [*OTA hotel reservation response token* (`ota_res_response_token`) feature](/connectivity/docs/reservations-api/retrieving-new-reservations-ota#include-reservationid) 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 matching `GET` call. | | | `ResID_Source` | Specify the reservation source. Only applicable when the *OTA hotel reservation response token* feature is enabled. | enumerated string | optional | Accepts the value `BOOKING.COM`. If you omit the attribute, the API treats the source as `BOOKING.COM`. | | | `ResID_Type` | Specifies the Booking.com Reservation type. Only applicable when the *OTA hotel reservation response token* feature is enabled. | enumerated string | optional | Make sure to copy and paste the `` elements under `` from the matching `GET` response: [`OTA_HotelResNotif` for new reservations](/connectivity/docs/reservations-api/retrieving-new-reservations-ota#hotelreservationids) or [`OTA_HotelResModifyNotif` for modified or cancelled reservations](/connectivity/docs/reservations-api/retrieving-modifcancel-reservations-ota#hotelreservationids). 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_Value`s. If you omit `ResID_Type`, the API treats the element as `ResID_Type="14"`. Every acknowledgement must contain at least one `HotelReservationID` with `ResID_Type="14"` and `ResID_Source="BOOKING.COM"`; otherwise the API returns an `HTTP 400` error. | | | `ResID_Date` | Specifies the date and time when the reservation was created. | datetime | optional | Applies only to the `HotelReservationID` element that carries the numeric reservation ID, not to the response-token element (`ResID_Type="18"`). Copy the value from the `` element in the matching `GET` response. If the value is not available, omit the attribute; do not send a placeholder value. Format: ISO 8601, for example `2026-07-06T06:40:53`. | | **>** `Success` | | Specifies successful processing of the reservation. | object | required if `Errors` is not specified | | | **>** `Errors` | | Contains the error details in case of failure to process the reservation. | object | required if `HotelReservations` is not specified | | | **>>** `Error` | | Contains information about individual errors. | object | | | | | `Code` | Specifies the error code. | string | | Specify a numeric error code. The example below uses `193` with the short text `Confirm reservation not processed`. | | | `RecordID` | Specifies the Booking.com reservation ID. | string | | | | | `ShortText` | Specifies 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 ``` ##### Acknowledging unsuccessful Processing The following is a request body example to acknowledge unsuccessful processing: ```xml ``` #### Response body example ```xml ``` #### Response body elements The following table describes the response elements: | Element | Attribute | Description | Type | Notes | | --- | --- | --- | --- | --- | | `OTA_HotelResNotifRS` | | Root element. | object | | | **>** `Success` | | Contains the success status of the request. | object | | | **>** `Errors` | | Contains the error details. | object | | | **>>** `Error` | | Contains information about individual errors. | object | | | | `Type` | Specifies the error type. | string | | | | `Code` | Specifies the error code. | string | | | | `Status` | Specifies the reservation's processing status. | string | | | | `ShortText` | Specifies a short description of the error. | string | | | `RUID` | | Specifies the Booking.com `RUID` string, which is an encoded string used by the Booking.com staff to trace back any updates made before. | object | Whenever 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 Booking.com technical staff to provide Connectivity Partners with support. | #### Quick Actions → For troubleshooting information, see [Troubleshooting and list of error codes.](/connectivity/docs/reservations-api/reservations-troubleshooting)