TL;DR →

Until now, keeping your system in sync with Wheelhouse meant polling — calling an endpoint on a schedule and diffing the results to see what changed. Webhooks flip that: you register an HTTPS endpoint once, and Wheelhouse pushes events to it as they happen.

Setting one up is a single call: give us a URL and the event types you want, and you're covered. One subscription spans your entire portfolio — every listing you own plus every listing shared with you to manage — so there's no per-listing setup, and no need to maintain multiple subscriptions as your portfolio grows.

Every event at launch is scoped to a listing:

All three are batched: instead of firing the instant something happens, events collect for 5 minutes, then go out together. So if pickup on 40 listings triggers within the same few minutes, you get one delivery covering all 40 — not 40 separate webhook calls to process.

A few things this actually looks like:

When you create a subscription, the response includes a signing secret — and that's the only time you'll see it. Store it immediately; it can't be read back later. If you lose it, or it leaks, rotate it and you'll get a new one on the spot. Just know the old secret stops working the moment you rotate, so have your endpoint ready to verify against the new one before you do.

Every delivery attempt is logged — the HTTP status your endpoint returned, and the reason for any failure — retained for 7 days and pullable up to 200 at a time. If your endpoint starts timing out or rejecting deliveries, this is where you go to see exactly what Wheelhouse sent and how your side responded.

And if your endpoint goes down for a while, Wheelhouse won't keep hammering it forever: a subscription that fails repeatedly pauses itself automatically. Once your endpoint's healthy again, re-enable the subscription and the failure count clears — it starts fresh rather than counting against you from before the fix.

You're also in control directly: pause a subscription with any time you need to do maintenance on your end, and resume it the same way when you're ready.

Wire a webhook into your workflow, and pair it with a Scoreboards call the moment it fires. The webhook tells you a listing just got flagged — Scoreboards tells you where that listing actually ranks against the rest of your portfolio on the metric that matters, so you're not reacting to one signal in isolation.

📽️ Demo here:

TL;DR →

A few weeks ago, Wheelhouse added dozens of new performance stats.

And, with our RM API live, we wanted to make it easier to analyze your whole portfolio quickly, instead of pulling all data for your listings.

Therefore, we built a new endpoint we call "Scoreboards", so you send one request telling us which stat you care about, and we send back every listing you manage, ranked from best to worst on that stat — in seconds.

Because it's part of our API, you can plug the results you get from Scoreboard straight into whatever tools you already use.

For example: pull the listings losing the most money to blocked dates, and automatically email their owners. Or pull the premium listings that haven't booked in a week, and flag them for a price change.

Before Scoreboards, getting one stat across your whole portfolio meant looking it up one listing at a time, then doing the ranking yourself. That's fine for 5 listings. It's painful for 500.

Scoreboards does the ranking for you. You tell it which stat and which time period you want, and it hands back every listing you manage, already sorted from best to worst — in one request.

Learn more in this 4 minute video:

When you make the request, you only need to tell us two things: which stat you want (we call this the ), and what time period to look at (the ).

There are more than 30 stats to choose from. Roughly, they fall into a few buckets:

For the time period, you can look forward or backward — anywhere from the next/last 7 days out to a full year.

For API calls, you will get an array back you can easily sort. And, for chats (Claude, Open, Gemini) you can simply ask for a "top 5" or "worst 10" — to return a specific number of listings.

Additionally, you can easily filter this list - narrowing your request down to one market, one bedroom count, or anything else you track, on your end.

If your listings are priced in more than one currency, Scoreboards can convert dollar-based stats (like ADR or revenue) into a single currency before ranking, so you're not comparing apples to oranges.

You can access Scoreboard via our MCP as well, enabling you to more quickly analyze your portfolio.

Your LLMs will use Scoreboards and answers in seconds.

We think this looks like the foundation of a better workflow: use Scoreboards to zoom out and find the listings that need attention, then zoom in to fix the ones that need it.

Once Scoreboards has narrowed your portfolio down to a handful of listings worth a closer look, pull each listings full stats history to understand exactly what's going on before you make a change.

You'll find more in our documentation, but for some quick hits, here's how you use this endpoint.

Full metric list:

Ask for a metric/window pairing that isn't valid (e.g. with a window) and you'll get back a rather than a bad number.

A listing with no data for the requested window still shows up, with , so it sorts to the bottom instead of disappearing.

A listing with no stats generated at all is left out entirely.

Wheelhouse handles the revenue management side of your business — but Airbnb's algorithm is weighing a lot more than your nightly rate when deciding who shows up on page one.

Your listing title, photo quality, description strength, review velocity, and availability configuration all factor into how Airbnb ranks and distributes your property to potential guests. A perfectly priced listing that ranks poorly is leaving money on the table — and most of those ranking signals are fixable once you know where the gaps are.

That's the problem AutoRank by Otamiser was built to solve. Their tool audits the listing-level factors that influence your Airbnb ranking, and we've partnered to make it available to Wheelhouse users at no cost.

Drop in any Airbnb URL and the tool evaluates:

You walk away with a clear, scored breakdown of where your listing profile is strong and where it has room to improve.

Getting started takes about 60 seconds (Video proof here!)

No signup required to run the audit. It's fully standalone and free.

If you're managing a large portfolio, start with your top-revenue properties or those in your most competitive markets. That's where small ranking improvements compound fastest — and where a stronger listing profile has the most to add on top of your pricing strategy.

Dynamic Sets (comp sets built from real market listings) have been available in the app for a while — now you can build the entire workflow through the API, from search to upgrade.

Here's the full lifecycle:

Say you manage a portfolio of 3BR cabins near a specific trailhead and want a comp set for one of them. You can now search candidates by lat/long/radius, filter to , review trailing-year occupancy on the results, add the ones you want, and upgrade the set — all without leaving your integration.

Segments (your saved, dynamic portfolio filters) already return listing-level data via the API. Now you can also pull rolled-up performance for the whole segment.

returns monthly metrics aggregated across every listing the segment's filter currently matches.

This is the same aggregated view you'd see reporting on that segment in-app — now available directly to your integration, so you can more easily build dashboards or alerts on top of any segment.

You can now read and manage a user's alert preferences without going through the app:

Supported events include:

If you're building a custom notification center or want to route specific alerts to your own system, this is the endpoint pair for that.

We've raised the default rate limit for RM API keys to . If you're running higher-throughput integrations — syncing large portfolios, polling multiple endpoints, or backfilling historical data — this gives you meaningfully more headroom out of the box.

If you're using the RM API directly, generate or check your API key from your Wheelhouse account under "Api Key," and start with or to see what's available for your account.

If you're connecting through an MCP client, authenticate with OAuth through your client's sign-in flow — the same credentials you use in the Wheelhouse app.

🥳 Pair the new endpoint with your existing Segments to build a lightweight performance dashboard for any saved filter — no need to pull and re-aggregate listing-level data yourself.

Until now, Wheelhouse integrations have meant connecting your PMS or OTA so your prices flow downstream.

This is something different.

IntelliHost is the first partner to build directly on the Wheelhouse API — meaning it can read from and write to your Wheelhouse account programmatically, as part of a fully automated workflow. IntelliHost doesn't just connect to Wheelhouse; it acts on Wheelhouse, on your behalf, based on rules you define.

For property managers running 20 to 200+ units, that's a meaningful distinction. Your pricing strategy is only as good as your ability to execute it consistently — and execution at scale, done manually, is where revenue leaks.

IntelliHost is a performance intelligence platform for professional short-term rental operators. What makes it different: it brings in your real OTA click traffic from Airbnb and Vrbo — the impressions, clicks, and conversions your listings are actually getting — and runs your pricing, your listing optimization, and your portfolio reporting off of that signal.

That traffic data drives three things:

Traffic-based pricing. Every morning, IntelliHost reviews your whole portfolio and finds dates where your pricing is leaving money on the table — based on how much real click demand each date is pulling. When it finds one worth acting on, it pings you in Slack. You tap approve, and the updated rate is pushed directly into Wheelhouse. That’s it.

Automated AI listing optimization. IntelliHost diagnoses where each listing is underperforming — title, photos, amenities, conversion — ranks the fixes by revenue impact in dollars, and rewrites what’s holding the listing back. Visibility isn’t the goal; turning impressions into clicks and clicks into bookings is.

Total portfolio performance. One dashboard shows the health of every property, which listings have the most upside, and what to fix first — instead of a half-day spent compiling spreadsheets.

What IntelliHost handles automatically:

Wheelhouse handles the intelligence layer: building a dynamic pricing strategy calibrated to your market, your comp set, and your listing's demand curve.

IntelliHost handles the execution layer: monitoring that strategy every day against your real OTA traffic, catching the gaps, and acting on approvals without requiring you to log in.

Together, the loop is closed. You set your strategy in Wheelhouse. IntelliHost watches for drift. You approve in Slack. Wheelhouse updates.

No logging in. No copy-paste. No manual re-entry.

For a portfolio of 50 properties, that's the difference between a pricing strategy you review when you have time and one that runs continuously — on your terms, with your approval at every step.

Active IntelliHost users see an average 21% revenue increase — achieved with roughly 10 minutes of hands-on work per week.

That figure comes from IntelliHost's live customer base and reflects the compounding impact of daily portfolio reviews that most managers simply can't do manually at scale.

If you're already a Wheelhouse customer, connecting IntelliHost takes just a few minutes.

IntelliHost is the first in a new class of Wheelhouse API partners. If you've built a tool on top of our API and want to be featured, reach out to hello@usewheelhouse.com

Historical Anchoring has always protected your floors by looking at what actually booked last year.

That's great — until a promo code or channel-specific discount leads to a booking, and that discounted rate quietly becomes your floor for the same date next year.

Now you can choose what Historical Anchoring anchors to:

Imagine a last-minute traveler booked your July 4th weekend at a steep discount, due to PMS or channel specific discounts.

Under Booked price anchoring, that discounted rate could drag down your floor for July 4th next year.

Switch to Wheelhouse's Posted Price, and your floor instead reflects what your engine actually recommended before that discount was applied.

Activating this is a quick switch, that you can setup in your , under .

There are two (2) important callouts for this setting.

, as you know, we only post prices for connected listings.

Therefore, if a booking occurred before you connected to Wheelhouse, we won't know the "final posted price" for your bookings. (We can see the booking amount, but can't infer potential discounts from your final price)

This drawback means this new data source is useful/valuable for listings that have been on Wheelhouse for 1+ years.

, historically we have stored the final posted price for an unbooked night for 7 months.

Starting now, we will store this price posting data for 12+ months, but it will take 5 months for us to accumulate 12 months of historic prices for each stay date.

Therefore, for the next few months, you will want to leverage other protections to ensure we protect your nights as intended.

Good news!

Historical Anchoring now protects every date across your — using the most recent same-day booking as an anchor, even if that booking is still in the future, relative to today.

For example:

And, for stay dates , if no comparable booking exists one year back, Wheelhouse extends the lookback up to two years to find an anchor.

Every time your account's Anchor source setting changes, Wheelhouse logs it — timestamp, user, and the old and new values — so you and your team always have a clear record of what changed and when.

Managing Historical Anchoring across a large portfolio just got easier:

Nothing changes for you today — every account, new or existing, defaults to , exactly like current behavior.

To try the new option:

📃 Help Center article — Historical Anchoring Source

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.