# Get the historical snapshots of a calendar day for a listing.

`GET /listings/{listing_id}/calendar_day_history`

> Wheelhouse Revenue Management API. Web version: https://docs.usewheelhouse.com/rm/reference/rm-get-calendar-day-history · OpenAPI spec: https://docs.usewheelhouse.com/rm/openapi.yaml · Operation ID: `rmGetCalendarDayHistory` · Tag: Calendar

Returns a history of price postings and calendar state snapshots for a specific stay date.

- **`posted_prices`** — each entry records a price that Wheelhouse posted to the channel for this date, in chronological order.
- **`calendar_snapshots`** — historical snapshots of the calendar day's state (availability, price, booking, etc.) over time.

Requires a Pro tier listing. Returns `402` if the feature is not available. The maximum lookback window is 180 days.

## Request

`GET https://api.usewheelhouse.com/ss_api/v1/listings/{listing_id}/calendar_day_history`

Authentication: send your RM API key in the `X-Integration-Api-Key` header (see https://docs.usewheelhouse.com/rm/authentication.md). Read-only keys can call this endpoint.

### Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `listing_id` | string | yes | The channel's unique listing identifier, or the Wheelhouse listing ID when `channel` is `wheelhouse`. |

### Query parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `channel` | string | yes | Channel name the listing is on (the `channel` field of the [/listings](https://docs.usewheelhouse.com/rm/reference/rm-get-listings.md) response), or the literal `wheelhouse` to read `listing_id` as a Wheelhouse listing ID instead. See [Identifying Listings](https://docs.usewheelhouse.com/rm/concepts/listings.md). |
| `stay_date` | string (date) | yes | The stay date to retrieve history for (YYYY-MM-DD). |

### Example request

```bash
curl -X GET 'https://api.usewheelhouse.com/ss_api/v1/listings/{listing_id}/calendar_day_history?channel=<channel>&stay_date=<stay_date>' \
  -H 'X-Integration-Api-Key: <your RM API key>'
```

Only required parameters and body fields are filled in, with placeholder values. Add the optional ones you need from the lists above; some are required in combination, as their descriptions say.

## Responses

### 200

Historical price postings and calendar snapshots for the requested stay date.

Body (`application/json`): object

- `stay_date` (string (date)): The stay date the history is for.
- `posted_prices` (array of object): Chronological list of prices posted to the channel for this stay date.
  - `posted_at` (string (date-time)): When the price was posted.
  - `posted_price` (integer): The price posted at that time in the listing currency.
- `calendar_snapshots` (array of object): Historical snapshots of the calendar day's state over time.
  - `price` (integer, nullable): The observed price for this date, or `null` if none is recorded.
  - `currency` (string, nullable): ISO 4217 currency code for the price, or `null` if none is recorded.
  - `is_available` (boolean): Whether the date is available for booking. State matrix: `is_available=true, is_booked=false` = available; `is_available=false, is_booked=true` = booked (confirmed reservation); `is_available=false, is_booked=false` = blocked (owner hold or similar).
  - `is_booked` (boolean): Whether the date has a confirmed booking. See `is_available` for the full state matrix.
  - `block_time` (string (date), nullable): The date and time (ISO-8601) when this night first became unavailable. Null for available nights.

    This field applies to both owner-blocked and guest-booked nights using the same column:
    - **Booked nights** (`is_booked=true`): the date the reservation was first detected as pending or accepted by Wheelhouse.
    - **Blocked nights** (`is_booked=false, is_available=false`): approximately the date the calendar sync recorded the block.

    The value is not the check-in date or booking date in the channel sense — it reflects when Wheelhouse's calendar ingestion first observed the night as unavailable.
  - `reservation_id` (string, nullable): The reservation ID associated with this date, if booked. This is the channel reservation ID (a string), or `null` when the night is not booked.
  - `unit_number` (integer): The unit number, 0 if the listing is single-unit.
  - `created_at` (string (date-time)): When this snapshot was recorded.

Example shape (generated from the schema; placeholder values, not a real response):

```json
{
  "stay_date": "2026-01-01",
  "posted_prices": [
    {
      "posted_at": "2026-01-01T00:00:00Z",
      "posted_price": 0
    }
  ],
  "calendar_snapshots": [
    {
      "price": 0,
      "currency": "string",
      "is_available": true,
      "is_booked": true,
      "block_time": "2026-01-01",
      "reservation_id": "string",
      "unit_number": 0,
      "created_at": "2026-01-01T00:00:00Z"
    }
  ]
}
```

### 400

`stay_date` is missing or beyond the historical lookback limit.

### 401

API key authorization failed.

### 402

The listing does not have access to historical calendar data. Upgrade the plan to unlock this feature.

### 403

Listing authorization failed.

### 404

Listing not found.

### 406

The listing is inactive. See the **Inactive Listings** section in the overview.

Body (`application/json`): object

- `error` (string, example: `Listing '12345' is inactive`)

Example shape (generated from the schema; placeholder values, not a real response):

```json
{
  "error": "Listing '12345' is inactive"
}
```

### 429

Rate limit exceeded — the API key has sent too many requests. Wait before retrying. See the **Rate Limits** section in the overview for the recommended exponential backoff strategy.

Body (`application/json`): object

- `error` (string, example: `API token is at rate limit`)

Example shape (generated from the schema; placeholder values, not a real response):

```json
{
  "error": "API token is at rate limit"
}
```
