For now, partners can only move reservations to different dates, keeping the length of stay and price unchanged.

Report reservations changes

Use the Reporting API to report the following types of changes to a reservation:

• Guest provided invalid credit card
• Changes to check-out date and/or price
• Cancellation due to guest no-show
• Cancellation due to invalid credit card
• Guest misconduct

Read on for details about each reporting function. To learn more about the commercial and design aspects of the Reporting API, try these additional materials:

• The slideshow Provider Handbook: Reporting API explains the commercial benefits of using the Reporting API.
• The slideshow Reporting API: UI Handbook for Providers provides guidelines on how to design UI components related to the Reporting API.

Reporting endpoint URL

Use the following method and URL to call the Reporting API:

POST https://supply-xml.booking.com/hotels/xml/reporting

Request body

Report invalid credit card

Properties can mark credit cards as invalid if the card doesn't meet validation conditions (card expired, incorrect number, insufficient funds, etc.).

An invalid credit card can be reported immediately after the reservation is made, or up until midnight (00:00) on the day of check-in, in the property's local timezone. You can report a credit card as invalid for the entire reservation and not per room basis.

Example request: cc_is_invalid

<request>
  <reservation_id>123456789</reservation_id>
  <report>cc_is_invalid</report>
</request>

After a credit card is reported as invalid, the booker receives an email and SMS from Booking.com inviting them to enter a different, valid credit card details before a deadline. The deadline depends on when the reservation was made, relative to the planned check-in day and time. Read more about this in our Partner Help.

If the booker does not enter valid credit card details before the deadline, the property may cancel the reservation. See Report cancellation due to invalid credit card.

Example responses: cc_is_invalid

Success

<status>enqueued</status>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Error 400: Credit card not required for reservation

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"You cannot mark credit card as invalid since it is not required"</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Error 400: Credit card is already marked as invalid

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Card is already marked as invalid"</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Error 400: Reservation still being processed

We recommend waiting at least 1 minute after receiving a reservation before reporting an invalid credit card.

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"You cannot mark credit card as invalid. Please try again later"</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Report cancellation due to invalid credit card

A property may cancel a reservation if the guest's credit card details are invalid and certain conditions are met. Read more about these conditions in our Partner Help.

Example request: cancel_reservation_invalid_cc

<request>
   <reservation_id>123456789</reservation_id>
   <report>cancel_reservation_invalid_cc</report>
</request>

Example responses: cancel_reservation_invalid_cc

Success

<status>ok</status>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Error 400: Reservation can't be cancelled

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Cannot cancel the reservation. Make sure all preconditions are met"</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Report stay change

A property can change the check-out date of a room and set a new price for the reservation. The booker automatically receives a confirmation email with the new reservation dates and/or price.

A stay can be changed if:

• the guest has already checked in
• the status of the reservation allows modifications
• the reservation is not overbooked
• the property does not use payments by Booking.com or online payments. For more information on payments, see payments.
• the change does not involve setting a new check-out date for a stay whose check-out date was already changed in the last 24-hour period (calculated as 00:00–23:59 CE(S)T)

The new stay must meet these conditions:

• the stay length is at least 1 night
• if the reservation is non-refundable, the new price must not be lower than the original price

Example request: stay_change

<request>
   <reservation_id>123456789</reservation_id>
   <stay_change>
      <roomreservation_id>2345678</roomreservation_id>
      <checkin>2017-01-02</checkin>
      <checkout>2017-01-05</checkout>
      <price>1000</price>
   </stay_change>
   <stay_change>
      <roomreservation_id>3456789</roomreservation_id>
      <checkin>2017-01-03</checkin>
      <checkout>2017-01-06</checkout>
      <price>900</price>
   </stay_change>
</request>

Example responses: stay_change

Success

<status>enqueued</status>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Error 404: Room reservation not found

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Not found error: room reservation could not be found."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Error 400: Room reservation doesn't belong to this property

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Room reservation not within right hotel reservation."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Error 400: Direct payment property

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Not able to change stay for a direct payment hotel."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Report guest no-show

If a guest doesn't show up on the planned check-in date, the property may mark the reservation (or a specific room in a multi-room reservation) as "no show". This results in either a cancellation or a modification, depending on if it is a complete or partial no-show.

The property can waive no-show fees, if desired. This means Booking.com will not charge commission for the reservation.

You can mark a reservation as a no-show from 00:00 (midnight, in property's local time) on the planned check-in date, up to 48 hours after the planned check-out date, provided that:

• the status of the reservation allows modifications
• the reservation isn't overbooked

A room reservation won't be considered a part of the reservation anymore if the reservation is marked as a no-show.

The property reserves the right to charge no-show fees (unless waived), in line with their cancellation policies listed on Booking.com.

The booker will receive an email explaining that (part of) their reservation has been cancelled. If the property did not waive the cancellation fees, the email will also instruct the booker to pay any cancellation costs outlined on Booking.com.

Example request: is_no_show

This request reports the full reservation as a no-show.

<request>
   <reservation_id>1234567</reservation_id>
   <report waived_fees="yes">is_no_show</report>
</request>

This request reports one room in the reservation as a no-show.

<request>
   <reservation_id>1234567</reservation_id>
   <report>
      <is_no_show roomreservation_id="2345678" waived_fees="yes" />
   </report>
</request>

Example responses: is_no_show

Success

<status>enqueued</status>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Error 400: Too early to cancel

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Not able to cancel booking earlier than 1 day after the check in."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Error 400: Too late to cancel

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Not able to cancel booking later than 2 days after the check in."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Error 400: Can't cancel, overbooked

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Not able to cancel overbooked."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Error 400: Can't cancel, unmodifiable booking

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Not able to cancel unmodifiable booking."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY] -->

Report guest misconduct

If a guest did damage to the property or performed any other misconduct - you can perform a report.

This type of report can only be done after reservation check-in date and no later than 7 days after check-out date.

In order to report a guest misconduct you need to:

1. Retrieve all the possible guest misconduct categories and subcategories via Misconduct Categories Call.
   • Some report types require you to provide additional fields (for example, Property Damage category). You can find their descriptions in the additional_fields section of the resulting xml.
2. Send a request with corresponding category/subcategory and additional fields.

Provide all the details using the misconduct_details object (see an example below).

Request body parameters

All the fields are mandatory, unless otherwise specified.

Example request: guest_misconduct - Breaking House Rules

The request below reports reservation as guest misconduct with: category #7 (Breaking House Rules) and subcategory #170 (Smoking)

<request>
   <reservation_id>123456789</reservation_id>
   <report>guest_misconduct</report>
   <misconduct_details>
   		<category_id>7</category_id>
   		<subcategory_id>170</subcategory_id>
   		<details_text>Guest was smoking in the room.</details_text>
   		<escalate_report>0</escalate_report>
   		<rebooking_allowed>1</rebooking_allowed>
   </misconduct_details>
</request>

Example request: guest_misconduct - Property damage

The request below reports reservation as guest misconduct with: category #9 (Property damage).

Note that this category has no subcategories, so no subcategory_id is provided.

<request>
   <reservation_id>123456789</reservation_id>
   <report>guest_misconduct</report>
   <misconduct_details>
   		<category_id>9</category_id>
        <damage_type_id>1</damage_type_id>
        <damage_cost>100</damage_cost>
   		<details_text>Guest left the property dirty and one of chairs was broken.</details_text>
   		<escalate_report>1</escalate_report>
   		<rebooking_allowed>0</rebooking_allowed>
   </misconduct_details>
</request>

Example responses: guest_misconduct

Success

<status>ok</status>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Error - subcategory_id is invalid

<reporting>
    <fault code="400">
        <string>Misconduct `subcategory_id` is invalid or subcategory does not belong to selected `category_id`</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Error - details_text is too long

<reporting>
    <fault code="400">
        <string>Misconduct `details_text` cannot exceed 240 characters</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Troubleshooting common error messages

Error 404: Reservation not found

These are general error messages that the API can return for any of the above requests.

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="404">
        <string>"Reservation 1234567 not found."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Error 400: Bad request

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="400">
        <string>"Either a report or a stay change is required."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Error 500: Generic error

<?xml version='1.0' standalone='yes'?>
<reporting>
    <fault code="500">
        <string>"Internal server error."</string>
    </fault>
</reporting>
<!-- RUID: [YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY==] -->

Going live

Before you go live with your API integration, you'll need to meet certain requirements. For more information, see Going Live.