---
title: "Update Listing Restrictions"
method: POST
path: "/listings/restrictions"
tags: ["Listing Calendar"]
---

# Update Listing Restrictions

`POST /listings/restrictions`

Update the restrictions of channel listings. <br><br>Please be aware that a successful response indicates only that we have initiated an asynchronous task to handle your submission; it <b>DOES NOT</b> ensure that the channel restrictions have been modified successfully. If you wish to view detailed results of the task execution, please visit the [Host Portal](https://hostex.io/app/price).

## Request body

- object
  - `channel_type` 'airbnb' | 'booking.com' | 'agoda' | 'expedia' | 'vrbo' | 'trip.com' | 'booking_site' | 'tujia_intl' | 'houfy', required — The type of the channel to be queried.
  - `listing_id` string, required — The unique identifier for different channels. <br>For example, the listing id for Airbnb is the Airbnb listing id, and the listing id for Booking.com is the Booking.com room id - rateplan id.
  - `restrictions` object[], required
    - `start_date` string, date, required — The start date from which restrictions update will apply.
    - `end_date` string, date, required — The end date until which restrictions update will apply, must be within 3 years from now.
    - `closed_on_arrival` boolean — Reservations for the check-in date on this date are not allowed. Available for `airbnb` `booking.com` `agoda` `expedia` `booking_site` `trip.com`.
    - `closed_on_departure` boolean — Reservations for the check-out date on this date are not allowed. Available for `airbnb` `booking.com` `agoda` `expedia` `booking_site` `trip.com`.
    - `min_stay_on_arrival` integer — Reservations including this date must not be shorter than the specified number of days. Available for `airbnb` `booking.com` `agoda` `expedia` `booking_site` `trip.com`.
    - `max_stay_on_arrival` integer — Reservations including this date must not be longer than the specified number of days. Available for `airbnb` `booking.com` `agoda` `expedia` `booking_site` `trip.com`.
    - `min_stay_through` integer — Reservations including this date must not be shorter than the specified number of days. Available for `booking.com` `agoda` `trip.com`.
    - `max_stay_through` integer — Reservations including this date must not be longer than the specified number of days. Available for `booking.com` `trip.com`.
    - `min_advance_reservation` string — The minimum number of days and/or hours that guests must book in advance (before the planned check-in or check-out date). The search date is counted as one of the days in the restriction length. This field requires the format like 'xDxH'. Examples: 4D = four days; 4D4H = four days and four hours. Available for `booking.com` `trip.com`.
    - `max_advance_reservation` string — The maximum number of days and/or hours that guests may book in advance (before the planned check-in or check-out date). The search date is counted as one of the days in the restriction length. This field requires the format like 'xDxH'. Examples: 4D = four days; 4D4H = four days and four hours. Available for `booking.com` `trip.com`.
    - `exact_stay_on_arrival` integer — Reservations with the check-in date on this date must be equal to the specified number of days. Available for `booking.com`.

## Response `200`

The request has been successfully submitted.

- CommonResponse
  - `request_id` string, required — Unique identifier for the request.
  - `error_code` integer, required — Numeric error code representing the status of the response. A value of `200` indicates success. <br> See the [Error Codes](/reference/error-manual#error-codes) section for more information.
  - `error_msg` string, required — Message detailing the status of the response.

---

[API](https://skmtc.net/hostex/apis/hostex-api.md) · [All operations](https://skmtc.net/hostex/apis/hostex-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hostex/hostex-api/revisions/a3fa555dee66/schema)