VRBO Vacation Rentals Scraper
Under maintenancePricing
Pay per event
Scrape VRBO (Expedia Group) vacation-rental search results and listing details by destination: title, location, price per night, beds/baths, guests, rating, reviews, amenities, host, and coordinates. Camoufox-powered to clear anti-bot challenges. Pay only per listing scraped.
Fixes two cloud-QA blockers found after the initial Camoufox build:
![VRBO Scraper — Properties + Calendar + Full Reviews [$2.5💰] avatar](https://images.apifyusercontent.com/GjYEFnGAoN4h98SQVX5_-16p4UJ22WTlYPlZvYf0T8c/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vbmduOHZSRVNUa3NleVdFNnAtYWN0b3ItMk5jcGRpZ2VTOU5mOE91U28tamRMQkNsTlV6Vy1WUkJPX2FwcC53ZWJw.webp){kind=avatar}
RESIDENTIAL proxy pool is Akamai-flagged
for vrbo.com (429 "Bot or Not?" challenge, confirmed via cloud QA).
resolve_proxy now prefers a WEBSHARE_PROXY_URL env var (parsed
into the same Playwright-shaped proxy dict) when set, falling back to
the original Apify RESIDENTIAL → BUYPROXIES94952 resolution
otherwise. WEBSHARE_PROXY_URL must be set as an Actor env var /
secret in Apify Console for cloud runs — it is not forwarded from
local .env.DeferredSearchResults
GraphQL response (~1.7MB) wasn't reliably landing inside the previous
fixed 6s post-load wait — cloud QA captured a 133-char mid-load body
("Searching thousands of properties"). Replaced the blind
page.wait_for_timeout(...) with wait_for_search_results, which
polls for either a captured GraphQL response or the results-card DOM
selector, capped at a 25s timeout, before falling through to the
existing GraphQL-first/DOM-fallback extraction.docs/specs/vrbo-vacation-rentals-scraper/tasks.md for the build
order (T04 Camoufox infra proof is the next hard gate).