# Retrieve Property Settings Damage Programme

This endpoint allows partners to retrieve the terms and conditions of the Damage Payment Request Process (DPRP) associated with their property on the Booking.com platform.

***

### <mark style="color:yellow;">Endpoint</mark>

<mark style="color:green;background-color:green;">**`POST`**</mark>&#x20;

<div align="left"><figure><img src="https://958347541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9bn2UcBkeqtqixkl5eF%2Fuploads%2FpsybX0n39kUB8Z8WOk4X%2FSandbox%20image.png?alt=media&#x26;token=4ae73d0f-0d1a-4d73-a4e2-673dbc081d6a" alt="" width="56"><figcaption></figcaption></figure></div>

{% code overflow="wrap" %}
```url
https://connect-sandbox.su-api.com/SUAPI/jservice/bdc/property/settings/retrieveDamageProgramme
```
{% endcode %}

#### <mark style="color:yellow;">Header</mark>

```xml
-app-id: YOUR_APP_ID
Authorization: YOUR_API_KEY
Content-Type:application/json
```

<table><thead><tr><th width="185">Header</th><th width="85">Type</th><th width="101">Required</th><th>Description</th></tr></thead><tbody><tr><td><code>app-id</code></td><td>string</td><td>Yes</td><td>Your application ID. Required for authentication.</td></tr><tr><td><code>Authorization</code></td><td>string</td><td>Yes</td><td>Your API key for authorization. </td></tr><tr><td><code>Content-Type</code></td><td>string</td><td>Yes</td><td>Must be set to <code>application/json</code>.</td></tr></tbody></table>

***

<mark style="color:yellow;">**Attributes**</mark>

`language_code` <mark style="color:orange;">**string (Required)**</mark>

Specify the language code in which you want the terms to be returned in.

{% hint style="info" %}
Accepts the values listed under [BCL](broken-reference).
{% endhint %}

***

## <mark style="color:yellow;">**Sample Request**</mark>

```json
{
   "language_code": "en-us"
}
```

***

## <mark style="color:yellow;">Response</mark>

#### <mark style="color:green;">**Sample Success Response**</mark>

{% code overflow="wrap" %}
```json
{
  "Status": "Success",
  "Message": "Successfully fetch details",
  "Warnings": "",
  "Ruid": "e527c45a-f23a-4ee4-beb2-7d21f7699b1b",
  "data": "The following terms apply to the Damage Payment Request Process (as defined below) between the Accommodation (hereinafter the “Partner” or “You”) & Booking.com (hereinafter “Booking.com” or “Us”).\nBooking.com offers partners a Damage Payment Request Process (hereinafter the “DPRP”), through which Booking.com facilitates the collection of damage fee(s) incurred from damages caused to your property (hereinafter “Damage Fee(s)”), in line with the DPRP communicated to your guest(s) (hereinafter the “Guest(s)”). By implementing the DPRP on your behalf, Booking.com will not require the upfront collection of a deposit. Instead, in the event of alleged damage being caused to your property by a guest, you will be able to submit a damage payment request (the “Damage Payment Request”) to the guest via Booking.com (according to the conditions below), which might result in the Guest(s) reimbursing you if they accept that the damage was caused during their stay.\nPlease note: You can opt out of the DPRP at any moment. However, you agree and acknowledge that in such a situation, if your Property has been booked through our platform during the time you were part of the DPRP, then the booking will be subject to these Terms.\nBy opting in to the Damage Payment Request Process, you accept the following Terms:\nBooking.com will inform the Guest(s) that:\nthey must keep your property and its content(s), including all furniture, electronic equipment, fixtures, fittings, and effects (hereinafter the “Property”), in, on or at the Property in the same state of repair as at the start of the stay.\nthey are responsible for the safekeeping of the rental property and its contents, therefore they must remember, among others, to lock all doors and windows, and ensure that the Property is safe upon their departure.\nin the situation where any breakages, damage(s) or loss(es) occur in the Property, the Guests should report it to the Partner, and request them to make a Damage Payment Request under their reservation, as soon as reasonably practicable, but always up to 14 days after the Guests’ check-out.\nthey are responsible to reimburse Booking.com/the Partner for the damage(s), breakages or loss(es) caused to the Property and its contents (as defined above) by the Guest(s), according to the DPRP, limited to the amount You agreed when signing up to the DPRP, and in any case to a maximum limit of € 1,000. For the avoidance of doubt, the DPRP does not seek to undermine or replace the Partners’ property, liability or contents insurance it may have or prevent such insurance company's ability to pursue a claim for compensation for damage claims.\nExclusions to Damage Fees may include general cleaning, ordinary wear and tear, theft of cash and securities, and non-physical damages like smoking fines and breaking House Rules. Exclusions also include any type of bodily injury or proprietary damage to Guests' personal belongings or others, any kind of criminal activities, secondary/consequential loss, third-party liability as well as any damages that might be caused by an event of force majeure.\nIf you wish to make a Damage Payment Request for these types of incidents, you will need to handle such a request directly with your Guest(s), as these types of incidents are not included in the DPRP.\nYou agree that in order to submit a Damage Payment Request, you will need to connect to the reservation page on the extranet, and initiate the request via the right side menu “Make a Damage Payment Request” button, where you will be required to provide key details (such as which item has been damaged, what is the exact damage, what was the initial cost of the item, etc.)\nYou will also be required to provide evidence(s) of the damage/loss, as specified on the extranet platform. Please note that without providing any evidence of the damage caused to the Property and/or its contents, Booking.com will not be in a position to be able to communicate your Damage Payment Request to the Guest(s) for potential agreement.\nPlease note that you should not share any personal data or private information when formulating a Damage Payment Request through the platform, unless it is strictly necessary in order to support the Payment Request in question.\nIn the situation where the Guest(s) does not agree with and/or rejects your payment request, and/or does not confirm the alleged damage(s) to the Property and/or its content(s), you give Booking.com consent to review all communications between you and the Guest(s) via the Booking.com Platform. Booking.com has the full discretion not to facilitate the guest payment request. Booking.com's decision in relation to the DPRP is final and not subject to appeal, however, this will not preclude the Partner from pursuing legal remedies against the Guest outside of the DPRP.\nYou agree that Booking.com will only involve itself to support with the facilitation of the Damage Payment Request between You and the Guest(s), and will not in any way be responsible for the cost of the damages itself and/or for pursuing any claim against the guest outside of the DPRP.\nYou agree that You will be able to submit a payment request to Guest(s) for damage caused to the Property and/or its contents (as defined above) via Booking.com, up to 14 days after the end of their stay.\nIn any case, You agree that by opting into the DPRP, you will not be able to charge the Guest, even though you might already hold the Guest(s) payment details, and that Booking.com will be the only party allowed to charge the Guest(s) under the DPRP.\nYou understand that for the time being, Partners will not be required to pay the additional costs of Booking.com collecting the money from the Guest(s). However, Booking.com might reserve its right, in the future, to charge Partners for the costs of recuperating the Damage Fee(s) – in such case, Booking.com will provide beforehand, by way of notification, the details of such costs.\nIf You submit a fraudulent Damage Payment Request either by yourself or in collusion with the Guest(s), Booking.com reserves the right to:\nsuspend Partner participation in the DPRP;\nsuspend Partner payouts related with any ongoing and/or suspected fraudulent process;\nsuspend or terminate the Partner Agreement contract on the basis of a violation of our General Delivery Terms.\nThese Terms shall be exclusively governed by and construed in accordance with the laws of the Netherlands. Save as set out otherwise in these Terms, any disputes arising out of or in connection with these Terms shall exclusively be submitted to and dealt with by the competent court in Amsterdam, the Netherlands.\nWe may from time to time update and adjust these Terms, subject to prior communication (e.g. email or system notice) to You. Any updated or adjusted version shall replace and supersede the existing (current) version with such effect as set out in the notice of update/replacement."
}
```
{% endcode %}

#### <mark style="color:yellow;">Success Response Body Elements</mark>

`Status` <mark style="color:orange;">**string**</mark>&#x20;

Indicates the overall status of the request. In this case, "Success" means the operation was completed successfully.

`Message` <mark style="color:orange;">**string**</mark>&#x20;

Provides a brief message about the outcome. Here, it states "Successfully fetch details," confirming that the requested information was retrieved.

`data` <mark style="color:orange;">**string**</mark>&#x20;

Contains detailed terms regarding the Damage Payment Request Process (DPRP) between the accommodation (the Partner) and Booking.com. This text outlines the responsibilities, conditions, and processes involved in handling damage fees incurred during a guest's stay.

#### <mark style="color:red;">Errors</mark>

<mark style="color:red;">**Sample Error Response 1**</mark>

```json
{
   "Errors": [
       {
           "Code": "400",
           "ShortText": "HotelCode: Invalid HotelCode ('AWSTEST')"
       }
   ],
   "Status": "Fail"
}
```

<mark style="color:red;">**Sample Error Response 2**</mark>

```json
{
   "Errors": [
       {
           "Code": "573",
           "ShortText": "channel-mapping not found for this property!"
       }
   ],
   "Status": "Fail"
}
```

<mark style="color:red;">**Sample Error Response 3**</mark>

```json
{
   "Errors": [
       {
           "Code": "718",
           "ShortText": "language_code - is not valid or not found!"
       }
   ],
   "Status": "Fail"
}
```

<mark style="color:red;">**Sample Error Response 4**</mark>

```json
{
   "Status": "Fail",
   "Errors": [],
   "Message": "Invalid value: query param language_code - Language code is invalid.",
   "Ruid": "dbe6c93d-836c-437e-a604-c361ba8e654f",
   "Data": {}
}
```

***

<mark style="color:yellow;">**Error Response Body Elements**</mark>

`Status` <mark style="color:orange;">**string**</mark>

Indicates the result of the API call, which will be always `"Fail"` in case of an error response.

***

`Error` <mark style="color:orange;">**array**</mark>

Array that contains details about any errors that occurred during the API call. Each object in the `Errors` array contains the following properties:

`Code` <mark style="color:orange;">**string**</mark>

Specific error code that helps identify the type of error.

{% hint style="info" %}
For example: `"400"` indicates a bad request.
{% endhint %}

`ShortText` <mark style="color:orange;">**string**</mark>

A short description of the error.

***

`Message` <mark style="color:orange;">**string**</mark>

A message providing more information about the error.
