listing_id (string, path, required) — the channel's unique listing identifier

channel (string, query, required) — the channel name for this listing (from GET /listings)

listing_id — Wheelhouse's internal numeric ID for this listing

partner_listing_id — the channel's listing ID (same as the id in GET /listings)

base_price — the manually set base price (if set, overrides Wheelhouse's recommendation)

base_price_adjustment — percentage adjustment to the Wheelhouse recommended base price (only present if base_price is not set)

weekly_discount / monthly_discount — discount percentage for stays ≥7 / ≥28 nights (0 = no 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: -10 is a 10% discount and 10 a 10% premium

automatic_rate_posting_enabled — whether Wheelhouse auto-pushes prices to the channel

last_minute_discount / seasonality_adjustment / far_future_premium / day_of_week — objects with type set to CON (conservative), REC (recommended), AGG (aggressive), or CUS (custom). For day_of_week, CUS takes your own rules, whose values are price multipliers (1.1 is 10% higher), and CUS without rules has no effect. Sent without rules, CON and AGG store the matching preset rule

smooth — a boolean on last_minute_discount, far_future_premium and seasonality_adjustment, shown as Smooth in the app. It defaults to false, which is stepped, and it is 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 custom rules still apply exactly. On seasonality_adjustment, smoothing also ignores the step, start_value and end_value of monthly rules

currency — currency used for prices on this listing

fee_adjustments — the estimated fees guests pay on top of the nightly rate (shown as "Asking Rate (+Est. Fees)" in the app). An object with total_fee_percentage (fees as a percentage of the nightly rate, -100 or more; 15 means guests pay about 15% on top) and auto_update (when true, the percentage is recalculated weekly from the fees on recent reservations, replacing what was set; defaults to false). It is null when nothing is configured, otherwise both keys are present. When you update it, the object replaces the stored one as a whole, so send both keys; null clears it. It is what GET /listings/:listing_id/fee_impact_calendar reads

historical_anchoring_mode — how a historical anchoring percentage (Historical Protections in the app) turns the historical price into a floor for the recommendation: blended (default) or anchor_only. 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_price_source — which historical price anchoring weighs in: observed (default), the listing's price as Wheelhouse saw it on the channel once the date booked; posted, the price Wheelhouse last posted for the date before it booked, so dates Wheelhouse never posted a price for are not anchored; or posted_with_fallback, the posted price where there is one and the observed price otherwise

supported_settings — which settings this listing's channel can act on. A setting reported false is discarded on write rather than posted to the channel, so check it before sending that setting

channel (string, required) — the channel name for these listings

listing_ids (string[], optional) — listing IDs to include. Send more than one in brackets (?listing_ids[]=12345678&listing_ids[]=87654321); a key repeated without brackets keeps only its last value. If omitted, returns an empty array (not all listings)

listing_id (string, path, required)

channel (string, query, required)

checkin_checkout — 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. Rule values are allow flags: 1 allows the day and 0 blocks it, and a day_of_week rule has 7 values, with index 0 = Sunday. Where rules overlap, the more specific rule type wins (a date-specific custom rule over a day_of_week rule); between rules of the same type, the later one in the array wins. auto_adjust, when true, opens extra check-in and check-out days around unavailable nights so open stretches between bookings can still be booked.

occupancy_pacing — {} means pacing is off, which is the default for a new listing; omit it to leave pacing unchanged. A non-empty object needs adjusted and pacing, and pacing must include a matrix with type global, otherwise the request is rejected with 400. Each column is a lead-time window in days from today, and each row is an occupancy band: a row covers occupancy above min up to and including max, and the first matching row wins. values holds one array per row with one whole percentage per column (-10 is a 10% decrease), each -100 or more. Any other shape is rejected with 400.

gap_night — the custom array replaces the stored one.

gap (integer, required) — the rule applies to gaps of this many nights or fewer

day_of_week (array of integers, required) — the weekdays the rule applies to, 0 = Sunday through 6 = Saturday, each at most once

adjustment (number, required) — a price multiplier, greater than 0 and at most 10. 0.8 is a 20% discount

adjacent (string, optional) — leave it out 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")

400 — a setting in the request has the wrong shape; the message names the field

423 — preferences not yet initialized for this listing; retry after a brief delay

409 — another request already in progress for this listing; retry after it completes

base_price_adjustment — body: {"type": "CON" | "REC" | "AGG"}

day_of_week — body: {"type": "CON" | "REC" | "AGG"}

seasonality_adjustment — body: {"type": "CON" | "REC" | "AGG"}

last_minute_discount — body: {"type": "CON" | "REC" | "AGG"}

far_future_premium — body: {"type": "CON" | "REC" | "AGG"}

automatic_rate_posting — body: {"enabled": true | false}

listing_id (string, path, required)

setting (string, path, required) — one of the settings listed above

channel (string, query, required)

channel (string, query, required)

listing_preferences (array, body, required) — each entry must include:

207 — some updates succeeded, some failed; check the response body for per-listing breakdown

424 — all updates failed

channel (string, required) — channel name of the target listing

copy_preferences_from (object, required) — identifies the source listing:

listing_id (string, required) — the source listing's channel ID

copy_custom_rates (boolean, optional, default: true) — when true, also copies custom rates from the source to the target

weekly_discount — discount percentage for stays ≥7 nights (integer, nullable)

monthly_discount — discount percentage for stays ≥28 nights (integer, nullable)

channel (string, required)

start_date (string, optional) — start of the date range (YYYY-MM-DD); defaults to 30 days ago, clamped to 90 days max

end_date (string, optional) — end of the date range (YYYY-MM-DD); defaults to tomorrow

time — when the change occurred (ISO 8601)

source — who triggered it: "Wheelhouse" (system), "User" / "User <name>", "API" / "API <name>", "Customer Support", "Wheelhouse team" / "Wheelhouse team <name>". Reservation imports show the name of the person who ran them, including past imports; imports from before the name was recorded still show just "Wheelhouse team". Fixed rate changes made through the RM API or admin tools show where the change came from instead of always showing "User"; older entries still show "User". Preference and custom rate copies made through the RM API show as "API <name>"

event — type of event: "Prices posted", "Calendar synced", "Settings changed", "Custom rates", "Reservations imported"

status — "success", "warning" (partial success: for example some prices posted, but the channel rejected some dates; msg says what to fix) or "error"

msg — human-readable description of the change