The `OTA_HotelDescriptiveContentNotif` (HDCN) endpoint is now under deprecation
The `OTA_HotelDescriptiveContentNotif` (HDCN) endpoint was deprecated in December 2024. We will fully sunset this endpoint on December 31, 2026. For more information on the deprecation and sunsetting timeline, see [OTA_HotelDescriptiveContentNotif (HDCN) endpoint in Content API](/connectivity/docs/deprecation-policy/deprecation-and-sunsetting#ota_hoteldescriptivecontentnotif-hdcn-endpoint-in-content-api).

Implement the Property Details API to [specify property settings](/connectivity/docs/content-api-modules/property-details-api/implementing-property-api-settings#managing-property-settings) such as long stays, damage policy among others. To learn more, see our guide on [Making property onboarding easier](https://connectivity.booking.com/s/solution-article/content-api-modernisation-MCP2RH5PDI6VHN5HU3ECL2FER2TY?language=en_US).

# Enable long stay bookings

You can enable properties to consent to accept stays longer than 30 days and upto 90 days using the `OTA_HotelDescriptiveContentNotif` endpoint.
By default, a property is configured to accept bookings for stays up to 30 days.

To enable properties to host stays longer than 30 days and up to a maximum of 90 days, use the `LongStayInfo` element:

- Set the `AcceptLongStay` attribute to `1`.
- Set the maximum stay duration using the `MaxLengthOfStay` attribute. Allowed values are: 45, 60, 75, 90 days.


Before enabling long stays, make sure that properties [follow any applicable local laws and regulations.](https://partner.booking.com/en-gb/help/legal-security/policies-local-laws/local-laws-and-regulations)

→ For properties located in Japan, make sure that properties show the disclaimer text as listed in the standard phrase: [LongStayDisclaimerJapan.](/connectivity/docs/api-reference/standardphrase#longstaydisclaimerjapan)

### Request body parameters

The following table describes the elements you must add in the request body when creating or updating a property to enable long stays:

| Element | Attribute | Description | Type | Using Property Details API |
|  --- | --- | --- | --- | --- |
| **>** `OTA_HotelDescriptiveContentNotifRQ` |  | [Required] Root element. | object |  |
| **>>** `HotelDescriptiveContents` |  | [Required] Contains property details. | object |  |
| **>>>** `HotelDescriptiveContent` |  | [Required] Contains property details. | object |  |
| **>>>>** `TPA_Extensions` |  | [Optional] Contains additional details like standard phrases, pricing type, long stay support and so on. | object |  |
| **>>>>>** `LongStayInfo` |  | [Optional] Contains long stay booking support. | object |  |
|  | `AcceptLongStay` | [Required] Specify whether the property accepts bookings for stays longer than 30 nights. Accepts:  - 0: false (default)  - 1: true | boolean | Use Property Details API's [`property_settings.​long_stay.​enabled` parameter.](/connectivity/docs/openapispecs/property-details-api/property-details-api-specification/property-settings-api/createpropertysettings#property-settings-api/createpropertysettings/t=request&path=property_settings/long_stay/enabled()) |
|  | `MaxLengthOfStay` | Specify the maximum length of stay that a guest can book. Accepts: `45, 60, 75, 90`.  Defaults to 90. | integer | Use Property Details API's [`property_settings.​long_stay.​max_length_of_stay` parameter.](/connectivity/docs/openapispecs/property-details-api/property-details-api-specification/property-settings-api/createpropertysettings#property-settings-api/createpropertysettings/t=request&path=property_settings/long_stay/max_length_of_stay) |


### Request body example

The following is an excerpted request body example that consents to long stay bookings and receives stays upto 45 days long:


```xml
<HotelDescriptiveContent
  HotelCode="12345"
  HotelDescriptiveContentNotifType="Overlay"
  HotelName="Example Hotel"
  ID="101010"
  LanguageCode="en">
    ...
  <TPA_Extensions>
    <LongStayInfo
      AcceptLongStay="1"
      MaxLengthOfStay="45"
    />
  </TPA_Extensions>
    ...
</HotelDescriptiveContent>
```

### Response body example

The following is a successful response body example:


```xml
<?xml version="1.0" encoding="UTF-8"?>
<OTA_HotelDescriptiveContentNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_HotelDescriptiveContentNotifRS.xsd" TimeStamp="2022-10-11T16:27:00+00:00" Target="Test" Version="3.000">
<Success />
</OTA_HotelDescriptiveContentNotifRS>
<!-- RUID: [[XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX==]] -->
```

## Response body parameters

The following table describes the response elements:

| Element | Description | Type | Notes |
|  --- | --- | --- | --- |
| `OTA_HotelDescriptiveContentNotifRS` | Contains the response data. | object |  |
| **>**  `warnings` | Contains potential warnings. These can help you improve your requests. | array |  |
| **>**  `errors` | Contains potential errors. These can help you understand what went wrong with your request. | array |  |
| **>** `success` | Indicates the success of the request. | object |  |
| `ruid` | Specifies the unique ID of the request. | string | You can send this ID to Booking.com Connectivity support team if you run into an issue. This can help to understand what went wrong. |