Skip to main content

How to Preview Pricing Changes Before Applying Them

Learn how to simulate preference changes and see their impact on daily prices before saving anything to your listing.

Written by Ryo

Before committing to a preference change, you can preview exactly how it would affect your listing's daily prices — without saving anything. This is useful for building "what if" tools, showing users a price impact before they confirm, or validating changes programmatically.


Preview a preference change

Send the hypothetical preference values in the request body. The API returns the same price recommendation format as the standard recommendations endpoint — but calculated using your hypothetical settings, not the saved ones.

curl --request POST "https://api.usewheelhouse.com/ss_api/v1/preferences/12345678/preview?channel=airbnb" \
-H "X-Integration-Api-Key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"base_price": 200
}'

Reading the response

The response matches the daily price recommendations format — a data array with one entry per day, plus base price context. Note: min_stay and events are not included in preview responses. Each day does include min_price, the minimum price applied to that date, or null when no minimum applies.

{
"data": [
{ "stay_date": "2026-03-20", "price": 210, "currency": "USD" },
{ "stay_date": "2026-03-21", "price": 240, "currency": "USD" },
{ "stay_date": "2026-03-22", "price": 252, "currency": "USD" }
],
"base_price": 200,
"base_price_recommended": 175,
"base_price_conservative": 158,
"base_price_aggressive": 193
}

Nothing is saved. The listing's actual preferences remain unchanged until you explicitly call the update endpoint.


What you can preview

The request body accepts the same fields as the preferences update endpoint:

  • base_price — the anchor price to simulate

  • base_price_adjustment — a multiplier on Wheelhouse's recommended base price, for example 0.9 for 10% below it (the presets are 0.9, 1.0 and 1.1). Used when base_price is not set

  • last_minute_discount / far_future_premium — discount/premium config objects, same format as the preferences endpoint

  • weekly_discount / monthly_discount — long-stay discount percentages

  • price_model — "current" or "opt_in". "opt_in" returns 400 when there are several opt-in models, so use price_model_id instead

  • price_model_id — the ID of a price model from GET /price_models, used instead of price_model. It must be a model the listing can use and that has run for the listing's market, or the request returns 400

Pass one or multiple fields in a single request to see their combined effect.

Next steps

How to pull reservation data

Did this answer your question?