# Step 14 - Add Availability

Use the `/hotels/xml/availability` endpoint to create availability based on the inventory pricing you set in the previous step. Adding availability makes your rooms available for booking on Booking.com.

## Prerequisites

You must have completed the following steps:

- Step 2 and have the property ID
- Step 3 and have the unit ID
- Step 6 and have a rate plan ID
- Step 7 and set the property's pricing type to `LOS` (Length of stay)
- Step 12 and have mapped a unit to a rate plan to create an LOS roomrate
- Step 13 and have created pricing


## Adding availability


```http
POST
https://supply-xml.booking.com/hotels/xml/availability
```

### Header parameter

| Header | Description | Type | Required/Optional | Notes |
|  --- | --- | --- | --- | --- |
| `Accept-Version` | Specify the version number to get the API functionality specific to that version. | string | optional | Currently supports the version 1.1 (default).  Version 1.0 is sunset. If used, the endpoint returns a 400 Not acceptable error. |


### Request body parameters

The following table describes the elements you can add in the request body:

All parameters are required unless otherwise noted.

| Element | Attribute | Description |
|  --- | --- | --- |
| `request` |  | Root element. |
| **>** `room` |  | Contains details about the room. |
|  | `id` | The Booking.com unit ID specified as an integer. |
| **>>** `date` |  | Specifies the date(s) (`value`), date range (`from` `to`), or mix of both to which the availability applies. Uses datetime format. Follows the format: `YYYY-MM-DD`. We recommend specifying at least 12 months of availability. |
|  | `from` | Specifies the starting date of a date range. Follows the format: `YYYY-MM-DD`. Date must be before the date you specify in `to`. Please note, you can update for periods in the future and up to two day in the past, in the Central European Time (CET) timezone. |
|  | `to` | Specifies the ending date of a date range, excluding the end date. Follows the format: `YYYY-MM-DD`. You can specify up to 10 years of availability from the date you make the call.  **NOTE:** You should interpret `date[to]` as "up to and *not including*". In other words, a request with `<date from="2025-08-27" to="2029-09-02" />` applies to all days from 27 August 2025 up to 1 September 2029. |
| **>>>** `currencycode` |  | [Optional] Specifies the property's local [currency code.](/connectivity/docs/b_xml-countrycurrencies) We recommend providing the currency code. When provided, it must match the property's currency code. |
| **>>>** `roomstosell` |  | Specifies the number of rooms of this type that Booking.com can sell. The number of available rooms applies across all rates including prices set using other rates for the same room type. Maximum value: `254`  **NOTE:** Setting a value greater than `255` implies that there are unlimited rooms available. Use other restrictions (such as `closed`) to prevent overbookings. |
| **>>>** `closed` |  | Specifies whether all rooms of a room type are closed (not bookable) or only the specified room type and rate combination on the specified date depending on whether the rate ID is provided. Accepts: `1` (closed), `0` (open).  **NOTE:** See also [Availability restrictions](/connectivity/docs/understanding-pricing-types#availability-restrictions). Closing a room does not clear the value of `roomstosell`, `price`, or other fields. The values are preserved.  Once you close a room, make sure to open it before setting availability for it. |


### Request body example

The following is a request body example:


```xml
<request>
  <room id="1479536101">
    <date from='2025-10-21' to='2025-10-24'>
      <roomstosell>5</roomstosell>
      <currencycode>JPY</currencycode>
      <closed>0</closed>
    </date>
  </room>
</request>
```

### Response body example

The following is a successful response body example:


```xml
<?xml version='1.0' encoding='UTF-8'?>
<ok/>
<!-- RUID: [XXXXXXX-XXXXX-XXXXXXXXXXX-XXXXXXXXXXXX] -->
```