TL;DR →
- We've added 4 new endpoint groups
- Market Datagives you access to data for your region. Markets are generally a broad area, incorporating data from many submarkets.
- Neighborhood Datagives you access to local pricing, occupancy, and booking pace for listings near you.
- Dynamic Sets Data: You can now get data from any Dynamic Set you have created on our platform.
- Last Posted Pricesurfaces the actual rate pushed to the OTA for each stay date — making it easy to reconcile recommendations vs. posted prices.
- All are available now via your existing RM API key. If you already have a key — no new authentication is required.
- Need an RM API key? Just message us at: hello@usewheelhouse.com
Revenue Manager API Overview
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!
🏘️ Neighborhood Data
Two new endpoints give your integration a daily view of what's happening around each listing:
- GET /listings/{listing_id}/neighborhood_pricing- daily neighborhood pricing data
- GET /listings/{listing_id}/neighborhood_occupancy- daily neighborhood occupancy and booking data
What this unlocks:
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:
- Surfacing comp-set context in your own dashboards or owner reports
- Building alerting logic when your listings are moving against neighborhood trends
- Feeding neighborhood signals into your own revenue models alongside Wheelhouse's recommendations
Each endpoint is scoped to a single listing and returns day-level data, so you can pull exactly the window you need.
🗂️ Dynamic Sets
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:
- GET List all dynamic sets
- GET Get a single dynamic set
- GET Get aggregated metrics for a dynamic set
- GET Get the report of a dynamic set
- GET List the listings in a dynamic set
- GET List the user listings associated with a dynamic set
- PUT Associate your user listings with a dynamic set
- DELETE Remove associated user listings from a dynamic set
- GET Get the changelog of a dynamic set
What this unlocks:
Dynamic Sets are how Wheelhouse models local market context for each listing. With these endpoints, you can:
- Pull aggregated performance metrics for any comp set and display them alongside your own reporting
- Associate (and disassociate) your managed listings with specific dynamic sets programmatically — useful for onboarding automation or portfolio restructuring
- Track the changelog for a dynamic set to understand when and how comp group membership has changed over time
- Retrieve the full report for a dynamic set to feed into your own analytics
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.
📊 Market Reports
Three endpoints give your integration access to Wheelhouse's market-level data:
- GET /market_report— list all markets (for a country) where you have at least one Pro tier listing, including geographic boundaries and postal codes
- GET /market_report/{market_id}/time_series— daily time-series data for any combination of 9 market metrics over a date range
- GET /market_report/{market_id}/distribution— histogram distributions for market metrics, broken down by calendar month
Available metrics:
- asking_rate_w_feesAverage asking rate including fees
- adr_w_feesAverage daily rate of booked rooms including fees
- occupancyOccupancy rate across all nights
- occupancy_adjustedOccupancy rate over open (non-blocked) nights
- revpar_w_feesRevPar including fees
- revpar_adjusted_w_feesRevPar over open available room-nights including fees
- revenue_w_feesTotal revenue including fees
- lead_time Averagebooking lead time in days
- nights_bookableOpen available room-nights
- length_of_staydistribution endpoint only
Filtering:
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.
What this unlocks:
This is the most data-dense addition in this release.
A few things you can build with it:
- Market benchmarking dashboards— pull RevPar, ADR, and occupancy time-series for your markets and display them alongside your portfolio KPIs
- Demand forecasting inputs— feed lead time and occupancy trends into your own models to anticipate soft or strong periods.
- Owner reporting— show how a listing's performance compares to the distribution of the broader market for that month, filtered to comparable properties (same bedroom count, property type)
- Competitive ADR analysis— track asking rate trends in your markets over time, sliced by bedroom count or property type, to validate your pricing strategy
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.
📌 Last Posted Price
A single new endpoint under the Calendar tag:
- GET /listings/{listing_id}/last_posted_prices— returns the last price posted to the OTA per stay date
What this unlocks:
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
🥳 Pro Tip!
Pair this with the existing Price Recommendations endpoint (GET
/listings/{listing_id}/price_recommendations
) to calculate the delta between recommended and posted prices — a useful signal for auditing override behavior or channel sync issues across your portfolio.🚀 Getting Started
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.