Booking.com Reviews Scraper

Extract currently visible public Booking.com guest-review highlights for hotel, apartment, and other accommodation URLs. Each real result is one visible review card with the property score, reviewer details, and review text Booking.com exposes without sign-in.

Input

Example:

{
  "propertyUrls": ["https://www.booking.com/hotel/ca/fairmont-royal-york.en-gb.html"],
  "maxReviewsPerProperty": 10,
  "enableResidentialFallback": false
}

Output

Each successful row contains:

• propertyName, propertyUrl, reviewUrl, and rating
• positiveText, plus reviewTitle and negativeText when Booking.com exposes them
• reviewerName, reviewerCountry, and other visible fields when Booking.com displays them
• reviewKind (featured_public_review), transport (direct_browser, or <lane>_browser_fallback for a proxied retry), and scrapedAt

An empty input returns one clearly labelled sample row. A blocked, invalid, or empty target returns a diagnostic row. Neither is charged. Only genuine review rows call Actor.charge({ eventName: "review" }).

Proxy and Cost Control

The actor attempts direct Booking.com review-page HTTP first. When Booking renders only an empty static shell, it loads the public property page directly to read its visible featured review cards. It makes at most one proxied browser retry, only after a BLOCKED or RATE_LIMITED browser response, and only when enableResidentialFallback is enabled or you supplied your own proxy servers. That retry uses rotating Apify datacenter addresses (or your own servers); metered per-gigabyte groups such as RESIDENTIAL are never used, so proxy transfer never inflates the cost of a run. Keep review limits small while validating a target because browser compute is still billed per run.

Pricing

$1.50 per 1,000 reviews ($0.0015 each), with no run-start fee. Flat rate — no volume tiers, no plan gates — and you are charged only for reviews actually returned.

Sample rows, diagnostic rows, blocked pages and no-result runs are never charged, so a run that finds nothing costs nothing at all. Because there is no run-start fee, running one property per scheduled check costs exactly the same as batching ten properties into a single run.

Scope

This actor extracts public featured reviews displayed on Booking.com property pages. It does not bypass logins or CAPTCHAs, access private guest data, guarantee full historical pagination, or promise that Booking.com will preserve the current page markup.