Vrbo Vacation Rentals Scraper 🏖️

Extract vacation rental listings, prices, availability signals, amenities, photos, geo, ratings and full guest reviews from vrbo.com, by location, region, coordinates, property URL, or property ID.

You get clean, structured records that are fast, reliable, and inexpensive to run.

---

✨ Why this scraper

	This Actor	Basic scrapers
Input forms	Location, region ID, coordinates, property URL, bare ID, dotted ID, /reviews link, search URL	URL or location only
Reviews	Full paginated guest reviews, manager responses, category ratings	Limited or none
Output	40+ fields incl. sleeps, bedrooms, bathrooms, property type, badges, geo	Title and price only
Reliability	Keeps working through Vrbo site updates and recovers automatically from blocks	Often stop returning results
Proxy spend	Residential-first proxy handling with fallback guidance	Residential always on

---

🔑 Input

Run in Search mode (by location) or URL mode (by specific properties or search URLs). Everything is optional except the stay dates, which default sensibly.

Search mode

Field	Description
destination	Location text, e.g. Orlando, Florida, Bali, Tulum Mexico
destinationId	Optional region ID to pin an exact region
latitude / longitude	Search by coordinates instead of a name
checkIn / checkOut	Date or relative value (1 day, 30 days). Drives nightly pricing
adults, children, rooms	Guest configuration
bedrooms	Minimum bedrooms filter
minPrice / maxPrice	Nightly price range
sortBy	RECOMMENDED, PRICE_LOW_TO_HIGH, PRICE_HIGH_TO_LOW, DISTANCE, REVIEW

URL mode

Paste any mix into startUrls:

• Full property URL, e.g. https://www.vrbo.com/2165911
• Bare ID, e.g. 2165911
• Dotted ID, e.g. 321.2880733.3452770
• Reviews link, e.g. https://www.vrbo.com/2165911/reviews
• Search URL, e.g. https://www.vrbo.com/search?destination=Bali

Reviews and output options

Field	Description
reviewsOnly	Output one row per review instead of property cards
includeReviews	Embed up to N reviews inside each property card
maxReviewsPerProperty	Cap reviews per property
reviewsFrom	Only keep reviews on or after YYYY-MM-DD
includeCategoryRatings	Attach cleanliness, communication, location and accuracy scores
currency, locale	Output currency and language
maxItems	Hard cap on total records
proxy	Proxy configuration (Residential recommended)

Resume & recurring updates

Field	Description
resumeFromRunId	Paste a previous run ID or dataset ID to continue an interrupted crawl — properties already saved there are skipped, so this run only fetches new ones.
incrementalMode	Off by default. Turn on for scheduled/recurring runs of the same search: the Actor remembers the previous run itself and classifies every property as NEW, UPDATED, UNCHANGED, REAPPEARED, or EXPIRED.
stateKey	Only used with Incremental mode. Name this monitoring campaign so it keeps its own baseline; leave empty to derive one automatically from your search/URL and stay settings (destination/URLs, dates, guests, filters, sort, currency/locale, review options). Raising maxItems or maxReviewsPerProperty never starts a new baseline.
emitUnchanged	Off by default. When off, UNCHANGED properties are skipped and not billed. Turn on to also return (and pay for) every unchanged property.
emitExpired	Off by default. When on, a previously-tracked property missing from a complete, uncapped scan is returned once (and billed) as an EXPIRED tombstone with its last known data. Skipped automatically whenever the scan was capped, resumed, or otherwise incomplete.

These two features are independent and can be combined: resumeFromRunId finishes one interrupted crawl; incrementalMode is for recurring monitoring of the same search. Note: reviews embedded via includeReviews never affect NEW/UPDATED/UNCHANGED classification — reordered or newly-added reviews alone never make a property look changed. A field that goes from unobserved (null) to populated, or back, is also never classified as an update on its own (only a value-to-different-value change is) — Vrbo occasionally answers the same property through a leaner or fuller response path, and that must not look like the listing itself changed. title is excluded from classification entirely for the same reason: it is fetched via two different underlying paths that can render different headline copy for the same property (confirmed live, e.g. "Recently Remodeled Studio Condo in the Heart of Aspen" vs "Remodeled studio in city centre Aspen" for the same listing) — a real title edit by the host will still appear in the output field, it just never drives changeType.

---

📤 Output

Property record (Search / URL mode)

{
  "mode": "search",
  "vrboId": "2165911",
  "listingUrl": "https://www.vrbo.com/2165911",
  "title": "Beachfront Villa with Private Pool",
  "propertyType": "Villa",
  "sleeps": 8,
  "bedrooms": 4,
  "bathrooms": 3,
  "pricePerNight": 412,
  "priceFormatted": "$412 nightly",
  "priceStrikeout": "$520",
  "priceCurrency": "USD",
  "rating": 9.8,
  "ratingScale": 10,
  "ratingLabel": "Exceptional",
  "reviewCount": 137,
  "latitude": -8.6887,
  "longitude": 115.1700,
  "image": "https://...",
  "images": ["https://...", "https://..."],
  "imagesCount": 24,
  "badges": ["Great location"],
  "description": "Completely renovated beachfront villa...",
  "provider": "vrbo",
  "searchLocation": "Bali",
  "checkIn": "2026-07-15",
  "checkOut": "2026-07-20",
  "adults": 2,
  "scrapedAt": "2026-06-13T10:00:00Z",
  "changeType": "UPDATED",
  "changedFields": ["pricePerNight", "priceFormatted"],
  "firstSeenAt": "2026-06-01T10:00:00Z",
  "lastSeenAt": "2026-06-13T10:00:00Z"
}

changeType, changedFields, firstSeenAt, and lastSeenAt are only present when incrementalMode is on.

Review record (reviewsOnly or /reviews link)

{
  "mode": "reviews",
  "vrboId": "2165911",
  "reviewId": "abc123",
  "rating": 10,
  "ratingScale": 10,
  "ratingLabel": "Excellent",
  "reviewTitle": "Perfect family getaway",
  "reviewText": "The villa exceeded our expectations...",
  "authorName": "Sarah M.",
  "reviewDate": "2026-05-02",
  "stayDuration": "Stayed 5 nights in April 2026",
  "liked": ["Cleanliness", "Location"],
  "disliked": [],
  "managerResponse": { "text": "Thank you Sarah!", "author": "Host", "date": "2026-05-03" },
  "photos": ["https://..."],
  "categoryRatings": { "Cleanliness": 10, "Communication": 9.8, "Location": 10 },
  "propertyReviewCount": 137,
  "provider": "vrbo",
  "scrapedAt": "2026-06-13T10:00:00Z"
}

Detail and URL-mode records add address, city, country, postalCode, neighborhood, amenities, amenitiesCount, and categoryRatings where available.

---

💸 Pricing

You are charged a small property-detail event only when fetching a specific property by URL or ID in URL mode. Location-search property cards and review rows are not charged that event. You also pay your own Apify platform compute and proxy usage.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape, and the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record, not the full JSON. Each item becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.