# Update preferences for a batch of listings.

`PUT /preferences`

> Wheelhouse Revenue Management API. Web version: https://docs.usewheelhouse.com/rm/reference/rm-put-preferences-batch · OpenAPI spec: https://docs.usewheelhouse.com/rm/openapi.yaml · Operation ID: `rmPutPreferencesBatch` · Tag: Listing Preferences

Updates pricing preferences for multiple listings in one request.

Returns status `207` if some updates failed, `424` if all updates failed.

This is a bulk update, which a user with *restricted editor* access to a shared
listing may not make: such a listing is reported in `errors` with status `403`,
however many listings the request names. Use
[PUT /preferences/{listing_id}](https://docs.usewheelhouse.com/rm/reference/rm-put-preferences.md) for it instead.

All fields are optional; only provided fields will be updated. This partial-update
behavior applies at the top level only — omitting a field (e.g. `minimum_stay_rules_v3`)
leaves it unchanged, but providing a field that holds an array of rules
(e.g. `minimum_price_rules_v3`) will **completely replace** the existing rule set
for that field; individual rules within an array cannot be merged or patched.
Always fetch the current preferences before writing and include every rule you
wish to retain — any rules omitted from an array will be permanently deleted.

## Request

`PUT https://api.usewheelhouse.com/ss_api/v1/preferences`

Authentication: send your RM API key in the `X-Integration-Api-Key` header (see https://docs.usewheelhouse.com/rm/authentication.md). Modifies data; read-only keys get `403 Forbidden`.

### Query parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `channel` | string | yes | Channel name the listings are 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_ids` as Wheelhouse listing IDs instead. See [Identifying Listings](https://docs.usewheelhouse.com/rm/concepts/listings.md). |

### Request body (`application/json`, required)

- `listing_preferences` (array of object, required)
  - Each item: The pricing preferences to set for a listing. All fields are optional; only provided fields will be updated. This partial-update behavior applies at the top level only — omitting a field (e.g. `minimum_stay_rules_v3`) leaves it unchanged, but providing a field that holds an array of rules (e.g. `minimum_price_rules_v3`) will **completely replace** the existing rule set for that field; individual rules within an array cannot be merged or patched.
  - `listing_id` (string, required): The channel's listing ID to update.
  - `automatic_rate_posting_enabled` (boolean): Whether Wheelhouse automatically posts its price recommendations to the channel calendar. When `false`, recommendations are computed but not pushed to the channel. This setting does not affect custom rates set via the API — those are posted independently.
  - `base_price` (integer, nullable, min: 1): The manually set base price. If set, overrides Wheelhouse's data-driven recommendation. Must be a whole number of at least 1.
  - `base_price_adjustment` (number, nullable): A multiplier on the Wheelhouse recommended base price, for example `0.9` for 10% below it. Only used if `base_price` is not set. Sending a non-null value without `base_price` clears a manual `base_price`. Sending `null` leaves a manual `base_price` in place. To clear it, send `null` for `base_price`. Cannot be `0`.
  - `monthly_discount` (integer, nullable, default: `0`): Monthly discount percentage as an integer in the range 0–100 (e.g. `5` = 5%). On listings that accept length-of-stay premiums (every listing whose `supported_settings.long_term_discount_type` is `complex`, and some with `rules`), values are signed instead, so `-10` is a 10% discount and `10` a 10% premium. Applied to bookings ≥ 28 nights. Kept in sync with the global rule in `long_term_discounts.rules['28']` — setting one automatically updates the other. When both are sent in the same PUT, `long_term_discounts` takes precedence.
  - `weekly_discount` (integer, nullable, default: `0`): Weekly discount percentage as an integer in the range 0–100 (e.g. `5` = 5%). On listings that accept length-of-stay premiums (every listing whose `supported_settings.long_term_discount_type` is `complex`, and some with `rules`), values are signed instead, so `-10` is a 10% discount and `10` a 10% premium. Applied to bookings ≥ 7 nights. Kept in sync with the global rule in `long_term_discounts.rules['7']` — setting one automatically updates the other. When both are sent in the same PUT, `long_term_discounts` takes precedence.
  - `nickname` (string, nullable): Listing nickname. Overrides the listing's default nickname.
  - `last_minute_discount` (object, nullable): UI: 'Last minute' — Last-minute discount configuration.
    - `type` (string, one of: `CON`, `REC`, `AGG`, `CUS`)
    - `rules` (array of object `calendar_rule_time_based` | object `calendar_rule_seasonal` | object `calendar_rule_event` | object `calendar_rule_monthly_simple` | object `calendar_rule_day_of_week` | object `calendar_rule_custom`): Calendar rules when `type` is `CUS`. Valid rule types: `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
      - One of:
        - **calendar_rule_time_based**: see `calendar_rule_time_based` under Schemas.
        - **calendar_rule_seasonal**: see `calendar_rule_seasonal` under Schemas.
        - **calendar_rule_event**: see `calendar_rule_event` under Schemas.
        - **calendar_rule_monthly_simple**: see `calendar_rule_monthly_simple` under Schemas.
        - **calendar_rule_day_of_week**: see `calendar_rule_day_of_week` under Schemas.
        - **calendar_rule_custom**: see `calendar_rule_custom` under Schemas.
    - `smooth` (boolean, default: `false`): UI: 'Smooth' — Only used when `type` is `CUS`. When `true`, the adjustment eases gradually from one rule to the next instead of jumping at each rule's edge. `custom` rules still apply exactly. Defaults to `false` (stepped).
  - `far_future_premium` (object, nullable): UI: 'Far future' — Far-future premium configuration.
    - `type` (string, one of: `CON`, `REC`, `AGG`, `CUS`)
    - `rules` (array of object `calendar_rule_time_based` | object `calendar_rule_seasonal` | object `calendar_rule_event` | object `calendar_rule_monthly_simple` | object `calendar_rule_day_of_week` | object `calendar_rule_custom`): Calendar rules when `type` is `CUS`. Valid rule types: `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
      - One of:
        - **calendar_rule_time_based**: see `calendar_rule_time_based` under Schemas.
        - **calendar_rule_seasonal**: see `calendar_rule_seasonal` under Schemas.
        - **calendar_rule_event**: see `calendar_rule_event` under Schemas.
        - **calendar_rule_monthly_simple**: see `calendar_rule_monthly_simple` under Schemas.
        - **calendar_rule_day_of_week**: see `calendar_rule_day_of_week` under Schemas.
        - **calendar_rule_custom**: see `calendar_rule_custom` under Schemas.
    - `smooth` (boolean, default: `false`): UI: 'Smooth' — Only used when `type` is `CUS`. When `true`, the adjustment eases gradually from one rule to the next instead of jumping at each rule's edge. `custom` rules still apply exactly. Defaults to `false` (stepped).
  - `seasonality_adjustment` (object, nullable): UI: 'Seasonality' — Seasonality adjustment configuration.
    - `type` (string, one of: `CON`, `REC`, `AGG`, `CUS`)
    - `rules` (array of object `calendar_rule_seasonal` | object `calendar_rule_event` | object `calendar_rule_monthly`): Calendar rules when `type` is `CUS`. Valid rule types: `seasonal`, `event`, `monthly`.
      - One of:
        - **calendar_rule_seasonal**: see `calendar_rule_seasonal` under Schemas.
        - **calendar_rule_event**: see `calendar_rule_event` under Schemas.
        - **calendar_rule_monthly**: see `calendar_rule_monthly` under Schemas.
    - `smooth` (boolean, default: `false`): UI: 'Smooth' — Only used when `type` is `CUS`. When `true`, the adjustment eases gradually from one rule to the next instead of jumping at each rule's edge, and monthly rules' `step`, `start_value` and `end_value` are ignored. Defaults to `false` (stepped).
  - `day_of_week` (object, nullable): Day-of-week pricing factor configuration.

    - `REC` applies the market's day-of-week pattern.
    - `CON` and `AGG` adjust that pattern conservatively or aggressively. Sent without `rules`, they
      store the matching preset `day_of_week` rule.
    - `ADJ` applies the market's pattern and multiplies your own `rules` on top of it.
    - `CUS` replaces the market's pattern with your own `rules`, whose values are price multipliers
      (`1.1` is 10% higher). `CUS` without `rules` prices every day the same.
    - `type` (string, one of: `CON`, `REC`, `AGG`, `ADJ`, `CUS`)
    - `rules` (array of object `calendar_rule_global` | object `calendar_rule_time_based` | object `calendar_rule_seasonal` | object `calendar_rule_event` | object `calendar_rule_monthly_simple` | object `calendar_rule_day_of_week` | object `calendar_rule_custom`): Calendar rules when `type` is `ADJ` or `CUS`. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
      - One of:
        - **calendar_rule_global**: see `calendar_rule_global` under Schemas.
        - **calendar_rule_time_based**: see `calendar_rule_time_based` under Schemas.
        - **calendar_rule_seasonal**: see `calendar_rule_seasonal` under Schemas.
        - **calendar_rule_event**: see `calendar_rule_event` under Schemas.
        - **calendar_rule_monthly_simple**: see `calendar_rule_monthly_simple` under Schemas.
        - **calendar_rule_day_of_week**: see `calendar_rule_day_of_week` under Schemas.
        - **calendar_rule_custom**: see `calendar_rule_custom` under Schemas.
  - `gap_night` (object `gap_night`, nullable): Gap night pricing strategy (UI: 'Gaps & Adjacencies' in the Pricing Engine panel). Controls the price multiplier for
    gap nights between bookings. When `type` is `CUS`, provide `custom` rules; the server rejects `CUS` without `custom`.
    This is a **pricing-only** setting. It is unrelated to the `gap` and `adjacency`/`one_sided_gap` rule types in
    `minimum_stay_rules_v3`, which control minimum stay behavior for gap nights. In a request the `custom` array
    replaces the stored one.

    Gap night pricing does not apply to listings with more than one unit. The setting is still accepted, and
    the response carries a `not_supported_for_multi_unit` warning.
    - Fields: see `gap_night` under Schemas.
  - `minimum_stay_rules_v3` (array of object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`, default: `[]`): UI: 'Minimum stays' — minimum stay rules. The `_v3` suffix is a stable historical identifier; this field name is not expected to change.
    - Fields: see `integer_calendar_rule` under Schemas.
  - `min_stays_enabled` (boolean): Whether minimum stay rules are enabled.
  - `minimum_price_rules_v3` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`, default: `[]`): UI: 'Minimum prices' — Minimum price rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`. The `_v3` suffix is a stable historical identifier; this field name is not expected to change.
    - One of:
      - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
      - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
      - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
      - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
      - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
      - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
      - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
  - `maximum_price_rules_v3` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`, default: `[]`): UI: 'Maximum prices' — Maximum price rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`. The `_v3` suffix is a stable historical identifier; this field name is not expected to change.
    - One of:
      - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
      - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
      - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
      - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
      - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
      - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
      - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
  - `checkin_checkout` (object, nullable): Which days guests may check in and check out. Rule values are allow flags: `1` allows the day and
    `0` blocks it. A `day_of_week` rule's `day_of_week_values` has 7 entries, index 0 = Sunday. Where rules
    overlap, the more specific rule type wins (for example a date-specific `custom` rule over a
    `day_of_week` rule); between rules of the same type, the later one in the array wins.

    In a request the object replaces the stored one as a whole: send `active` and both
    `check_in_rules` and `check_out_rules` (a request missing either array is rejected with 400). An
    empty `check_out_rules` leaves check-out unrestricted.

    Example, check-in on Friday and Saturday only, check-out any day:

    ```json
    {
      "active": true,
      "auto_adjust": false,
      "check_in_rules": [{"type": "day_of_week", "day_of_week_values": [0, 0, 0, 0, 0, 1, 1]}],
      "check_out_rules": [{"type": "day_of_week", "day_of_week_values": [1, 1, 1, 1, 1, 1, 1]}]
    }
    ```
    - `active` (boolean): Whether the check-in/check-out rules are enforced. Stored as `false` when omitted.
    - `auto_adjust` (boolean): When `true`, Wheelhouse opens additional check-in and check-out days around unavailable nights so that open stretches between bookings can still be booked, even on days the rules would otherwise block.
    - `check_in_rules` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`): Allowed check-in rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
      - One of:
        - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
        - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
        - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
        - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
        - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
        - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
        - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
    - `check_out_rules` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`): Allowed check-out rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
      - One of:
        - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
        - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
        - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
        - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
        - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
        - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
        - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
  - `long_term_discounts` (object, default: `{"active":false,"weekly_rules":[],"monthly_rules":[],"rules":{}}`): Rule-based long-term discount configuration.
    - `active` (boolean)
    - `weekly_rules` (array of object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`, **deprecated**): Weekly discount rules (integer calendar rules).
      - Fields: see `integer_calendar_rule` under Schemas.
    - `monthly_rules` (array of object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`, **deprecated**): Monthly discount rules (integer calendar rules).
      - Fields: see `integer_calendar_rule` under Schemas.
    - `rules` (map of string to array of object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`): LOS-keyed rules (integer calendar rules). Keys are length-of-stay thresholds (e.g. "7", "28"); values are arrays of integer calendar rules holding whole percentages (`10` is a 10% discount). On listings that accept length-of-stay premiums (every listing whose `supported_settings.long_term_discount_type` is `complex`, and some with `rules`), values are signed instead, so `-10` is a 10% discount and `10` a 10% premium.
      - Fields: see `integer_calendar_rule` under Schemas.
  - `occupancy_pacing` (object `occupancy_pacing`, nullable, default: `{}`): Occupancy pacing configuration. When `occupancy_pacing` is sent as a non-empty object, both `adjusted` and `pacing` are required.

    Occupancy pacing matrix configuration. `{}` means pacing is off, which is the default for a new listing.
    When `occupancy_pacing` is sent as a non-empty object, `adjusted` and `pacing` are required, and `pacing`
    must include a matrix with `type` `global` (otherwise the request is rejected with 400). In a request the
    object replaces the stored one as a whole; omit it to leave pacing unchanged.

    For each lead-time column, occupancy is measured across that whole window and the matching row's
    percentage is applied to every date in it. A row covers occupancy above `min` up to and including
    `max` (`min` `0` includes 0%); the first matching row wins, and dates outside every column or row are
    unchanged. The adjusted price still respects the listing's minimum and maximum price rules.
    - Fields: see `occupancy_pacing` under Schemas.
  - `fee_adjustments` (object `fee_adjustments`, nullable): Estimated fee share applied on top of the nightly rate. `null` when nothing is configured, otherwise both keys are present; in a request the object replaces the stored one as a whole, and `null` clears it.

    UI: 'Asking Rate (+Est. Fees)' — The estimated share of fees guests pay on top of the nightly rate, as a
    percentage of that rate. It is what `GET /listings/{listing_id}/fee_impact_calendar` returns as a per-date
    multiplier. A response carries `null` when nothing is configured, otherwise both keys. In a request the
    object replaces the stored one as a whole, so send both keys; `null` clears the setting.
    - Fields: see `fee_adjustments` under Schemas.
  - `demand_sensitivity_rules` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`, default: `[]`): Local events rules. Shown as Demand sensitivity before day of week became its own setting; the field name is unchanged. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
    - One of:
      - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
      - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
      - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
      - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
      - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
      - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
      - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
  - `historical_anchoring_price_source` (string, one of: `observed`, `posted`, `posted_with_fallback`): Which historical price historical anchoring weighs in. `observed`, the default, is the listing's price as Wheelhouse saw it on the channel once the date booked. `posted` is the price Wheelhouse last posted for the date before it booked, so dates Wheelhouse never posted a price for are not anchored. `posted_with_fallback` uses the posted price where there is one and the observed price otherwise.
  - `historical_anchoring_mode` (string, one of: `blended`, `anchor_only`): How a historical anchoring percentage turns the historical price into a floor for the recommendation. `blended` averages the historical price with the recommendation, using the percentage as the weight on the historical price: at 50%, a $1,200 historical price and a $400 recommendation give $800. `anchor_only` takes the percentage of the historical price alone, so at 50% the floor is $600: a $400 recommendation rises to $600 and a $700 one stays at $700. Either only ever raises a price, and from 100% up both give the same price.
  - `historical_anchoring_rules` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`, default: `[]`): Historical anchoring rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
    - One of:
      - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
      - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
      - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
      - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
      - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
      - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
      - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
  - `custom_date_ranges` (array of object `custom_date_range`, default: `[]`): Represents an Event or Season entry used by the Wheelhouse Events & Seasons feature.
    Calendar rules reference these entries by `id` to apply settings (e.g. min stay, pricing)
    over named date windows.

    Each listing stores its own copy of every Event or Season it belongs to. Entries for the
    same event or season share the same `id` across listings — this shared `id` is what enables
    bulk adjustments in the Wheelhouse UI. If you write a `custom_date_ranges` entry with a new
    or changed `id`, that listing's entry is no longer linked to the others and will not be
    included in future bulk edits of the original Event or Season.

    To safely modify an event or season's definition (dates or name) on one listing without
    affecting others, omit the `id` field — the server assigns a new independent ID scoped to
    that listing. To update only a rule value (e.g. raise the minimum price) without changing
    dates, include the existing `id` unchanged.

    A new `custom_date_ranges` entry and a rule referencing it can be submitted in the same
    PUT request. Manually assign an `id` on the new entry so that the referencing rule can
    use it in the same payload. Alternatively, use two sequential PUTs: the first PUT
    creates the entry without an `id` (the server assigns one, returned in the response);
    the second PUT adds the rule referencing that server-assigned `id`.
    - Fields: see `custom_date_range` under Schemas.
  - `min_min_price` (integer, default: `0`): UI: 'Absolute minimum price' — Hard lower bound that overrides all pricing rules. No recommended price will fall below this value regardless of any rule configuration. Distinct from a `global` rule in `minimum_price_rules_v3`, which can be overridden by higher-priority rules. Must be an integer (whole currency units).
  - `min_min_stay` (integer, default: `0`): UI: 'Absolute minimum stay' — Hard lower bound that overrides all minimum stay rules. No minimum stay will be set below this value regardless of any rule configuration. Distinct from both a `global` rule in `minimum_stay_rules_v3` (which can be overridden by higher-priority rules) and from `global_min_stay` in the price recommendations response (which reflects the current effective default rule value, not a hard floor).
  - `apply_gap_night_rules_to_overrides` (boolean): UI: 'Apply Gap Night Rules to Overrides' — When `true`, gap-night minimum stay rules take priority over custom (date override) rules. When `false` (default), custom rules win over gap-night rules.

### Example request

```bash
curl -X PUT 'https://api.usewheelhouse.com/ss_api/v1/preferences?channel=<channel>' \
  -H 'X-Integration-Api-Key: <your RM API key>' \
  -H 'Content-Type: application/json' \
  -d '{
  "listing_preferences": [
    {
      "listing_id": "string"
    }
  ]
}'
```

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

All updates succeeded.

Body (`application/json`): object

- `updated_preferences` (array of object `listing_preference_response`)
  - Fields: see `listing_preference_response` under Schemas.

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

```json
{
  "updated_preferences": [
    {
      "listing_id": 0,
      "partner_listing_id": "string",
      "currency": "string",
      "automatic_rate_posting_enabled": true,
      "base_price": 0,
      "base_price_adjustment": 0,
      "monthly_discount": 0,
      "weekly_discount": 0,
      "nickname": "string",
      "last_minute_discount": {
        "type": "CON",
        "rules": [
          {
            "type": "time_based",
            "days_after": 0,
            "days_before": 0,
            "months": [
              1
            ],
            "priority": 0,
            "day_of_week_values": [
              0,
              0,
              0,
              0,
              0,
              0,
              0
            ],
            "value": 0
          }
        ],
        "smooth": false
      },
      "far_future_premium": {
        "type": "CON",
        "rules": [
          {
            "type": "time_based",
            "days_after": 0,
            "days_before": 0,
            "months": [
              1
            ],
            "priority": 0,
            "day_of_week_values": [
              0,
              0,
              0,
              0,
              0,
              0,
              0
            ],
            "value": 0
          }
        ],
        "smooth": false
      },
      "seasonality_adjustment": {
        "type": "CON",
        "rules": [
          {
            "type": "seasonal",
            "id": 0,
            "priority": 0,
            "day_of_week_values": [
              0,
              0,
              0,
              0,
              0,
              0,
              0
            ],
            "value": 0
          }
        ],
        "smooth": false
      },
      "day_of_week": {
        "type": "CON",
        "rules": [
          {
            "type": "global",
            "priority": 0,
            "value": 0
          }
        ]
      },
      "gap_night": {
        "custom": [
          {
            "adjacent": "left",
            "adjustment": 0,
            "day_of_week": [
              0
            ],
            "gap": 0
          }
        ],
        "type": "CON"
      },
      "minimum_stay_rules_v3": [],
      "min_stays_enabled": true,
      "minimum_price_rules_v3": [],
      "maximum_price_rules_v3": [],
      "checkin_checkout": {
        "active": true,
        "auto_adjust": true,
        "check_in_rules": [
          {
            "type": "global",
            "priority": 0,
            "value": 0
          }
        ],
        "check_out_rules": [
          {
            "type": "global",
            "priority": 0,
            "value": 0
          }
        ]
      },
      "long_term_discounts": {
        "active": false,
        "weekly_rules": [],
        "monthly_rules": [],
        "rules": {}
      },
      "occupancy_pacing": {},
      "fee_adjustments": {
        "total_fee_percentage": 0,
        "auto_update": true
      },
      "demand_sensitivity_rules": [],
      "historical_anchoring_price_source": "observed",
      "historical_anchoring_mode": "blended",
      "historical_anchoring_rules": [],
      "custom_date_ranges": [],
      "min_min_price": 0,
      "min_min_stay": 0,
      "apply_gap_night_rules_to_overrides": true,
      "update_from": "string",
      "update_from_id": 0,
      "created_at": "string",
      "updated_at": "string",
      "supported_settings": {
        "checkin_checkout": true,
        "min_stays": true,
        "long_term_discounts": true,
        "long_term_discount_type": "disabled"
      },
      "warnings": [
        {
          "setting": "checkin_checkout",
          "reason": "not_supported_by_channel",
          "message": "string",
          "attributes": [
            "string"
          ]
        }
      ]
    }
  ]
}
```

### 207

Some updates succeeded and some failed.

Body (`application/json`): object

- `updated_preferences` (array of object `listing_preference_response`)
  - Fields: see `listing_preference_response` under Schemas.
- `errors` (array of array of string | integer, each item min items: 3, max items: 3): List of per-listing errors.
  - Fields: see `preference_error` under Schemas.

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

```json
{
  "updated_preferences": [
    {
      "listing_id": 0,
      "partner_listing_id": "string",
      "currency": "string",
      "automatic_rate_posting_enabled": true,
      "base_price": 0,
      "base_price_adjustment": 0,
      "monthly_discount": 0,
      "weekly_discount": 0,
      "nickname": "string",
      "last_minute_discount": {
        "type": "CON",
        "rules": [
          {
            "type": "time_based",
            "days_after": 0,
            "days_before": 0,
            "months": [
              1
            ],
            "priority": 0,
            "day_of_week_values": [
              0,
              0,
              0,
              0,
              0,
              0,
              0
            ],
            "value": 0
          }
        ],
        "smooth": false
      },
      "far_future_premium": {
        "type": "CON",
        "rules": [
          {
            "type": "time_based",
            "days_after": 0,
            "days_before": 0,
            "months": [
              1
            ],
            "priority": 0,
            "day_of_week_values": [
              0,
              0,
              0,
              0,
              0,
              0,
              0
            ],
            "value": 0
          }
        ],
        "smooth": false
      },
      "seasonality_adjustment": {
        "type": "CON",
        "rules": [
          {
            "type": "seasonal",
            "id": 0,
            "priority": 0,
            "day_of_week_values": [
              0,
              0,
              0,
              0,
              0,
              0,
              0
            ],
            "value": 0
          }
        ],
        "smooth": false
      },
      "day_of_week": {
        "type": "CON",
        "rules": [
          {
            "type": "global",
            "priority": 0,
            "value": 0
          }
        ]
      },
      "gap_night": {
        "custom": [
          {
            "adjacent": "left",
            "adjustment": 0,
            "day_of_week": [
              0
            ],
            "gap": 0
          }
        ],
        "type": "CON"
      },
      "minimum_stay_rules_v3": [],
      "min_stays_enabled": true,
      "minimum_price_rules_v3": [],
      "maximum_price_rules_v3": [],
      "checkin_checkout": {
        "active": true,
        "auto_adjust": true,
        "check_in_rules": [
          {
            "type": "global",
            "priority": 0,
            "value": 0
          }
        ],
        "check_out_rules": [
          {
            "type": "global",
            "priority": 0,
            "value": 0
          }
        ]
      },
      "long_term_discounts": {
        "active": false,
        "weekly_rules": [],
        "monthly_rules": [],
        "rules": {}
      },
      "occupancy_pacing": {},
      "fee_adjustments": {
        "total_fee_percentage": 0,
        "auto_update": true
      },
      "demand_sensitivity_rules": [],
      "historical_anchoring_price_source": "observed",
      "historical_anchoring_mode": "blended",
      "historical_anchoring_rules": [],
      "custom_date_ranges": [],
      "min_min_price": 0,
      "min_min_stay": 0,
      "apply_gap_night_rules_to_overrides": true,
      "update_from": "string",
      "update_from_id": 0,
      "created_at": "string",
      "updated_at": "string",
      "supported_settings": {
        "checkin_checkout": true,
        "min_stays": true,
        "long_term_discounts": true,
        "long_term_discount_type": "disabled"
      },
      "warnings": [
        {
          "setting": "checkin_checkout",
          "reason": "not_supported_by_channel",
          "message": "string",
          "attributes": [
            "string"
          ]
        }
      ]
    }
  ],
  "errors": [
    [
      "1234567890",
      "Listing not found",
      404
    ]
  ]
}
```

### 401

API key authorization failed.

### 403

The API key is read-only and may not be used with PUT.

### 424

All updates failed.

Body: same as `207` above.

### 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"
}
```

## Schemas

Shared by more than one field above.

### `calendar_rule_time_based`

Type: object `calendar_rule_time_based`

**time_based** — Relative to "today" for the listing. At least one of `days_before` or `days_after` must be set.
Provide `value` or `day_of_week_values`, not both. Optional `months` scopes by calendar month.

When only `days_before` is set, the rule applies to dates within that many days of today (last-minute window).
When only `days_after` is set, the rule applies to dates at least that many days away (far-future window).
When both are set, the rule applies to dates that satisfy both conditions simultaneously — at least
`days_after` days away AND within `days_before` days — creating a mid-booking-window band.
`days_before` must be greater than or equal to `days_after` when both are provided.

**time_based** — Relative to “today” for the listing. At least one of `days_before` or `days_after` must be set.
Provide `value` or `day_of_week_values`, not both. Optional `months` scopes by calendar month.

When only `days_before` is set, the rule applies to dates within that many days of today (last-minute window).
When only `days_after` is set, the rule applies to dates at least that many days away (far-future window).
When both are set, the rule applies to dates that satisfy both conditions simultaneously — at least
`days_after` days away AND within `days_before` days — creating a mid-booking-window band.
`days_before` must be greater than or equal to `days_after` when both are provided.

- `type` (string, required, one of: `time_based`)
- `days_after` (integer, nullable): Applies on/after “today + days_after”. When combined with `days_before`, creates a mid-window band (see rule description). `null` when this side of the window is unset.
- `days_before` (integer, nullable): Applies within “today + days_before”. Must be >= `days_after` when both are set. `null` when this side of the window is unset.
- `months` (array of integer, min items: 1, each item min: 1, max: 12): When set, restrict to these month ordinals (1–12).
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of number, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (number)

### `calendar_rule_seasonal`

Type: object `calendar_rule_seasonal`

**seasonal** — Tied to a custom seasonal date range. Set `id` to the custom range. Provide `value` or `day_of_week_values`, not both.

- `type` (string, required, one of: `seasonal`)
- `id` (integer | string, required): Custom seasonal date-range identifier.
  - One of:
    - **Option 1** (integer)
    - **Option 2** (string)
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of number, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (number)

### `calendar_rule_event`

Type: object `calendar_rule_event`

**event** — Tied to a custom event date range. Set `id` to the custom range. Provide `value` or `day_of_week_values`, not both.

- `type` (string, required, one of: `event`)
- `id` (integer | string, required): Custom event / date-range identifier.
  - One of:
    - **Option 1** (integer)
    - **Option 2** (string)
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of number, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (number)

### `calendar_rule_monthly_simple`

Type: object `calendar_rule_monthly_simple`

**monthly** — Limited to specific `months`. Provide `value` or `day_of_week_values`, not both.

- `type` (string, required, one of: `monthly`)
- `months` (array of integer, required, min items: 1, each item min: 1, max: 12): Month ordinals (1–12); at least one.
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of number, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (number)

### `calendar_rule_day_of_week`

Type: object `calendar_rule_day_of_week`

**day_of_week** — Per weekday (7 values, Sunday-first). Optional `months` limits to those month ordinals.
Must not combine with `days_before` / `days_after` (use `time_based` for that).

- `type` (string, required, one of: `day_of_week`)
- `months` (array of integer, min items: 1, each item min: 1, max: 12): When set, restrict to these month ordinals (1–12).
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of number, required, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.

### `calendar_rule_custom`

Type: object `calendar_rule_custom`

**custom** — Fixed calendar date range. `start_date` and `end_date` inclusive; optional `yearly` repeats each year.
Provide `value` or `day_of_week_values`, not both.
UI: 'Date-specific overrides.' Not related to `custom_date_ranges` (Events & Seasons), Custom Rates, or the `CUS` preset type.

- `type` (string, required, one of: `custom`)
- `end_date` (string (date), required): Inclusive end (ISO-8601 date).
- `id` (integer | string): Server-assigned identifier, returned as a string when present. On `checkin_checkout` rules it pairs a check-in rule with its check-out rule and is derived from the rule's contents, so it changes when the rule changes (on `seasonal` and `event` rules it is the season or event id instead). Requests don't use it to identify a rule, so don't store it as a stable key.
  - One of:
    - **Option 1** (integer)
    - **Option 2** (string)
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `start_date` (string (date), required): Inclusive start (ISO-8601 date).
- `yearly` (boolean): When true, repeat the same month/day span every year.
- `day_of_week_values` (array of number, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (number): Single value for dates in range when `day_of_week_values` is not used.

### `calendar_rule_monthly`

Type: object `calendar_rule_monthly`

**monthly** — Limited to specific `months`. Provide `value` or `day_of_week_values`, not both.
For linear interpolation (`step: false`), set `start_value` and `end_value` with the peak in `value`.
Linear interpolation is only honored in the `seasonality_adjustment` setting, and not when `smooth` is `true`.

- `type` (string, required, one of: `monthly`)
- `months` (array of integer, required, min items: 1, each item min: 1, max: 12): Month ordinals (1–12); at least one.
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of number, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `end_value` (number): Value at month end for linear interpolation when `step` is false.
- `start_value` (number): Value at month start for linear interpolation when `step` is false.
- `step` (boolean): When true, stepped monthly values; when false, linear interpolation using `start_value`, `value` (peak), and `end_value`. Ignored in `seasonality_adjustment` when `smooth` is `true`.
- `value` (number): Single value for the month or peak value when interpolating.

### `calendar_rule_global`

Type: object `calendar_rule_global`

**global** — Single default for the calendar in this rule set. Must not set `day_of_week_values`.
UI: 'Default' or 'Minimum price default' (label varies by setting).

- `type` (string, required, one of: `global`)
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `value` (number, required): Default value (non-negative).

### `gap_night`

Type: object `gap_night`

Gap night pricing strategy (UI: 'Gaps & Adjacencies' in the Pricing Engine panel). Controls the price multiplier for
gap nights between bookings. When `type` is `CUS`, provide `custom` rules; the server rejects `CUS` without `custom`.
This is a **pricing-only** setting. It is unrelated to the `gap` and `adjacency`/`one_sided_gap` rule types in
`minimum_stay_rules_v3`, which control minimum stay behavior for gap nights. In a request the `custom` array
replaces the stored one.

Gap night pricing does not apply to listings with more than one unit. The setting is still accepted, and
the response carries a `not_supported_for_multi_unit` warning.

- `custom` (array of object `gap_night_custom_rule`): Per-gap custom rules. Required when `type` is `CUS` (may be an empty array). Each entry targets a gap length,
  weekday set, and optional one-sided adjacency (`left` / `right`).
  - Each item: One custom gap-night rule. `adjustment` is a price multiplier greater than 0 and at most 10 (`0.8` is a 20%
    discount). `day_of_week` uses 0 = Sunday through 6 = Saturday, unique values only, length 1–7. When several
    rules match a night, rules without `adjacent` are checked first, then `left`, then `right`. Within those,
    the rule with the smallest `gap` that still covers the gap wins, and among rules sharing that `gap` the
    largest `adjustment` wins.
  - `adjacent` (string, one of: `left`, `right`): Omit to match open nights with an unavailable night on both sides ("In between"). `left` matches the
    first `gap` open nights after an unavailable night ("Only after"); `right` matches the last `gap` open
    nights before one ("Only before").
  - `adjustment` (number, required): Price multiplier; greater than 0 and at most 10. `0.8` is a 20% discount.
  - `day_of_week` (array of integer, required, min items: 1, max items: 7, each item min: 0, max: 6): Weekdays this rule applies to (0–6, each at most once).
  - `gap` (integer, required): Applies to gaps of this many nights or fewer.
- `type` (string, required, one of: `CON`, `REC`, `AGG`, `CUS`): Preset strategy (`CON`, `REC`, `AGG`) or custom (`CUS`) gap-night rules.

### `integer_calendar_rule`

Type: object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`

Integer calendar rules (minimum stay, min/max price caps, local events, check-in/out, long-term discounts, etc.).

- One of:
  - **calendar_rule_adjacency_int** (object `calendar_rule_adjacency_int`): Integer-valued adjacency / one-sided gap rule (same semantics as `calendar_rule_adjacency`). Only used in `minimum_stay_rules_v3` (MLOS behavior). Not related to the `gap_night` pricing setting.
    - `type` (string, required, one of: `adjacency`, `one_sided_gap`): Use `adjacency` or legacy `one_sided_gap` (same behavior).
    - `adjustment` (integer): Add to the existing calendar value instead of replacing it.
    - `day_of_week_adjustments` (array of integer, min items: 7, max items: 7, each item nullable): Per-day adjustments (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
    - `days_adjacent` (integer, required): Window of adjacent days (negative = prior side, positive = subsequent side). To match both sides, use two separate rules — one with a negative value and one with a positive value. When both rules fire on the same date, the negative rule's value takes precedence (it is evaluated last and overwrites the positive rule's result).
    - `days_after` (integer): Legacy alias retained on some stored adjacency rules. Prefer `days_adjacent`.
    - `days_one_sided_gap` (integer): Legacy alias retained on some stored adjacency rules. Prefer `days_adjacent`.
    - `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
    - `day_of_week_values` (array of integer, min items: 7, max items: 7, each item nullable): Per-day minimums (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
    - `value` (integer): Single minimum when `day_of_week_values` is not used.
  - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
  - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
  - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
  - **calendar_rule_gap_int** (object `calendar_rule_gap_int`): **gap** — When `gap_enabled` is true, applies a minimum stay only for "gap" nights that cannot fit the normal min stay.
    Provide `value` or `day_of_week_values` for the gap minimum. Optional `days_before` / `days_after` scope the rule in time.
    Only used in `minimum_stay_rules_v3` (MLOS behavior). Not related to the `gap_night` pricing setting.

    **gap** — When `gap_enabled` is true, applies a minimum stay only for “gap” nights that cannot fit the normal min stay.
    Provide `value` or `day_of_week_values` for the gap minimum. Optional `days_before` / `days_after` scope the rule in time.
    - `type` (string, required, one of: `gap`)
    - `days_after` (integer)
    - `days_before` (integer)
    - `gap_enabled` (boolean, required, one of: `true`)
    - `gap_flexibility` (integer): Reduces effective min stay in the gap by this many nights. It will never drop below `value`.
    - `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
    - `day_of_week_values` (array of integer, min items: 7, max items: 7, each item nullable): Per-day gap minimums (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
    - `value` (integer): Gap minimum stay (integer in typical min-stay rules).
  - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
  - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
  - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
  - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.

### `calendar_rule_global_int`

Type: object `calendar_rule_global_int`

**global** — Single default for the calendar in this rule set. Must not set `day_of_week_values`.
UI: 'Default' or 'Minimum price default' (label varies by setting).

- `type` (string, required, one of: `global`)
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `value` (integer, required): Default value (non-negative).

### `calendar_rule_time_based_int`

Type: object `calendar_rule_time_based_int`

**time_based** — Relative to "today" for the listing. At least one of `days_before` or `days_after` must be set.
Provide `value` or `day_of_week_values`, not both. Optional `months` scopes by calendar month.

When only `days_before` is set, the rule applies to dates within that many days of today (last-minute window).
When only `days_after` is set, the rule applies to dates at least that many days away (far-future window).
When both are set, the rule applies to dates that satisfy both conditions simultaneously — at least
`days_after` days away AND within `days_before` days — creating a mid-booking-window band.
`days_before` must be greater than or equal to `days_after` when both are provided.

**time_based** — Relative to “today” for the listing. At least one of `days_before` or `days_after` must be set.
Provide `value` or `day_of_week_values`, not both. Optional `months` scopes by calendar month.

When only `days_before` is set, the rule applies to dates within that many days of today (last-minute window).
When only `days_after` is set, the rule applies to dates at least that many days away (far-future window).
When both are set, the rule applies to dates that satisfy both conditions simultaneously — at least
`days_after` days away AND within `days_before` days — creating a mid-booking-window band.
`days_before` must be greater than or equal to `days_after` when both are provided.

- `type` (string, required, one of: `time_based`)
- `days_after` (integer, nullable): Applies on/after “today + days_after”. When combined with `days_before`, creates a mid-window band (see rule description). `null` when this side of the window is unset.
- `days_before` (integer, nullable): Applies within “today + days_before”. Must be >= `days_after` when both are set. `null` when this side of the window is unset.
- `months` (array of integer, min items: 1, each item min: 1, max: 12): When set, restrict to these month ordinals (1–12).
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of integer, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (integer)

### `calendar_rule_seasonal_int`

Type: object `calendar_rule_seasonal_int`

**seasonal** — Tied to a custom seasonal date range. Set `id` to the custom range. Provide `value` or `day_of_week_values`, not both.

- `type` (string, required, one of: `seasonal`)
- `id` (integer | string, required): Custom seasonal date-range identifier.
  - One of:
    - **Option 1** (integer)
    - **Option 2** (string)
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of integer, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (integer)

### `calendar_rule_event_int`

Type: object `calendar_rule_event_int`

**event** — Tied to a custom event date range. Set `id` to the custom range. Provide `value` or `day_of_week_values`, not both.

- `type` (string, required, one of: `event`)
- `id` (integer | string, required): Custom event / date-range identifier.
  - One of:
    - **Option 1** (integer)
    - **Option 2** (string)
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of integer, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (integer)

### `calendar_rule_monthly_int`

Type: object `calendar_rule_monthly_int`

**monthly** — Limited to specific `months`. Provide `value` or `day_of_week_values`, not both.

- `type` (string, required, one of: `monthly`)
- `months` (array of integer, required, min items: 1, each item min: 1, max: 12): Month ordinals (1–12); at least one.
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of integer, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (integer): Single value for the month.

### `calendar_rule_day_of_week_int`

Type: object `calendar_rule_day_of_week_int`

**day_of_week** — Per weekday (7 values, Sunday-first). Optional `months` limits to those month ordinals.
Must not combine with `days_before` / `days_after` (use `time_based` for that).

- `type` (string, required, one of: `day_of_week`)
- `months` (array of integer, min items: 1, each item min: 1, max: 12): When set, restrict to these month ordinals (1–12).
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `day_of_week_values` (array of integer, required, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.

### `calendar_rule_custom_int`

Type: object `calendar_rule_custom_int`

**custom** — Fixed calendar date range. `start_date` and `end_date` inclusive; optional `yearly` repeats each year.
Provide `value` or `day_of_week_values`, not both.
UI: 'Date-specific overrides.' Not related to `custom_date_ranges` (Events & Seasons), Custom Rates, or the `CUS` preset type.

- `type` (string, required, one of: `custom`)
- `end_date` (string (date), required): Inclusive end (ISO-8601 date).
- `id` (integer | string): Server-assigned identifier, returned as a string when present. On `checkin_checkout` rules it pairs a check-in rule with its check-out rule and is derived from the rule's contents, so it changes when the rule changes (on `seasonal` and `event` rules it is the season or event id instead). Requests don't use it to identify a rule, so don't store it as a stable key.
  - One of:
    - **Option 1** (integer)
    - **Option 2** (string)
- `priority` (number, read-only): Read-only. Assigned automatically by the server based on rule type; any value submitted in a request body is ignored.
- `start_date` (string (date), required): Inclusive start (ISO-8601 date).
- `yearly` (boolean): When true, repeat the same month/day span every year.
- `day_of_week_values` (array of integer, min items: 7, max items: 7, each item nullable): Per-day values (length 7; index 0 = Sunday). A null element means this rule does not apply for that weekday — the date falls through to the next applicable rule in the hierarchy. Use `0` to explicitly apply a zero value.
- `value` (integer): Single value for dates in range when `day_of_week_values` is not used.

### `occupancy_pacing`

Type: object `occupancy_pacing`

Occupancy pacing matrix configuration. `{}` means pacing is off, which is the default for a new listing.
When `occupancy_pacing` is sent as a non-empty object, `adjusted` and `pacing` are required, and `pacing`
must include a matrix with `type` `global` (otherwise the request is rejected with 400). In a request the
object replaces the stored one as a whole; omit it to leave pacing unchanged.

For each lead-time column, occupancy is measured across that whole window and the matching row's
percentage is applied to every date in it. A row covers occupancy above `min` up to and including
`max` (`min` `0` includes 0%); the first matching row wins, and dates outside every column or row are
unchanged. The adjusted price still respects the listing's minimum and maximum price rules.

- `adjusted` (boolean): When true, occupancy is computed as booked nights divided by bookable (unblocked) nights; when false,
  against calendar days × units.
- `pacing` (array of object `occupancy_pacing_matrix`): Pacing matrices. Must include one with `type` `global`, which is the one applied; others are ignored.
  - Each item: One pacing matrix (rows × columns of adjustment percentages).
  - `columns` (array of object `occupancy_pacing_column`, required): Lead-time column definitions; count must match each row in `values`.
    - Each item: Lead-time window (days from today) for one column of the pacing matrix.
    - `days_max` (integer, required, min: 0, max: 1000): Inclusive end of lead-time window (0–1000). Must be greater than or equal to `days_min`.
    - `days_min` (integer, required, min: 0, max: 1000): Inclusive start of lead-time window (0–1000).
  - `rows` (array of object `occupancy_pacing_row`, required): Occupancy (or revenue) percentage band rows; each `min`/`max` is 0–100 for occupancy pacing.
    - Each item: Occupancy percentage band for one row of the pacing matrix.
    - `max` (integer, required, min: 0, max: 100): Upper bound of the band (0–100 inclusive).
    - `min` (integer, required, min: 0, max: 100): Lower bound of the band (0–100 inclusive).
  - `type` (string, required): Rule discriminator; `global` is used for the active pacing matrix.
  - `values` (array of array of integer, required): Price adjustments as whole percentages (`-10` is a 10% decrease, `10` a 10% increase), each ≥ -100.
    One array per entry in `rows`, each holding one value per entry in `columns`; any other shape is
    rejected with 400.

### `fee_adjustments`

Type: object `fee_adjustments`

UI: 'Asking Rate (+Est. Fees)' — The estimated share of fees guests pay on top of the nightly rate, as a
percentage of that rate. It is what `GET /listings/{listing_id}/fee_impact_calendar` returns as a per-date
multiplier. A response carries `null` when nothing is configured, otherwise both keys. In a request the
object replaces the stored one as a whole, so send both keys; `null` clears the setting.

- `total_fee_percentage` (number): Fees as a percentage of the nightly rate, `-100` or more. `15` means guests pay about 15% on top of the nightly rate in fees; there is no upper bound, since fees can exceed the nightly rate on short stays. Omitted means `0`.
- `auto_update` (boolean): When `true`, `total_fee_percentage` is recalculated weekly from the fees on the listing's recent reservations, replacing whatever was set. Defaults to `false` when omitted.

### `custom_date_range`

Type: object `custom_date_range`

Represents an Event or Season entry used by the Wheelhouse Events & Seasons feature.
Calendar rules reference these entries by `id` to apply settings (e.g. min stay, pricing)
over named date windows.

Each listing stores its own copy of every Event or Season it belongs to. Entries for the
same event or season share the same `id` across listings — this shared `id` is what enables
bulk adjustments in the Wheelhouse UI. If you write a `custom_date_ranges` entry with a new
or changed `id`, that listing's entry is no longer linked to the others and will not be
included in future bulk edits of the original Event or Season.

To safely modify an event or season's definition (dates or name) on one listing without
affecting others, omit the `id` field — the server assigns a new independent ID scoped to
that listing. To update only a rule value (e.g. raise the minimum price) without changing
dates, include the existing `id` unchanged.

- `date_ranges` (array of object `custom_date_range_segment`, required): One or more inclusive calendar spans. Each span must include `start_date` and `end_date`, and
  `start_date` must be on or before `end_date`.
  - Each item: Inclusive calendar span within a custom date range.
  - `end_date` (string (date), required): Inclusive end (ISO-8601 date).
  - `start_date` (string (date), required): Inclusive start (ISO-8601 date).
- `id` (string): Stable identifier for this range, referenced by calendar rules. Listings that share the
  same `id` for an entry are considered part of the same Event or Season and can be
  bulk-edited together. Preserve the existing `id` when updating an entry to keep it
  linked; omit only when creating a new range (one will be assigned). The server always
  returns this field as a string. Calendar rule `id` fields accept both string and integer
  for backward compatibility, but the canonical type is string — use string comparisons
  when matching rule `id` values against `custom_date_ranges` entries.
- `name` (string, required): Display name for the season or event.
- `type` (string, required, one of: `event`, `seasonal`): Whether this range represents a recurring season or a dated event.
- `yearly` (boolean, required): When true, the date spans repeat each calendar year (same month/day pattern).

### `listing_preference_response`

Type: object `listing_preference_response`

The full set of pricing preferences for a listing.

- `listing_id` (integer, read-only): The Wheelhouse internal listing ID.
- `partner_listing_id` (string, read-only): The channel's listing ID.
- `currency` (string, nullable, read-only): The currency used for prices in this listing's preferences.
- `automatic_rate_posting_enabled` (boolean): Whether Wheelhouse automatically posts prices to the channel calendar. When `false`, recommendations are computed but nothing is pushed to the channel.
- `base_price` (number, nullable): The base price the user set by hand, in the preferences `currency`. When set, the pricing engine uses it instead of the Wheelhouse recommendation, and `base_price_adjustment` is `null`.

  `null` does **not** mean the listing has no base price. It means the base price follows the Wheelhouse recommendation, multiplied by `base_price_adjustment` (or by `1.0` when that is also `null`). To read the base price in use, call `GET /listings/{listing_id}/price_recommendations` and read its top-level `base_price`.

  Set to `null` to go back to the Wheelhouse recommendation, or set a preset with `PUT /preferences/{listing_id}/base_price_adjustment` and `type` `CON`, `REC`, or `AGG`.
- `base_price_adjustment` (number, nullable): The multiplier the pricing engine applies to the Wheelhouse recommended base price (`base_price_recommended` on `GET /listings/{listing_id}/price_recommendations`) when `base_price` is `null`. The presets are `0.9` (conservative, `CON`), `1.0` (recommended, `REC`), and `1.1` (aggressive, `AGG`). Any other value is a custom adjustment, for example `1.05` for 5% above the recommendation.

  For example, with `base_price_recommended` 200 and `base_price_adjustment` `0.9`, the base price in use is 180, and `base_price` here is `null`.

  `null` when `base_price` is set, because the manual base price applies instead. Both fields can also be `null`, for example after a manual base price is cleared. The pricing engine then uses `1.0`, the recommended preset.
- `monthly_discount` (integer, nullable, default: `0`): Monthly discount percentage as an integer in the range 0–100 (e.g. `5` = 5%). On listings that accept length-of-stay premiums (every listing whose `supported_settings.long_term_discount_type` is `complex`, and some with `rules`), values are signed instead, so `-10` is a 10% discount and `10` a 10% premium. Applied to bookings ≥ 28 nights. Kept in sync with the global rule in `long_term_discounts.rules['28']` — setting one automatically updates the other. When both are sent in the same PUT, `long_term_discounts` takes precedence.
- `weekly_discount` (integer, nullable, default: `0`): Weekly discount percentage as an integer in the range 0–100 (e.g. `5` = 5%). On listings that accept length-of-stay premiums (every listing whose `supported_settings.long_term_discount_type` is `complex`, and some with `rules`), values are signed instead, so `-10` is a 10% discount and `10` a 10% premium. Applied to bookings ≥ 7 nights. Kept in sync with the global rule in `long_term_discounts.rules['7']` — setting one automatically updates the other. When both are sent in the same PUT, `long_term_discounts` takes precedence.
- `nickname` (string, nullable): Listing nickname.
- `last_minute_discount` (object, nullable): UI: 'Last minute' — Last-minute discount configuration.
  - `type` (string, one of: `CON`, `REC`, `AGG`, `CUS`)
  - `rules` (array of object `calendar_rule_time_based` | object `calendar_rule_seasonal` | object `calendar_rule_event` | object `calendar_rule_monthly_simple` | object `calendar_rule_day_of_week` | object `calendar_rule_custom`): Calendar rules when `type` is `CUS`. Valid rule types: `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
    - One of:
      - **calendar_rule_time_based**: see `calendar_rule_time_based` under Schemas.
      - **calendar_rule_seasonal**: see `calendar_rule_seasonal` under Schemas.
      - **calendar_rule_event**: see `calendar_rule_event` under Schemas.
      - **calendar_rule_monthly_simple**: see `calendar_rule_monthly_simple` under Schemas.
      - **calendar_rule_day_of_week**: see `calendar_rule_day_of_week` under Schemas.
      - **calendar_rule_custom**: see `calendar_rule_custom` under Schemas.
  - `smooth` (boolean, default: `false`): UI: 'Smooth' — Only used when `type` is `CUS`. When `true`, the adjustment eases gradually from one rule to the next instead of jumping at each rule's edge. `custom` rules still apply exactly. Defaults to `false` (stepped).
- `far_future_premium` (object, nullable): UI: 'Far future' — Far-future premium configuration.
  - `type` (string, one of: `CON`, `REC`, `AGG`, `CUS`)
  - `rules` (array of object `calendar_rule_time_based` | object `calendar_rule_seasonal` | object `calendar_rule_event` | object `calendar_rule_monthly_simple` | object `calendar_rule_day_of_week` | object `calendar_rule_custom`): Calendar rules when `type` is `CUS`. Valid rule types: `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
    - One of:
      - **calendar_rule_time_based**: see `calendar_rule_time_based` under Schemas.
      - **calendar_rule_seasonal**: see `calendar_rule_seasonal` under Schemas.
      - **calendar_rule_event**: see `calendar_rule_event` under Schemas.
      - **calendar_rule_monthly_simple**: see `calendar_rule_monthly_simple` under Schemas.
      - **calendar_rule_day_of_week**: see `calendar_rule_day_of_week` under Schemas.
      - **calendar_rule_custom**: see `calendar_rule_custom` under Schemas.
  - `smooth` (boolean, default: `false`): UI: 'Smooth' — Only used when `type` is `CUS`. When `true`, the adjustment eases gradually from one rule to the next instead of jumping at each rule's edge. `custom` rules still apply exactly. Defaults to `false` (stepped).
- `seasonality_adjustment` (object, nullable): UI: 'Seasonality' — Seasonality adjustment configuration.
  - `type` (string, one of: `CON`, `REC`, `AGG`, `CUS`)
  - `rules` (array of object `calendar_rule_seasonal` | object `calendar_rule_event` | object `calendar_rule_monthly`): Calendar rules when `type` is `CUS`. Valid rule types: `seasonal`, `event`, `monthly`.
    - One of:
      - **calendar_rule_seasonal**: see `calendar_rule_seasonal` under Schemas.
      - **calendar_rule_event**: see `calendar_rule_event` under Schemas.
      - **calendar_rule_monthly**: see `calendar_rule_monthly` under Schemas.
  - `smooth` (boolean, default: `false`): UI: 'Smooth' — Only used when `type` is `CUS`. When `true`, the adjustment eases gradually from one rule to the next instead of jumping at each rule's edge, and monthly rules' `step`, `start_value` and `end_value` are ignored. Defaults to `false` (stepped).
- `day_of_week` (object, nullable): Day-of-week pricing factor configuration.

  - `REC` applies the market's day-of-week pattern.
  - `CON` and `AGG` adjust that pattern conservatively or aggressively. Sent without `rules`, they
    store the matching preset `day_of_week` rule.
  - `ADJ` applies the market's pattern and multiplies your own `rules` on top of it.
  - `CUS` replaces the market's pattern with your own `rules`, whose values are price multipliers
    (`1.1` is 10% higher). `CUS` without `rules` prices every day the same.

  A `CUS` setting saved before the day-of-week and local events split is returned as `ADJ`, since
  that is how it has priced since the split.
  - `type` (string, one of: `CON`, `REC`, `AGG`, `ADJ`, `CUS`)
  - `rules` (array of object `calendar_rule_global` | object `calendar_rule_time_based` | object `calendar_rule_seasonal` | object `calendar_rule_event` | object `calendar_rule_monthly_simple` | object `calendar_rule_day_of_week` | object `calendar_rule_custom`): Calendar rules when `type` is `ADJ` or `CUS`. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
    - One of:
      - **calendar_rule_global**: see `calendar_rule_global` under Schemas.
      - **calendar_rule_time_based**: see `calendar_rule_time_based` under Schemas.
      - **calendar_rule_seasonal**: see `calendar_rule_seasonal` under Schemas.
      - **calendar_rule_event**: see `calendar_rule_event` under Schemas.
      - **calendar_rule_monthly_simple**: see `calendar_rule_monthly_simple` under Schemas.
      - **calendar_rule_day_of_week**: see `calendar_rule_day_of_week` under Schemas.
      - **calendar_rule_custom**: see `calendar_rule_custom` under Schemas.
- `gap_night` (object `gap_night`, nullable): Gap night pricing strategy (UI: 'Gaps & Adjacencies' in the Pricing Engine panel). Controls the price multiplier for
  gap nights between bookings. When `type` is `CUS`, provide `custom` rules; the server rejects `CUS` without `custom`.
  This is a **pricing-only** setting. It is unrelated to the `gap` and `adjacency`/`one_sided_gap` rule types in
  `minimum_stay_rules_v3`, which control minimum stay behavior for gap nights. In a request the `custom` array
  replaces the stored one.

  Gap night pricing does not apply to listings with more than one unit. The setting is still accepted, and
  the response carries a `not_supported_for_multi_unit` warning.
  - Fields: see `gap_night` under Schemas.
- `minimum_stay_rules_v3` (array of object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`, default: `[]`): UI: 'Minimum stays' — minimum stay rules. The `_v3` suffix is a stable historical identifier; this field name is not expected to change.
  - Fields: see `integer_calendar_rule` under Schemas.
- `min_stays_enabled` (boolean): Whether minimum stay rules are enabled.
- `minimum_price_rules_v3` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`, default: `[]`): UI: 'Minimum prices' — Minimum price rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`. The `_v3` suffix is a stable historical identifier; this field name is not expected to change.
  - One of:
    - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
    - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
    - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
    - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
    - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
    - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
    - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
- `maximum_price_rules_v3` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`, default: `[]`): UI: 'Maximum prices' — Maximum price rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`. The `_v3` suffix is a stable historical identifier; this field name is not expected to change.
  - One of:
    - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
    - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
    - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
    - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
    - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
    - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
    - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
- `checkin_checkout` (object, nullable): Which days guests may check in and check out. Rule values are allow flags: `1` allows the day and
  `0` blocks it. A `day_of_week` rule's `day_of_week_values` has 7 entries, index 0 = Sunday. Where rules
  overlap, the more specific rule type wins (for example a date-specific `custom` rule over a
  `day_of_week` rule); between rules of the same type, the later one in the array wins.

  In a request the object replaces the stored one as a whole: send `active` and both
  `check_in_rules` and `check_out_rules` (a request missing either array is rejected with 400). An
  empty `check_out_rules` leaves check-out unrestricted.

  Example, check-in on Friday and Saturday only, check-out any day:

  ```json
  {
    "active": true,
    "auto_adjust": false,
    "check_in_rules": [{"type": "day_of_week", "day_of_week_values": [0, 0, 0, 0, 0, 1, 1]}],
    "check_out_rules": [{"type": "day_of_week", "day_of_week_values": [1, 1, 1, 1, 1, 1, 1]}]
  }
  ```
  - `active` (boolean): Whether the check-in/check-out rules are enforced. Stored as `false` when omitted.
  - `auto_adjust` (boolean): When `true`, Wheelhouse opens additional check-in and check-out days around unavailable nights so that open stretches between bookings can still be booked, even on days the rules would otherwise block.
  - `check_in_rules` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`): Allowed check-in rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
    - One of:
      - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
      - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
      - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
      - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
      - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
      - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
      - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
  - `check_out_rules` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`): Allowed check-out rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
    - One of:
      - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
      - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
      - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
      - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
      - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
      - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
      - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
- `long_term_discounts` (object, default: `{"active":false,"weekly_rules":[],"monthly_rules":[],"rules":{}}`): Rule-based long-term discount configuration.
  - `active` (boolean)
  - `weekly_rules` (array of object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`, **deprecated**): Weekly discount rules (integer calendar rules).
    - Fields: see `integer_calendar_rule` under Schemas.
  - `monthly_rules` (array of object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`, **deprecated**): Monthly discount rules (integer calendar rules).
    - Fields: see `integer_calendar_rule` under Schemas.
  - `rules` (map of string to array of object `calendar_rule_adjacency_int` | object `calendar_rule_custom_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_event_int` | object `calendar_rule_gap_int` | object `calendar_rule_global_int` | object `calendar_rule_monthly_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_time_based_int` `integer_calendar_rule`): LOS-keyed rules (integer calendar rules). Keys are length-of-stay thresholds (e.g. "7", "28"); values are arrays of integer calendar rules holding whole percentages (`10` is a 10% discount). On listings that accept length-of-stay premiums (every listing whose `supported_settings.long_term_discount_type` is `complex`, and some with `rules`), values are signed instead, so `-10` is a 10% discount and `10` a 10% premium.
    - Fields: see `integer_calendar_rule` under Schemas.
- `occupancy_pacing` (object `occupancy_pacing`, nullable, default: `{}`): Occupancy pacing configuration. When `occupancy_pacing` is sent as a non-empty object, both `adjusted` and `pacing` are required.

  Occupancy pacing matrix configuration. `{}` means pacing is off, which is the default for a new listing.
  When `occupancy_pacing` is sent as a non-empty object, `adjusted` and `pacing` are required, and `pacing`
  must include a matrix with `type` `global` (otherwise the request is rejected with 400). In a request the
  object replaces the stored one as a whole; omit it to leave pacing unchanged.

  For each lead-time column, occupancy is measured across that whole window and the matching row's
  percentage is applied to every date in it. A row covers occupancy above `min` up to and including
  `max` (`min` `0` includes 0%); the first matching row wins, and dates outside every column or row are
  unchanged. The adjusted price still respects the listing's minimum and maximum price rules.
  - Fields: see `occupancy_pacing` under Schemas.
- `fee_adjustments` (object `fee_adjustments`, nullable): Estimated fee share applied on top of the nightly rate. `null` when nothing is configured, otherwise both keys are present; in a request the object replaces the stored one as a whole, and `null` clears it.

  UI: 'Asking Rate (+Est. Fees)' — The estimated share of fees guests pay on top of the nightly rate, as a
  percentage of that rate. It is what `GET /listings/{listing_id}/fee_impact_calendar` returns as a per-date
  multiplier. A response carries `null` when nothing is configured, otherwise both keys. In a request the
  object replaces the stored one as a whole, so send both keys; `null` clears the setting.
  - Fields: see `fee_adjustments` under Schemas.
- `demand_sensitivity_rules` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`, default: `[]`): Local events rules. Shown as Demand sensitivity before day of week became its own setting; the field name is unchanged. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
  - One of:
    - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
    - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
    - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
    - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
    - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
    - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
    - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
- `historical_anchoring_price_source` (string, one of: `observed`, `posted`, `posted_with_fallback`, default: `observed`): Which historical price historical anchoring weighs in. `observed`, the default, is the listing's price as Wheelhouse saw it on the channel once the date booked. `posted` is the price Wheelhouse last posted for the date before it booked, so dates Wheelhouse never posted a price for are not anchored. `posted_with_fallback` uses the posted price where there is one and the observed price otherwise.
- `historical_anchoring_mode` (string, one of: `blended`, `anchor_only`, default: `blended`): How a historical anchoring percentage turns the historical price into a floor for the recommendation. `blended` averages the historical price with the recommendation, using the percentage as the weight on the historical price: at 50%, a $1,200 historical price and a $400 recommendation give $800. `anchor_only` takes the percentage of the historical price alone, so at 50% the floor is $600: a $400 recommendation rises to $600 and a $700 one stays at $700. Either only ever raises a price, and from 100% up both give the same price.
- `historical_anchoring_rules` (array of object `calendar_rule_global_int` | object `calendar_rule_time_based_int` | object `calendar_rule_seasonal_int` | object `calendar_rule_event_int` | object `calendar_rule_monthly_int` | object `calendar_rule_day_of_week_int` | object `calendar_rule_custom_int`, default: `[]`): Historical anchoring rules. Valid rule types: `global`, `time_based`, `seasonal`, `event`, `monthly`, `day_of_week`, `custom`.
  - One of:
    - **calendar_rule_global_int**: see `calendar_rule_global_int` under Schemas.
    - **calendar_rule_time_based_int**: see `calendar_rule_time_based_int` under Schemas.
    - **calendar_rule_seasonal_int**: see `calendar_rule_seasonal_int` under Schemas.
    - **calendar_rule_event_int**: see `calendar_rule_event_int` under Schemas.
    - **calendar_rule_monthly_int**: see `calendar_rule_monthly_int` under Schemas.
    - **calendar_rule_day_of_week_int**: see `calendar_rule_day_of_week_int` under Schemas.
    - **calendar_rule_custom_int**: see `calendar_rule_custom_int` under Schemas.
- `custom_date_ranges` (array of object `custom_date_range`, default: `[]`): Represents an Event or Season entry used by the Wheelhouse Events & Seasons feature.
  Calendar rules reference these entries by `id` to apply settings (e.g. min stay, pricing)
  over named date windows.

  Each listing stores its own copy of every Event or Season it belongs to. Entries for the
  same event or season share the same `id` across listings — this shared `id` is what enables
  bulk adjustments in the Wheelhouse UI. If you write a `custom_date_ranges` entry with a new
  or changed `id`, that listing's entry is no longer linked to the others and will not be
  included in future bulk edits of the original Event or Season.

  To safely modify an event or season's definition (dates or name) on one listing without
  affecting others, omit the `id` field — the server assigns a new independent ID scoped to
  that listing. To update only a rule value (e.g. raise the minimum price) without changing
  dates, include the existing `id` unchanged.

  A new `custom_date_ranges` entry and a rule referencing it can be submitted in the same
  PUT request. Manually assign an `id` on the new entry so that the referencing rule can
  use it in the same payload. Alternatively, use two sequential PUTs: the first PUT
  creates the entry without an `id` (the server assigns one, returned in the response);
  the second PUT adds the rule referencing that server-assigned `id`.
  - Fields: see `custom_date_range` under Schemas.
- `min_min_price` (integer, default: `0`): UI: 'Absolute minimum price' — Hard lower bound that overrides all pricing rules. No recommended price will fall below this value regardless of any rule configuration. Distinct from a `global` rule in `minimum_price_rules_v3`, which can be overridden by higher-priority rules. Must be an integer (whole currency units).
- `min_min_stay` (integer, default: `0`): UI: 'Absolute minimum stay' — Hard lower bound that overrides all minimum stay rules. No minimum stay will be set below this value regardless of any rule configuration. Distinct from both a `global` rule in `minimum_stay_rules_v3` (which can be overridden by higher-priority rules) and from `global_min_stay` in the price recommendations response (which reflects the current effective default rule value, not a hard floor).
- `apply_gap_night_rules_to_overrides` (boolean): UI: 'Apply Gap Night Rules to Overrides' — When `true`, gap-night minimum stay rules take priority over custom (date override) rules. When `false` (default), custom rules win over gap-night rules.
- `update_from` (string, read-only): The source used when the preferences were last updated.
- `update_from_id` (integer, nullable, read-only): The ID of the entity used when preferences were last updated.
- `created_at` (string, nullable, read-only): When the listing preferences were created (Rails-style timestamp).
- `updated_at` (string, nullable, read-only): When the listing preferences were last updated (Rails-style timestamp).
- `supported_settings` (object `supported_settings`, read-only): Which listing preference settings this listing's channel can act on. A setting reported `false` is discarded on write rather than posted to the channel, so check this before sending it. Reflects any per-account early access, so two listings on the same channel can differ.
  - `checkin_checkout` (boolean): Whether `checkin_checkout` rules can be set.
  - `min_stays` (boolean): Whether minimum stay settings (`min_min_stay`, `min_stays_enabled`, `minimum_stay_rules`) can be set.
  - `long_term_discounts` (boolean): Whether long-term discounts (`long_term_discounts`, `weekly_discount`, `monthly_discount`) can be set at all.
  - `long_term_discount_type` (string, one of: `disabled`, `simple`, `rules`, `complex`): The form of long-term discount the channel accepts. `disabled` takes none; `simple` takes only flat `weekly_discount` and `monthly_discount` values and ignores a `rules` object; `rules` additionally takes the 7 and 28 night tiers; `complex` takes arbitrary tiers.
- `warnings` (array of object `preference_warning`, read-only, each item read-only): Settings in the request this listing's channel cannot act on, and which were therefore not applied. Present on write responses and empty when everything applied, so it can be read unconditionally; absent on reads, where nothing was being set.
  - Each item: One setting in the request that was not applied, or that has no effect on this listing.
  - `setting` (string, one of: `checkin_checkout`, `gap_night`, `min_stays`, `long_term_discounts`): The setting group the warning is about.
  - `reason` (string, one of: `not_supported_by_channel`, `partially_supported_by_channel`, `not_supported_for_multi_unit`): `not_supported_by_channel` — the channel has no such feature and everything sent for it was dropped. `partially_supported_by_channel` — the channel has the feature but accepts a narrower form than what was sent, and only the excess was dropped. `not_supported_for_multi_unit` — the setting is stored but has no effect on price, because the listing has more than one unit.
  - `message` (string): A human-readable explanation of what was ignored and why.
  - `attributes` (array of string): The request attributes this warning covers, in dot notation for nested ones (e.g. `long_term_discounts.rules.14`).

### `preference_error`

Type: array of string | integer

An error that occurred when processing a listing preference update, returned as a positional tuple in the order `[listing_id, message, http_code]`. The first two elements are strings; the third is an integer HTTP status code (e.g. 404, 403, 423, 406, 409, 500).
