---
title: "Update calendar for multiple listings"
method: PUT
path: "/availability-pricing/api/calendar/listings"
tags: ["Calendar"]
---

# Update calendar for multiple listings

`PUT /availability-pricing/api/calendar/listings`

Use this endpoint to set availability and pricing for multiple listings across a range of dates.

IMPORTANT:
- It is strongly suggested updating a single unique listing ID in a single HTTP request, despite the fact the API does support receiving different listing IDs.
- Max allowed days to be updated - 730 (~2 years)
- Strongly suggested to not update the same listing ID in parallel.
- To decrease response time, send fewer date periods.

## Request body

- object[]
  - `listingId` string, required — The listing id to update
  - `startDate` string, date, required — First day affected by changes (format: YYYY-MM-DD)
  - `endDate` string, date, required — Last date affected by changes (format: YYYY-MM-DD)
  - `status` 'available' | 'unavailable' — New status, enum: available, unavailable.
  - `price` number — New price, in the listing's currency.
  - `isBasePrice` boolean — Whether to reset prices for the range to the listing's base price
  - `minNights` integer — New min nights value
  - `isBaseMinNights` boolean — Whether to reset min nights for the range to the listing's base min nights
  - `note` string — Note to add to those dates.
  - `cta` boolean — Set Closed To Arrival for the date range.
  - `ctd` boolean — Set Closed To Departure for the date range.

## Response `200`

Returns ok if the update successful

- string

## Other responses

- `404` — Listing Not Found
- `422` — Validation Error
- `500` — Unhandled exception. Something went wrong on server.

---

[API](https://skmtc.net/guesty/apis/guesty-open-api.md) · [All operations](https://skmtc.net/guesty/apis/guesty-open-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/guesty/guesty-open-api/versions/7c62644070f2/schema)
