If you're building pricing logic on top of the Wheelhouse RM API, you now have a direct line into how Base Price recommendations have moved over time.

The new endpoint returns a historical log of Base Price settings and recommendations for any listing — so you can track how pricing has evolved, audit changes, or feed historical context into your own tooling without reconstructing it from scratch.

Similarly, you can now pull a day-by-day history of calendar state for any listing — including observed status and posted prices.

This means you can now see, for any date, what price was actually posted and what the observed booking state looked like — a foundational building block if you're building reporting, auditing, or anomaly-detection tools on top of your portfolio's pricing history.

Previously, triggering a fresh price sync for a listing meant waiting on our internal cadence. Now, you can kick off a sync job directly through the API.

This is especially useful if you're building automation that needs pricing to reflect the very latest settings immediately — no more waiting on the next scheduled sync.

Segments — your saved, dynamic portfolio filters — are now fully manageable via the API.

You can create new Segments and edit existing ones programmatically, which means any tooling you're building to manage large or complex portfolios can now define and adjust Segment logic without a manual trip into the Wheelhouse UI.

Teams can now be viewed and managed directly through the API as well. If you're building integrations or internal tools that need to reflect your organization's team structure — who's on which team, and how teams map to portfolios — you can now do that programmatically instead of keeping a manual mirror of it.

Separately from new endpoints, we did a significant pass across the RM API docs to fix mismatches between what the docs described and what the implementation actually does.

If you've hit friction in the past where the docs didn't quite match real behavior, this should meaningfully clean that up.

🥳 Base Price History and Calendar Day History pair well together — combine them to reconstruct a full pricing-and-outcome timeline for any listing, rather than pulling each in isolation.

🚀

All five of these endpoints are live now — which means they're fair game for anything you build during our API Hackathon (July 21–24). Whether you're reconstructing pricing history, automating syncs, or building portfolio tooling around Segments and Teams, this week's additions give you more surface area to work with.

The Wheelhouse MCP (Model Context Protocol) server connects AI coding assistants and chat clients — — directly to your Wheelhouse account.

Once connected, those tools get access to 58 endpoints built on our RM APIs, which offer full 1:1 parity with the Wheelhouse UI. Every portfolio view, every pricing setting, every reservation and comp — accessible via natural language or code.

Your team doesn't need to learn a new interface. They just describe what they want to do.

The range here is wide. A few examples of what this unlocks:

These aren't hypotheticals — these are the kinds of prompts your team can run today, in an afternoon, after a straightforward setup.

The MCP is built on Wheelhouse's new Revenue Management APIs, which were designed from the ground up with external access in mind.

That 1:1 parity matters: you're not working with a simplified read-only layer. You have access to the same data and levers your team uses inside the Wheelhouse UI — pricing preferences, min/max rules, reservations, comp data, custom rates, and more.

To connect an AI assistant to your Wheelhouse account:

📽️ Watch a demo: https://www.loom.com/share/07d239b07b2a4cf18b67e95c0d02311e

TL;DR →

---

Local events are back — and meaningfully improved.

You can now see market events directly on your Individual Listing calendar: conferences, holidays, festivals, and other high-demand dates in your area, all surfaced automatically.

To turn them on, head to your calendar and click the button in the top right. From there, toggle on , and you'll start seeing relevant local demand drivers appear on your calendar.

---

Wheelhouse built its own AI to detect and curate the events that are actually relevant to your market.

The goal: surface the most important things to get right, pricing-wise — not just a firehose of noise.

We're continuing to refine this, and we'd love your feedback. If you're seeing events that don't seem relevant, or missing ones you'd expect, let us know.

---

Here's where it gets interesting.

In addition to Market Events, you can also toggle on from the same Display menu. This layer shows the events and seasons created in your settings — the ones you've already built minimum stay policies, minimum price rules, and other configurations around.

Seeing both layers at once gives you a powerful side-by-side view:

This combination makes it much easier to validate your existing events setup, catch any gaps, and quickly identify demand dates that deserve attention but haven't been configured yet.

---

Are your listings pacing ahead or lagging behind your local market? Answering this question just got a lot faster and more precise.

We’ve rolled out & across Wheelhouse to give you a multi-angle read on your locale's performance.

BNBCalc Markets is a live, searchable map of 10M+ active Airbnb and Vrbo listings. Every listing shows its gross yield and revenue — not estimates, real data — so you can pressure-test any market before committing to it.

When you're evaluating a new property or market, Markets gives you:

If you're already using Wheelhouse to optimize pricing on your current portfolio, Markets answers the question that comes before that: should I add this property or expand into this market at all?

A realistic scenario: you're evaluating a 3BR cabin in a new mountain market. Before you run any numbers in Wheelhouse, you open Markets, find the market, filter for comparable listings, and see the actual revenue distribution — not a headline average. You spot that 2BR properties dominate and 3BRs underperform the market average. Now you're negotiating with real data, or moving on to a better opportunity.

That's the research foundation. Once you have it, you bring the property into Wheelhouse and price it from day one with confidence.

As a Wheelhouse user, you get:

👉 Start your free trial → link

TL;DR →

-

Check-in/check-out configuration just got a lot faster to manage.

You can now make bulk adjustments to your check-in/check-out rules across any date range, right from your calendar.

This is a significant time-saver for anyone managing seasonal transitions or rolling out rule changes across a large date range.

To expand on this capability, you can set check-in/check-out availability by

You can now see your Check-In/Check-Out rules on your calendar views.

Simply open your "display" setup, and toggle on check-in/check-out.

This is the most significant of the three updates.

You've long been able to configure check-in/check-out rules at the season level.

But until now, there was no way to set rules within a season — your seasonal gate rules and your time-based rules lived in separate worlds.

For example, open up more nights for check-in as a stay date approaches for your Summer high season.

This unlocks a much more precise strategy:

🔗

These updates — date-specific overrides, day-of-week customization, and time-based seasonal check-in/check-out — are supported in the Wheelhouse API. If you're managing configurations programmatically, these settings are accessible the same way you'd expect.

🥳 Pair your new time-based seasonal check-in/check-out rules with your minimum stay rules in Events & Seasons Config.

---

📽️ Watch a demo

TL;DR →

-

This is the biggest new metric cluster in this release. Six new metrics let you measure how your listing's occupancy compares to the surrounding neighborhood — across a range of views depending on how you want to look at it.

— the percentage of booked nights in your listing's neighborhood within your selected time frame. Your baseline market occupancy number.

— same as above, but the denominator uses bookable nights only (blocked nights excluded). A cleaner benchmark when you want to strip holds out of both sides of the comparison.

Two metrics show the gap between your listing and the neighborhood in percentage points:

Two metrics express the same comparison as a multiplier:

Together, these give you a fast, multi-angle read on whether your listings are outpacing, matching, or lagging the local market — and by how much.

-

Revenue is the metric you use constantly — for performance reviews, owner reporting, accounting, and market benchmarking. The problem is that "revenue" means different things depending on what question you're asking. We've expanded the revenue metric family so you always know exactly what's included.

Between these four, you can slice your revenue picture in every direction — what you've earned, what guests paid in full, what's tied up in blocks, and what's still on the table.

-

We've added two new RevPAR variants to match the expanded revenue and occupancy definitions.

— Revenue (+ Fees) divided by all calendar nights. Use this when you want a RevPAR figure that reflects the full all-in rate guests see on OTAs, not just rent.

— Revenue divided by bookable nights (blocked nights excluded from the denominator). This gives you a cleaner RevPAR signal when your calendar has a meaningful number of holds or maintenance blocks that you'd rather not have penalizing the metric.

-

— the current observed price from OTAs, inclusive of fees — has been updated and is now available in Market Reports and Sets. This gives you a direct view of what guests are seeing in your market, including the fee loads that increasingly drive booking decisions on platforms like Airbnb and Vrbo.

-

All 13 metrics are live now. You can access them anywhere data lives in Wheelhouse:

We're excited to be bringing transparent, data-driven revenue management to one of the world's most sophisticated vacation rental markets.

Avantio powers professional portfolios across Europe and beyond. Now those operators can pair its vest-in-class Channel Manager and PMS with Wheelhouse's fully customizable pricing & revenue tools.

This partnership lets Avantio operators build their own tools on top of Wheelhouse. You get full API access to our entire pricing stack.

Connecting Wheelhouse & Avantio is fast: 1) Connect your Avantio account, 2) Fine-tune your pricing strategy, 3) Automate and sync.

This isn't just software. Every operator gets dedicated Wheelhouse Revenue Management onboarding to start strong. And Wheelhouse support connects you to a real person in under 60 seconds.

As you might have seen, two weeks ago we announced our new RM API, built to enable anyone to build robust tools on top of the Wheelhouse interface.

And, last week, we announce the Wheelhouse Hackathon (taking place July 20th).

And, this week, we've added new endpoints to the API on a daily basis... with more that are going live as this "goes to press"!

With this update, we're adding a huge amount of market data, for you to be able to analyze, communicate and adjust your pricing strategy, however you please. Enjoy!

Two new endpoints give your integration a daily view of what's happening around each listing:

Until now, the RM API gave you Wheelhouse's recommendations for your listings. Neighborhood Data gives you the market context those recommendations are built on — the daily pricing trends, occupancy rates, and booking pace for comparable properties in the same area.

This is especially useful for:

Each endpoint is scoped to a single listing and returns day-level data, so you can pull exactly the window you need.

This is the biggest of the three additions. Dynamic Sets are Wheelhouse's comparable property groupings — and they're now fully accessible via the RM API.

Nine new endpoints are available:

Dynamic Sets are how Wheelhouse models local market context for each listing. With these endpoints, you can:

The metrics and report endpoints in particular are useful for any integration that surfaces market benchmarking data — you're getting the same comp-set lens Wheelhouse's pricing engine uses.

Three endpoints give your integration access to Wheelhouse's market-level data:

All three endpoints support filtering by bedrooms (0–4+), property_type (house, apartment, cabin, etc.), and performance tier (low / average / high). The time-series endpoint supports date ranges up to 3 years back and 1 year forward.

This is the most data-dense addition in this release.

A few things you can build with it:

The distribution endpoint is particularly useful for owner reports: it lets you show where a listing sits in the market histogram for any given month — not just a market average, but the full spread.

A single new endpoint under the Calendar tag:

Wheelhouse generates price recommendations daily, but what actually lands on the OTA is the posted price — which can differ due to timing, overrides, custom rates, or channel-specific rules.

This endpoint closes that gap. You can now retrieve the last posted price for each stay date on any listing, enabling:

Reconciliation between Wheelhouse recommendations and what actually appeared on the channel

Audit logs or owner-facing reports that show "what we actually charged" vs. "what was recommended"

Debugging distribution issues — if a price didn't update as expected, this is the ground truth

Pair this with the existing Price Recommendations endpoint (GET ) to calculate the delta between recommended and posted prices — a useful signal for auditing override behavior or channel sync issues across your portfolio.

All these endpoint groups are available now under your existing RM API key.

No new authentication or setup required.

➡️ Full documentation: https://api.usewheelhouse.com/wheelhouse_rm_api

Questions or feedback? Our CS team is fully ready to help. Send us an email at hello@usewheelhouse.com, or simply open your normal chat window inside the App.

We're hosting our first-ever Hackathon 🏗️.

The Revenue Hackathon is aimed at teaching, sharing & building together.

This is open to anyone (customers, RM shops, developers in our industry, even our competitors), and will have for builders.

The goal is simple: leveraging (and data, MCP.)

Kickoff is Tuesday July 21 @ 9am PST — we'll start with an online gathering to say hello, give you an overview of some of your tools, and provide a place to meet other builders, in case you are looking for a team.

Throughout the Hackathon, we'll provide dedicated engineering & build support, to ensure the worst possible outcome is that you emerge with a powerful new skillset.

Well... anything!

Our RM API gives you access to live listing data, pricing infrastructure, and the full Wheelhouse platform.

Three days to build whatever you think is possible.

And... so much more.

Spots are limited... only in the name of over-delivering for those who participate.