TL;DR →

📖 Review the API Docs here

The Wheelhouse Revenue Management (RM) API gives you programmatic access to the full dynamic pricing stack.

That distinction matters. Most pricing APIs return a recommended rate.

The Wheelhouse RM API gives you read/write access to the controls behind the rate — base price strategy, seasonality curves, occupancy pacing, demand sensitivity, gap night fills, last-minute discounts, far-future premiums, check-in/out rules, and more.

If you're building an owner-facing dashboard, a view for your RM clients, or an internal analytics tool, this is the infrastructure that makes it possible to surface real revenue management controls — not just push numbers.

To start building, please fill out this form.

APIs used to be the playground for engineers. Not anymore.

With an LLM-based tool — Claude, ChatGPT, Cursor, take your pick — you can describe what you want to build, and start shipping customized workflow enhancements, without writing traditional code from scratch.

Want proof? The majority of the teams and individuals currently building on the RM API have zero or very limited engineering experience — and these builders were up and running within hours.

Owner dashboards. Automated pricing reports. Custom alert systems. The building blocks are here. And yes, you can build!

(PS - need help? Reach out to us to collab!)

One of the most distinctive capabilities of the RM API is the Preview / Simulation endpoint.

This endpoint accepts hypothetical preference changes and returns projected pricing — without saving anything.

This enables you to easily create a "what-if" UI that property managers and their owners have never had before: you can show exactly how a rate calendar would change before committing to it.

Change a base price, adjust a seasonality multiplier, tweak occupancy pacing — and see the full downstream impact, risk-free.

Pair the Simulation Endpoint with your Segments

Use Portfolio Segments to filter down to a specific group of listings, then run preview calls across each listing before applying a bulk preference update.

You'll have a full picture of the projected rate impact across your portfolio — before a single change goes live.

Every daily price recommendation from the Wheelhouse RM API includes optional per-factor attribution — a breakdown of exactly how each signal contributed to the recommended price.

The 10+ factors include: seasonality, local demand, time-to-booking, scarcity, occupancy pacing, any custom adjustments, and more.

For base price recommendations, you get an 8-factor breakdown plus an anchor credibility score from 0–100, indicating how confident the model is in the recommendation.

This means your integrations can explain pricing to property owners in plain language — not just show them a number.

Yes - you can now get the full calendar in one call.

This returns price, availability, booking state, and reservation ID for every stay date — up to 1.5 years out — in a single API call.

If you're building a calendar UI for owners or a booking tool for your team, this eliminates the need to cross-reference a separate availability source.

Everything you need to render a complete, accurate representation of your Wheelhouse calendar is available in one response.

The Wheelhouse RM API is designed for professional property management companies managing listings at scale:

Authentication uses a single RM API key — no separate opt-in, no additional per-listing configuration.

Read-only keys can be issued for analytics integrations and partner access that only need data, not write permissions.

Every write endpoint also includes concurrency protection (409 Conflict) when a request is already in progress for a given listing — production-safe for high-volume integrations.

The Wheelhouse RM API is now live, for anyone who wants early access.

To get started, please sign up here, and we’ll provision your account.

And, here is a demo of how you can get your API keys, once provisioned (hint - anyone can do it!).

Wheelhouse has long been known for our amazing, 24/7 Customer Support team.

And, we’re bringing that same team & approach to our API support.

We're here to help you build.

TL;DR →

---

Your pricing chart is one of the most-used surfaces in Wheelhouse — it's where you validate strategies, spot anomalies, and communicate pricing decisions to owners and teammates. Now you can make it look exactly the way you want.

The new lets you customize the visual appearance of every series on your chart — individually, with precision. Open it from your pricing chart by clicking the chart settings dropdown → → , and a new panel slides in on the right side of your screen.

From there, you're in control.

---

The Theme Editor shows your full list of chart series — Prices (Current Settings), Prices (Observed), Rent + Fee Preview, Base price, Min/Max price, Bookings, Set, Set median, and more. Expand any series to customize:

If you ever want to start fresh, simply click to brings every series back to its defaults in one click.

---

Once you've dialed in an appearance you like, save it as a named . Give it any name — "Owner Report View", "Alice's Setup", whatever makes sense for your workflow.

Switching between profiles is instant. This makes it easy to maintain different chart setups for different contexts: one optimized for your own analysis, another cleaned up for owner-facing conversations, a third for team reviews.

Wheelhouse ships with three ready-to-use profiles:

---

Your pricing chart surfaces a lot of data — easily 15+ series when you're looking at your full picture. The more series are active, the more important visual distinction becomes.

With the Theme Editor, you can make the series that matter most to your current analysis jump out at a glance. Heavier line weight on your Current Settings price. A distinct dash style on Last Year prices. Muted opacity on reference series you want visible but not dominant.

This kind of visual control is especially useful when:

---

📽️ Watch a demo — ![](

TL;DR →

--

"One-Sided Gaps" are now called Adjacencies. This name more accurately describes the function: targeting nights that sit directly next to a booking or a blocked period. You can still find these settings within the Min Stays menu.

--

Kegan, our Head of Onboarding, made an exceptionally thorough walkthrough video here:

--

Adjacency rules now feature Min and Max Lead Time logic. This allows you to trigger rules based on how close the stay date is to today.

Example: You can automatically drop a 3-night minimum to a 1-night minimum, but only if the gap is still unbooked within 7 days of arrival.

--

#New: 🛏️ Relative Min-Stay Adjustment

The system has moved from fixed stay requirements to Relative Adjustments. Instead of forcing a "2-night stay," you now adjust your base settings:

-1: Lowers your current min-stay by one night to fill a shoulder gap.

+2: Increases the requirement by two nights.

0: Maintains the status quo but allows the rule to function for lead-time or priority purposes.

Note: These adjustments respect your Absolute Min Stay floor; a rule will never push your requirements lower than your hard-coded minimum.

--

You can now copy Adjacency rules in bulk via Portfolio Settings > Minimum Stays. This is ideal for quickly rolling out a new shoulder-night strategy across an entire market.

You'll find Adjacencies in the Portfolio Settings > Minimum Stays bulk and copy flows, right alongside Gap Night rules.

Select a source listing with a well-configured Adjacency setup, choose your target listings, and copy.

This is especially useful if you've been manually replicating rules listing by listing. Whether you're rolling out a new shoulder-night strategy across a market or onboarding a new property type, portfolio-level copy makes it fast and consistent.

--

🔢 Advanced Conflict Resolution

A new prioritization toggle, "Priority by Smallest Subsequent Days," allows you to resolve rule conflicts. When enabled, the system will prioritize the rule targeting the smallest window of time, regardless of whether that window falls before or after a booking.

--

Adjacencies are available now for all customers.

To get started:

--

To maximize occupancy, use Gap Night rules (for gaps between two bookings) in tandem with Adjacency rules (for shoulder nights next to one booking). Together, they ensure your calendar remains flexible and protected regardless of how bookings land.

--

This is a seemingly small - but very powerful - feature. In this case, we truly believe this video is worth 1,000 words!

Your pricing chart and calendar are now stitched together.

When you click any point on your pricing chart, your calendar will automatically jump to that date — so the thing you noticed in the chart and the context behind it are always one click apart.

See an unexpected price spike three weeks out? Click it. Your calendar lands right there so you can check what's influencing that day — a nearby event, a gap, an override, etc.

Or, spot a low that doesn't look right, click it, and you're immediately in position to investigate and adjust.

It's a small change aimed to remove a common friction point — the back-and-forth of finding a date in the chart, then manually hunting for it in the calendar.

The Portfolio Calendar has always let you drag a contiguous set of date ranges & listings.

However, it did not enable you to pick scattered, non-adjacent nights and listings, and treat them as a single selection.

Until… now!

As of today, your portfolio calendar enables you to select any individual cells — across non-adjacent dates or listings — and apply a single bulk update across all of them.

This should make your pricing & settings updates much more targeted, precise, and fast.

While there are myriad use cases, here are a few worth highlighting:

It's not unusual to have 1–2 night gaps between reservations.

These gaps can be scattered all over your calendar — different dates, different listings, no perfect pattern.

Before, you'd have to hunt them down one-by-one, and make updates (e.g. lowering min prices, min stays, etc) one at a time.

Now, you can scan your calendar, click each orphan cell, and push updates across all selected cells at once.

To explore another use case, let’s imagine it's Thursday afternoon.

You have unsold nights this weekend scattered across 15 listings — different dates on different properties. You need to act before the weekend window closes.

Multi-select lets you build that exact set of cells — no matter how scattered — and cut rates or remove min stay restrictions across all of them in one shot.

Selecting multiple ranges is quite intuitive.

Simply hold the Control or Command key while making multiple selections.

As you add more cells, a counter shows how many cells, listings, and dates are in scope — so you can see the full picture before you apply any changes.

Accidentally add an extra date or listing?

Simply click that cell while still holding the Control or Command key, and you can easily modify your selection.

Or, close your side panel to one-click clear all active selections.

When your selection is ready, leverage your bulk updates tool much as before, to update any of the following:

And, you can even delete existing rates from all selected cells.

Every bulk update from this multi-range selection creates a changelog entry for each listing.

Each entry records who made the change, when, what was updated, and the specific dates affected for that listing.

Simply navigate to your Portfolio Calendar and start clicking cells to build your selection.

TL;DR →

----------

📡 5 New "In Context" Series

You now have 5 new data series available on any listing's pricing chart.

These series are designed to help you understand your neighborhood's prices and booking pace:

All booking series — Expected, Observed, and their range — are based on bookings in your listing's neighborhood.

We've pre-assembled these series into two new views so you can get to the signal instantly.

----------

From any listing's pricing chart, you can now open the view.

This view includes your standard series:

Plus all 5 new series:

Here's what that unlocks in practice.

Let's say it's early April and you're watching a holiday weekend in late May. The line is already running well above — your neighborhood is booking faster than the model predicted. That's a strong, data-backed signal that demand is spiking earlier than usual, giving you a concrete reason to be more aggressive on price now, before inventory tightens.

The inverse is equally useful: when Observed is lagging Expected, you have early visibility that pace is soft — and you can adjust strategy before it shows up in your own availability numbers.

This is the kind of signal that used to require piecing together comp data manually or waiting for a market report. Now it's right in your chart, and it .

To use it:

----------

The is purpose-built for one of the most important (and tricky) questions in modern STR pricing: what does my guest actually pay, and how does that compare to my neighbors?

Because fees vary by season, booking size, stay length, and channel, your "rent" price alone doesn't tell the whole story. This view brings it all together:

This should help you see exactly how your compare to

To use it:

The is most powerful once your is configured. Head to your listing's Settings → Rent + Fee Preview to confirm your fee load — or toggle on auto-detection so Wheelhouse keeps it current as your fee structure evolves.

📑 Want a reminder of our Model 9.0 Updates? Please read more here

Over the last 8 weeks, you provided a tremendous amount of feedback — often positive, but also constructive — that helped us improve two key aspects of the model. Thank you!

Here is what has been updated since launch:

Our event model is now better calibrated to real demand data. When we see early booking signals for a future event, the model more accurately translates that demand into prices that reflect what guests are actually willing to pay. In practice, this often means higher recommendations for future events with strong early demand — ensuring properties aren't leaving revenue on the table.

Wheelhouse's Pre-Demand Event Protection model ensures that prices reflect potential upcoming demand surges before bookings start rolling in. Based on your feedback and further analysis, we updated Model 9.0 so that PDEP recommendations are more tightly calibrated to what we expect to be the optimal price when future demand arrives.

With these changes locked in, we're now turning our research efforts toward Model 9.1.

The latest (and final) updates to Pricing Engine 9.0 will likely reduce how aggressively our pricing responds to local holidays and events.

Therefore, we recommend taking time to review your market’s major holiday periods to ensure your pricing—and any overrides—are delivering exactly the prices you want.

----------

As of today, Wheelhouse supports both Model 8.3 and Model 9.0. However, we will be phasing out Model 8.3 on , at which point all listings will be automatically moved to Model 9.0.

If you'd like to migrate before that date, Wheelhouse makes it easy to preview your 9.0 pricing, upgrade, and start taking advantage of a model that is driving significant revenue increases.

As a reminder, when we launched Model 9.0 in January, we planned to give users 90 days to evaluate and transition to the new model. Based on these recent updates, we've extended that window — while also making sure we can set the stage to bring Model 9.1 to market.

Hooray! You can now adjust Base Prices across multiple listings.

Before, you could either:

Now, you can:

And, you can do this from 1 to 1,000 listings, at the same time.

Let’s explore what this seemingly small update unlocks for you & your team 🗝️🔒

Let’s imagine it’s the end of the year.

You want to for your .

Before, you had to go to each listing to set those Base Prices 😡!

Now, you can simply:

Similarly, you could decrease your lightly occupied listings by -5% or -$20.

Whatever the adjustment you make, you will see a preview of your future Base Prices right next to the input field.

Ready for the real magic?

Let's combine “Base Price Adjust” with your recently launched “Events & Seasons Config”.

As you might know, you can now set for any event & season you create, as shown in the image below.

Already, when you set a new Base Price, your Event & Season pricing is updated instantly.

Now, since you can safely adjust multiple Base Prices at the same time, you can:

We’d suggest that Base Price Adjust + Events & Seasons is the biggest scale unlock we’ve ever created at Wheelhouse.

🤓 We’d encourage you to read this 3x…, to make sure you absorb this unlock…! Have questions about leveraging this unlock? Message us!

Let’s keep exploring this scale unlock.

As you might know, your can be set up for (20+ years in the future!).

Therefore, when you move up your Base Price, your season & event specific prices are immediately updated, far into the future.

And, since your Events & Seasons now allow you to split your vs. , creating a V1 of next year’s rate plan is a breeze!

Here are more details about Events & Seasons and Rules vs. Overrides, so you can better leverage these features together:

🔗 More about Events & Seasons

🔗 Rules vs. Overrides

→

In the current OTA landscape, it’s especially critical to compare your final distributed prices to other OTA prices.

However, this can be a challenging endeavor, as fee totals can be impacted by:

Therefore, to enable you to better understand your final distributed price, Wheelhouse has added a new “” tool to your settings.

This preview gives you a clearer signal of how your pricing strategy will translate into your posted rates.

For each listing, Wheelhouse now surfaces what our system is seeing as your average fee load, based on observable bookings.

By clicking “apply”, you can can now quickly preview your pricing, with this fee load.

📈

With the fees “applied” you can now see you final rates, but adding the Series “Rent + Fees” to any chart.

This line will show your fee burden, added for your Pricing (Current Settings).

🧮

And, as you might know, you can easily bring in your market range & median, to now see how your Rent + Fees Pricing relates to the market.

To do so, simply add more series to your chart, from the Series list:

➕

If you want to view or preview a different fee load, you can easily do so, by using the input box to see where your pricing will land.

🪄

🥳

And, as a reminder, you can store your OTA links on any listing, so you can quickly click through to your listing pages, and analyze your final prices for any stay length.

Today, Wheelhouse is releasing a new pricing engine that represents a significant improvement in how our ability to drive rental revenue, based on local demand signals.

introduces a (leveraging a “Generalized Additive Model”, methodology detailed below) to replace our last model generation’s “Distributional Pricing” approach.

This new methodology leverages machine learning to better interpret how demand signals relate to the market’s price tolerance, with performance improvements including:

Model 9.0 is much better at decomposing demand into distinct components — seasonal trend, day-of-week effects, and event-specific spikes — and understanding how these components should contribute to specific daily pricing recommendations.

This advancement has two benefits - both making price recommendations more accurate, and making it easier to use your settings to create your ideal pricing strategy.

Model 9.0 is very effective at understanding the relationship between local demand patterns and booked prices. This capability means your engine is far more proficient at analyzing your current competitive landscape, and knowing where to move your pricing in order to maximize revenue.

Importantly, this improvement helps to better position your listing in both high & low demand environments.

Model 9.0 is better at responding to emerging demand signals without overreacting and pushing your prices too dramatically, day over day.

This allows your listings to more precisely adapt to events in the far future, without risking owner/guest complaints from overly reactive pricing changes.

As part of our evaluation of Model 9.0, we have been running an A/B test across >1,000 real, live listings across 20+ markets, and a wide range of inventory.

The results of this ongoing A/B test are available here, and will be updated weekly until the end of the trial (early February).

The new pricing engine is clearly differentiating itself in terms of driving revenue.

Additionally, we are also happy to see that the revenue creation is being partially driven by increased ADR, as well. This helps us determine that these results are not just a short term bump tied to cannibalizing future potential bookings.

Model 9.0 should be much easier to work with - right out of the box.

For our A/B test, our testing team reduced the use of model customizations ~81% between our control & test group for Seasonality, Day of Week, and Demand Sensitivity.

This reduction was based on strong agreement with the output of the new Pricing Engine, in matching their understanding of each local market.

With this launch, we are publishing live results of an ongoing A/B test, in order for you to follow along for learnings, updates & results.

👩‍💻 The live tracker is linked here

Yes, this test has been configured & run by a teammate at Wheelhouse.

However, as you examine how the trial has been structured, I think it will be clear that the trial setup & execution are as fair as possible, and serve as a decent showcase for the different approaches and results for Model 8.3 & 9.0.

With this new Pricing Engine, Wheelhouse has created a new set of tools that will allow you to:

Both on your terms and timeline. Therefore, you will be able to evaluate the where the model recommends increasing & decreasing prices, key model metrics, and more.

Want to evaluate the model, or opt-in to the newest pricing engine?

📄 on from this Help Center article

📽️ on how to upgrade here