VRBO Occupancy Scraper — Calendar, Occupancy & Booking Pace

Disclaimer: Unofficial tool for publicly accessible VRBO listing calendars. VRBO is a trademark of HomeAway.com, Inc. / Expedia Group. Not affiliated with, sponsored by, or endorsed by VRBO or Expedia Group. For informational, research, revenue-management, and market-analysis use only. Respect applicable terms of use and law.

VRBO occupancy scraper for the public availability calendar — a practical VRBO calendar scraper, VRBO availability scraper, and VRBO API alternative. Paste listing URLs or IDs, a search URL, or a location. Export occupancy % (30 / 60 / 90 / 365 days), sold-out nights, ADR, min-stay, optional nightly prices, and booking-pace deltas as a JSON dataset. Call from Python, Node.js, cURL, or Apify MCP / AI assistants.

Built for STR revenue managers, vacation-rental investors, comp-set tracking, and short-term rental market research. No VRBO account required.

VRBO occupancy (STR calendars)	Airbnb occupancy (STR calendars)	Idealista (long-term ES/IT/PT)
VRBO Occupancy Scraper ◄── you are here	Airbnb Occupancy Scraper	Idealista Scraper

When to use this Actor

• You need a VRBO occupancy monitor / VRBO occupancy scraper that returns structured JSON
• You already know listing IDs (portfolio / comp set) or have a city search URL
• You want occupancy %, sold-out nights, ADR, min-stay, and booking pace — not a generic listing dump
• You want to scrape VRBO calendars with Python, Node.js, or MCP and export a dataset

When not to use this Actor

• Historical occupancy — VRBO only exposes a forward rate calendar (about 12 months; this Actor requests up to 730 days)
• Guaranteed booked vs owner-blocked — the public calendar cannot tell them apart; this Actor labels that honestly
• Guest PII, messages, host emails, or full review dumps — public calendar and listing fields only
• Whole-market 10k-listing crawls in one run — cap with maxListings and schedule by neighborhood
• Airbnb occupancy — use Airbnb Occupancy Scraper

Key Features

• Listing URLs or dual IDs — vrbo.com/2165911, 4193579ha, and expediaPropertyId= query ids
• Search / location discovery — paste a VRBO search URL or type Austin, TX to take the first search page, then pull calendars
• Forward calendar — available / sold-out, check-in / check-out validity, per-date min-stay, nightly price when published
• Occupancy windows — 30 / 60 / 90 / 365-day unavailable rates plus horizon totals
• ADR / RevPAR from available nights — never interpolated; priced nights only
• Booking pace — schedule the Actor with monitor: true and a stable monitorStoreName (named Key-Value store). First run is the baseline; later runs emit newly unavailable / newly available nights
• Honest metrics — unavailableRate and occupancyEstimate are the same calendar signal, with an explicit host-block caveat
• HTTP + Chromium fallback — listing HTML via Chrome TLS impersonation; calendar GraphQL and search pages use headless Chromium when Akamai blocks raw POST
• Apify Proxy ready — US residential recommended on the platform
• MCP / AI ready — call from assistants via Apify MCP

Use Cases

Use case	What you get
Comp-set occupancy	Forward sold-out % for rival VRBO listings in your market
Booking pace	Nights that flipped unavailable (or opened) since the last scheduled run
ADR / rate calendar	Nightly prices on open nights plus min / max / ADR
Min-stay intelligence	Most common minimum-night rule across the horizon
Investment screening	Occupancy windows + rating / sleeps / bedrooms from the public listing page
OTA suite	Same occupancy schema as Airbnb occupancy for STR / revenue buyers

Quick Start

Known listings:

{
  "listings": ["https://www.vrbo.com/2165911", "4193579ha"],
  "lookAheadDays": 365,
  "includeCalendar": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "US"
  }
}

City search (first page of listings, then calendars):

{
  "location": "Austin, TX",
  "lookAheadDays": 90,
  "maxListings": 20,
  "includeListingDetails": true
}

Scheduled booking-pace monitor:

{
  "listings": ["https://www.vrbo.com/2165911"],
  "lookAheadDays": 365,
  "monitor": true,
  "monitorStoreName": "vrbo-occupancy-monitor",
  "includeCalendar": false
}

Input Parameters

Parameter	Type	Default	Description
listings	Array	—	Property URLs or IDs (path id, ha suffix, Expedia id in the URL)
startUrls	Array	—	Property URLs and/or VRBO search URLs
location	String	—	City / area used to build a search URL
lookAheadDays	Integer	365	Forward nights (1–730)
maxListings	Integer	50	Cap (0 = unlimited)
adults	Integer	2	Guest count on the listing page
includeListingDetails	Boolean	true	Title, location, rating, capacity
includeCalendar	Boolean	true	Per-day calendar[] array
monitor	Boolean	false	Booking-pace vs previous run (needs named store)
monitorStoreName	String	vrbo-occupancy-monitor	Named KV store for pace snapshots
currency	String	USD	ISO code
proxyConfiguration	Object	US residential	Strongly recommended on Apify

Output Format

Each dataset item is one listing (or an error row if that listing failed) — not one row per night.

Field	Type	Description
vrboId	String	Path id from vrbo.com/{id}
expediaPropertyId	String	Internal id used by the rate calendar
listingUrl	String	Canonical listing URL
title	String	Listing title
city / region / countryCode	String	Location when exposed
rating / reviewsCount	Number / Integer	Public review stats (VRBO scale is typically 10)
sleeps / bedrooms / beds / bathrooms	Number	Capacity when exposed
unavailableRate	Number	Unavailable ÷ counted nights in the 365-day window (same as occupancy365d)
occupancyEstimate	Number	Same value; labeled as an estimate
occupancy30d / 60d / 90d / 365d	Number	Windowed unavailable rates
availableDays / unavailableDays / soldOutDays	Integer	Horizon counts
firstAvailableDate	String	Nearest open night
minNightsMode	Integer	Most common min-stay
adr / estimatedRevenue / revpar	Number	ADR from available priced nights only
bookingPace	Object	Present when monitor is on
calendar	Array	Per-day availability (optional)
occupancyNote	String	Host-block caveat
scrapedAt	String	ISO timestamp

Example row:

{
  "type": "listing",
  "source": "vrbo",
  "vrboId": "2165911",
  "expediaPropertyId": "63066336",
  "listingUrl": "https://www.vrbo.com/2165911?expediaPropertyId=63066336",
  "title": "Piccolo Ponte 3 BR Caribbean Villa. Pool & Hot Tub. Canal front, SUP, Bikes.",
  "city": "Leeward Settlement",
  "unavailableRate": 0.4123,
  "occupancyEstimate": 0.4123,
  "occupancy30d": 0.7,
  "occupancy90d": 0.4556,
  "availableDays": 215,
  "unavailableDays": 150,
  "firstAvailableDate": "2026-09-04",
  "minNightsMode": 3,
  "adr": 1094.0,
  "currency": "USD"
}

How occupancy is calculated

VRBO’s public rate calendar marks a night available or unavailable. An unavailable night can be a guest booking or a host calendar block. This Actor reports unavailableRate and occupancyEstimate as that share of upcoming nights, with occupancyNote on every row. It does not invent a booking-only occupancy figure. When the calendar is longer than 365 days, unavailableRate matches occupancy365d (not the full dump length). Nights without an availability flag are skipped rather than counted as 0% occupancy.

ADR is the average of real prices on available nights. Missing or blocked nights are not interpolated.

Integration examples

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('crawloop/vrbo-occupancy-scraper').call({
  listings: ['https://www.vrbo.com/2165911'],
  lookAheadDays: 365,
  proxyConfiguration: {
    useApifyProxy: true,
    apifyProxyGroups: ['RESIDENTIAL'],
    apifyProxyCountry: 'US',
  },
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]?.unavailableRate, items[0]?.occupancy90d, items[0]?.adr);

Python

from apify_client import ApifyClient

client = ApifyClient(token)
run = client.actor("crawloop/vrbo-occupancy-scraper").call(
    run_input={
        "listings": ["https://www.vrbo.com/2165911"],
        "lookAheadDays": 365,
        "proxyConfiguration": {
            "useApifyProxy": True,
            "apifyProxyGroups": ["RESIDENTIAL"],
            "apifyProxyCountry": "US",
        },
    }
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item.get("vrboId"), item.get("unavailableRate"), item.get("adr"))

cURL

curl "https://api.apify.com/v2/acts/crawloop~vrbo-occupancy-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"listings":["https://www.vrbo.com/2165911"],"lookAheadDays":365}'

MCP and AI assistants

Use this Actor from AI tools via Apify MCP. Connect your Apify account, then call crawloop/vrbo-occupancy-scraper.

Example prompts:

• "Run VRBO Occupancy Scraper for https://www.vrbo.com/2165911 with 365 look-ahead days and return unavailableRate, occupancy30d, occupancy90d, soldOutDays, adr"
• "Scrape VRBO occupancy for listings in Austin, TX, max 15, and summarize 90-day sold-out rates as JSON"
• "Chain VRBO Occupancy Scraper then Airbnb Occupancy Scraper for the same city to compare OTA occupancy and ADR"

FAQ

Is this an official VRBO API?
No. It reads the same public GraphQL rate calendar the website uses and returns structured dataset rows — a practical VRBO API alternative for pipelines.

VRBO occupancy scraper vs a VRBO listings scraper?
This Actor is calendar-first: occupancy %, sold-out nights, nightly rates, ADR, and booking pace. It is not a dump of search cards, reviews, or host emails.

Do I need a VRBO login?
No — public calendars and listing pages only.

Can I scrape VRBO occupancy with Python or Node.js?
Yes — use the Apify client examples above, or call the Actor from cURL / Apify MCP.

Why residential proxy?
VRBO is Akamai-protected and often challenges datacenter IPs. Residential (US) is the reliable default on the platform.

Is occupancy the same as booked nights?
No. Treat occupancyEstimate as unavailable share, including host blocks. That is the same limitation every calendar-based STR tool has.

Can I get historical occupancy?
No. The calendar is forward-only. Schedule the Actor to build your own history.

What IDs does VRBO use?
A listing URL can carry a path id (2165911 / 4193579ha) and an expediaPropertyId. This Actor stores both. The calendar GraphQL is keyed by the Expedia id.

How many listings per search?
A location / search URL contributes the first results page. Pass explicit listings for a known portfolio.

Related Actors

Actor	Focus
VRBO Occupancy Scraper ◄── you are here	STR calendars, occupancy %, ADR, booking pace
Airbnb Occupancy Scraper	Airbnb STR calendars, occupancy %, booking pace
Idealista Scraper	Long-term rental / sale listings (ES/IT/PT)

Suite next step: after VRBO occupancy snapshots, run Airbnb Occupancy Scraper for the same destination’s Airbnb calendars, then Idealista Scraper when you need long-term comps.