Skip to main content

Listing Preferences

Read and update detailed pricing preferences for listings, including base price, seasonality, discounts, min stay rules, and more.

Note: These preferences are called "Settings" in the Wheelhouse app.

Settings your channel may not support​

Not every channel can act on every setting. Some have no concept of check-in/check-out day rules, some cannot take minimum stays, and support for long-term discounts ranges from none at all, through fixed weekly and monthly tiers, to arbitrary ones. Which settings a listing accepts therefore depends on the channel it is connected to.

A setting the channel cannot act on is not applied — it is discarded rather than stored, so it never appears to have taken effect. The rest of the request still applies, and the response is still a success.

Each listing reports what it accepts as supported_settings, on both the listing object and the preferences object. Read it before sending a setting rather than after: a setting reported false will be discarded. It reflects any per-account early access, so two listings on the same channel can differ.

Every write also returns warnings, naming each setting that was not applied, why, and which attributes it covered. The array is present and empty when everything applied, so it can be read unconditionally. reason is not_supported_by_channel when the channel has no such feature, or partially_supported_by_channel when it accepts a narrower form than what was sent and only the excess was dropped. reason is not_supported_for_multi_unit for a setting that is stored but has no effect because the listing has more than one unit; today that is only gap_night.

UI settings panel groups​

The Wheelhouse Settings panel organizes preferences into labeled groups. The table below maps each group to its corresponding API fields.

UI GroupUI Setting NameAPI Field(s)
Pricing EngineBase pricebase_price, base_price_adjustment
Pricing EngineSeasonalityseasonality_adjustment
Pricing EngineDay of weekday_of_week
Pricing EngineLocal eventsdemand_sensitivity_rules
Pricing EngineLast minutelast_minute_discount
Pricing EngineFar futurefar_future_premium
Pricing EngineGaps & Adjacenciesgap_night
Model WeightsHistorical protectionshistorical_anchoring_rules, historical_anchoring_price_source, historical_anchoring_mode
LimitsMaximum pricesmaximum_price_rules_v3
LimitsMinimum pricesminimum_price_rules_v3, min_min_price
OperationsMinimum staysminimum_stay_rules_v3, min_min_stay
OperationsLength of stay pricinglong_term_discounts, weekly_discount, monthly_discount
Calendar PacingOccupancy pacingoccupancy_pacing
ConfigurationEvents & Seasonscustom_date_ranges

demand_sensitivity_rules is the Local events setting. The UI name changed when day of week became its own setting; the field name did not, so existing integrations keep working unchanged. historical_anchoring_* is the same case, shown as Historical protections.

📄️Get the changelog of all changes to a listing.

Returns a list of recent change events for the listing, most recent first. Despite sitting under `/preferences`, the changelog is not limited to preference changes: it is the single history of everything recorded against the listing. It covers changes to the pricing settings, prices posted to the channel and any post or calendar sync that failed, custom rates added, split or removed, a change of pricing engine, and reservations imported for the listing. Read `event` on each entry to tell them apart. Custom rate history is therefore read from here rather than from the Custom Rates endpoints, which report the rates currently in force.