Vrbo Availability Calendar Scraper - Occupancy & Prices

Vrbo Availability Calendar Scraper returns a Vrbo vacation rental's calendar day by day for up to 24 months: whether each date is available, whether you can check in or check out that day (and why not), and the minimum and maximum stay. Turn on Include nightly prices to add Vrbo's nightly date-picker price to every date. Paste Vrbo URLs or property ids; URLs are resolved once and the property id is cached for later runs. Use it to estimate occupancy and revenue, track booking pace and seasonality, or monitor competing short-term rentals. Pricing is pay-per-event: $0.006 per calendar, $0.012 with prices, and $0.042 the first time a URL is looked up; failed requests are not charged.

Proxies, retries and anti-bot handling are built in, so you don't need your own proxies or an API key. Start a run, get structured JSON.

What can this Vrbo scraper do?

• Day-by-day availability for 1-24 months per rental.
• Check-in / check-out rules per date with the reason (minimum notice, not available, ...).
• Minimum and maximum stay per check-in date, plus the rental's defaults.
• Nightly prices (optional): Vrbo's date-picker price on every date.
• URL or id input: URLs are resolved once, then the property id is cached in your key-value store.
• Summary per rental: available, check-in and check-out days.

Use cases for Vrbo data

• Short-term-rental investors: Estimate occupancy and revenue for comparable Vrbo homes.
• Property managers: Track competitors' booking pace, minimum stays and nightly prices.
• Market analysts: Measure seasonality and booked-out periods across a destination.

What Vrbo data can you extract?

Field	Description
calendar[].date / available	Availability per date
calendar[].checkin_allowed / checkin_rule	Whether a stay can start that day, and why not
calendar[].checkout_allowed / checkout_rule	Whether a stay can end that day
calendar[].min_stay / max_stay	Stay limits for a check-in on that date
calendar[].price	Nightly price (with Include nightly prices)
property	Property id, listing id, calendar range, default min/max stay, stay increment
summary	Days, available, unavailable, check-in and check-out days

Every dataset item also carries input (the exact request that was sent), request_id (quote it to support), billed and scraped_at.

How to scrape Vrbo availability calendars

1. Open Vrbo Availability Calendar Scraper in Apify Console and go to the Input tab.
2. Enter Vrbo listings, one per line: a Vrbo URL (https://www.vrbo.com/20218736ha), its URL id (20218736ha) or a property id from Vrbo search. Choose how many Months to return and whether to Include nightly prices.
3. Adjust the options if needed. Dates accept an exact date (2026-12-01) or a relative one (30 days from today), so saved tasks and schedules never go stale.
4. Click Start and wait for the run to finish.
5. Download the results from the Output tab as JSON, CSV, Excel or HTML, or fetch them with the Apify API.

Input example

This is the default input; running the Actor without changes uses it.

{
  "listings": [
    "122942416"
  ],
  "months": 12,
  "include_prices": false,
  "cacheListingIds": true,
  "includeErrors": true,
  "maxConcurrency": 3,
  "maxRetries": 2
}

Output example

One dataset item per request (trimmed here; real items contain every field the API returns):

{
  "endpoint": "/v1/ota/vrbo/calendar",
  "input": {
    "property_id": "122942416",
    "months": 12
  },
  "calendar": [
    {
      "available": true,
      "checkin_allowed": false,
      "checkin_rule": "min_prior_notification",
      "checkout_allowed": true,
      "checkout_rule": "valid",
      "date": "2026-10-20",
      "max_stay": 357,
      "min_stay": 2
    },
    {
      "available": true,
      "checkin_allowed": true,
      "checkin_rule": "valid",
      "checkout_allowed": true,
      "checkout_rule": "valid",
      "date": "2026-10-21",
      "max_stay": 356,
      "min_stay": 2
    },
    {
      "available": false,
      "checkin_allowed": false,
      "checkin_rule": "not_available",
      "checkout_allowed": true,
      "checkout_rule": "valid",
      "date": "2027-10-15",
      "max_stay": 0,
      "min_stay": 1
    }
  ],
  "meta": {
    "cached": false,
    "collection_id": "ratecol_0123456789abcdef0123456789abcdef",
    "elapsed_s": 0.66,
    "listing_resolved": false,
    "market": "US",
    "observed_at": "2026-08-07T01:23:45.678Z",
    "priced": false,
    "source": "vrbo",
    "upstream_elapsed_s": 0.62
  },
  "property": {
    "available_by_default": false,
    "calendar_end": "2027-10-19",
    "calendar_start": "2026-10-20",
    "default_max_stay": 999,
    "default_min_stay": 1,
    "listing_id": null,
    "property_id": "122942416",
    "stay_increment_days": 1
  },
  "search_parameters": {
    "end_date": "2027-10-19",
    "engine": "vrbo_calendar",
    "include_prices": false,
    "market": "US",
    "months": 12,
    "property_id": "122942416",
    "start_date": "2026-10-20"
  },
  "summary": {
    "available_days": 357,
    "checkin_days": 353,
    "checkout_days": 365,
    "days": 365,
    "unavailable_days": 8
  },
  "request_id": "req_3f9c0d6e2b8a4c1f9e7d5b3a1c0e8f6d",
  "billed": true,
  "scraped_at": "2026-10-01T14:03:27.512Z"
}

A request that fails is saved with an error message instead (turn off Include failed requests to skip those). Failed requests are never charged.

How much does it cost to scrape Vrbo availability calendars?

This Actor uses pay-per-event pricing: you pay for successful API requests, not for compute time.

Event	Charged when	Price	Per 1,000
calendar	One rental's day-by-day availability, check-in/check-out rules and minimum/maximum stay for up to 12 months.	$0.006	$6.00
priced-calendar	A calendar with Vrbo's nightly date-picker price on each date, or one longer than 12 months (up to 24).	$0.012	$12.00
listing-lookup	Added once when a Vrbo URL or URL id had to be resolved to its property id by loading the listing page. Resolved ids are cached, so later runs skip it.	$0.036	$36.00

For example, 1,000 twelve-month calendars cost $6.00; with nightly prices $12.00. The first run on 1,000 Vrbo URLs adds a one-time $36.00 lookup ($0.042 per rental in total); later runs on the same URLs use the cached property ids and cost $6.00.

• Failed requests (errors, invalid input, blocked upstream after retries) are free.
• Requests where the source returns nothing at all (no results, nothing priced) are saved but not charged.
• Set Maximum cost per run when you start a run and the Actor stops cleanly before going over it.

FAQ

Do I need proxies or an API key?

No. Proxy rotation, retries and anti-bot handling are built in, and the Actor is ready to run as is. You only pay the per-event prices above.

How am I charged?

One calendar event ($0.006) per rental calendar of up to 12 months, or one priced-calendar event ($0.012) with nightly prices or more than 12 months. A URL or URL id that has to be resolved adds one listing-lookup event ($0.036) the first time. Failed requests are never charged.

Why use property ids?

A property id goes straight to the calendar. A URL needs one extra listing-page load to find the property id, so it is charged once; the Actor then stores the id in your vrbo-listing-ids key-value store and reuses it on later runs.

Are the nightly prices booking quotes?

No. They are the indicative prices Vrbo shows in its date picker. For the exact price of a stay with fees, use the Vrbo Scraper.

How do I estimate occupancy?

Compare unavailable dates between runs: dates that turn unavailable over time were most likely booked. Schedule the Actor daily or weekly.

Is it legal to scrape Vrbo availability calendars?

The Actor collects publicly available information that anyone can see without logging in. You are responsible for how you use the results: respect the source site's terms, copyright and privacy law (such as GDPR) and do not collect personal data without a lawful basis. If in doubt, ask a lawyer.

What happens when a request is blocked or rate-limited?

Rate limits (HTTP 429) and temporary errors (5xx) are retried automatically with exponential backoff, respecting Retry-After. If a request still fails it is saved with the error message and not charged, and the rest of the batch keeps going. A run only fails when every request failed.

Why did a request return an error?

Read the error field: validation problems (for example a malformed date or an unknown id) are reported exactly as the API sees them. Fix the input and run again; failed requests cost nothing.

How many requests can I run at once?

Any number per run. The Actor sends up to 3 requests in parallel by default (change it under Run options); larger batches simply take longer.

Use it from your code

Call the Actor from any language through the Apify API. With the JavaScript client (npm install apify-client):

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('scrapercompany/vrbo-availability-calendar-scraper').call({
    "listings": [
        "122942416"
    ]
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

With Python (pip install apify-client):

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("scrapercompany/vrbo-availability-calendar-scraper").call(run_input={
    "listings": ["122942416"],
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

You can also schedule runs, chain them with webhooks, or connect them to Make, Zapier, n8n, Google Sheets and other integrations from the Integrations tab.

Related scrapers

• Vrbo Scraper: quotes with fees, and destination search
• Airbnb Availability Calendar Scraper: the same calendar data for Airbnb listings
• Airbnb Scraper: Airbnb listings and prices for a location

Support

Questions, a field you need, or a site that stopped working? Open an issue on the Issues tab. Include the request_id from the dataset item so we can trace the request.