Reservations Confirmation

The OTA can optionally require from WuBook the confirmation receipt of reservations. This confirmation can be used to mark all the already returned reservations and to not send them back again in the following get_bookings response, unless another event of modification/cancellation has occurred. This behavior is not mandatory, meaning that the OTA can also choose to always return all reservations in the requested date range.

Request from WooDoo

{
  "action":"confirm_bookings",
  "data":{
      "confirmBookings":[
           {
           "booking_id":"123",
           "status":"new",
           “booking_modification_id”: “1001”
           },
           {
           "booking_id":"234",
           "status":"modified",
           “booking_modification_id”: “2002”
           }
      ]
   }

Field	Mandatory	Type	Description
booking_id	Yes	String	The OTA boooking identifier to be confirmed
status	Yes	String	The status of the reservation to be confirmed
booking_modification_id	No	String	Identifier of the booking event. We will return this key-value element in booking confirmation if the same key-value element is included in booking json (pushed or returned by get_bookings)

Response from channel

{
  "code": 200,
}

Optional

In case the OTA chooses to return just the unconfirmed reservations, it would be preferable but not mandatory, to implement a variation of get_bookings service that accepts an additional parameter used to specify when any ( also) confirmed reservations should be returned (unconfirmed should be always returned)

{
"action":"get_bookings",
"data":{
    "start_time":"2015-09-20 15:00:00",
    "return_also_confirmed": true
 }
}

The default request made by WuBook will use return_also_confirmed= false, and if the key is not specified in the request, a default false value should be intended. It will be true only in particular cases in which WuBook needs to fetch again reservations already retrieved and confirmed before.