Booking Reviews Scraper — Hotels & Monitor
Pricing
from $0.80 / 1,000 booking.com reviews
Booking.com reviews scraper for hotel intelligence. Discover properties by name or destination, export scores, text, guest/stay/room data, photos and partner replies, filter by traveler/language/date/stay details, run summary-only benchmarks, and monitor only new reviews.
Booking.com hotel pages to scrape, one URL per line, e.g. https://www.booking.com/hotel/us/ace-new-york.html. Any Booking.com property page works (hotels, apartments, B&Bs). Leave empty when you use start URLs, hotel searches or discovery URLs below.
Maximum review rows returned (and billed) per hotel after filters, e.g. 200 (up to 5,000). Popular hotels have several thousand reviews on Booking.com.
Hard cap on review rows across all hotels in this run, e.g. 1000, for predictable runtime and spend.
Order in which Booking.com returns reviews: newest, most relevant, oldest, highest score or lowest score first (e.g. 'Lowest score first' to read complaints first). Uses Booking.com's own sort options. With 'Newest first' or 'Oldest first' and a reviewed date range, the Actor jumps straight to that period, so even a month several years back is reached in a few requests.
Optional. Same as hotel URLs, plus your own data per URL (userData, under Advanced in the editor), which is returned unchanged as customData on every row of that hotel, e.g. {"crmId": "H-1"}, to join the results with your CRM or sheet. Through the API you can also pass rows of a Booking.com hotel dataset that have a url or hotelUrl field.
[]Optional. Find hotels by name or destination on Booking.com, e.g. 'Ace Hotel New York' or 'hotels in Lisbon', then scrape reviews of the properties found (best effort; pasting hotel URLs is fastest).
[]Optional. Booking.com search or destination pages whose hotel links become review targets, e.g. https://www.booking.com/searchresults.html?ss=Lisbon (best effort: the links visible on the page are used).
[]Maximum number of hotels taken from hotel searches and discovery URLs together, e.g. 20.
Only return reviews scored at or above this value on Booking.com's 1-10 scale, e.g. 8 for happy guests.
Only return reviews scored at or below this value on Booking.com's 1-10 scale, e.g. 5 to collect complaints.
Only reviews written on or after this date: YYYY-MM-DD (e.g. 2026-01-01), ISO 8601, or a relative value counted back from the run start such as '7 days', '2 weeks' or '3 months' (ideal for schedules). With newest or oldest order the Actor jumps straight to the requested period.
Only reviews written on or before this date: YYYY-MM-DD (e.g. 2026-06-30), ISO 8601, or a relative value such as '30 days'. With newest or oldest order the Actor jumps straight to the requested period.
Only reviews written in these languages, e.g. en, it, de, fr. A code without region such as en includes all its variants (Booking.com's en, en-gb and xu = US English); a regional code such as en-us (or xu) or pt-br (or xb) includes only that variant. Empty means all languages.
[]Only these traveler types: COUPLES, SOLO_TRAVELLERS, FAMILIES, GROUP_OF_FRIENDS or BUSINESS_TRAVELLERS. Empty means all traveler types.
[]Only reviews from guests of these countries, as country codes or names, e.g. us, gb, Italy. Empty means all countries.
[]Only reviews whose title, positive or negative text contains this phrase (case-insensitive), e.g. breakfast. Filtered-out reviews are not billed.
Only reviews that at least this many readers marked as helpful, e.g. 1. 0 means no minimum.
Return any reviews, only reviews with a reply from the property, or only reviews without one, e.g. to find unanswered complaints.
Only reviews from stays that started (check-in) on or after this date: YYYY-MM-DD, e.g. 2026-06-01, or a relative value such as '6 months'.
Only reviews from stays that started (check-in) on or before this date: YYYY-MM-DD, e.g. 2026-08-31.
Only reviews from stays of at least this many nights, e.g. 3. 0 means no minimum.
Only reviews from stays of at most this many nights, e.g. 2 for short city breaks. Leave empty for no maximum.
Only reviews whose room type name contains this text (case-insensitive), e.g. suite or king.
Include the public photo URLs that guests attached to their reviews. Turn off for smaller rows; photoCount still says how many photos a review has.
Add one free hotel_summary row per hotel with the total review count, category sub-scores (staff, cleanliness, location, ...), score, language and traveler-type breakdowns from Booking.com, and the sort order applied.
Add one free review_insights row per hotel over the returned reviews: average score, hotel reply rate, score distribution, traveler types, languages, top guest countries, average nights and share of reviews with photos.
The guest's display name on each review. Turn off to collect reviews without guests' names (data minimisation, e.g. for GDPR); scores, texts, country, traveler type, stay details and hotel replies stay.
Return only hotel review counts and rating/filter aggregates, without review rows. Charged per hotel summary (event 'hotel-summary'). Useful for fast property benchmarking.
Name for a recurring review monitor, e.g. ace-hotel-weekly. Runs with the same name remember which reviews they already delivered and flag new ones with isNew.
With a monitor name, return (and bill) only reviews that earlier runs of the same monitor did not deliver. Reviews not delivered because of a spending limit come in the next run.
Safety ceiling on Booking.com review pages read per hotel (10 reviews per page), e.g. 100 pages = up to 1,000 reviews scanned. Selective filters may need more pages than reviews returned. With a reviewed date range and newest or oldest order, the Actor first jumps to that period and this is the number of pages it may read inside it.
Maximum seconds to load a hotel page in the browser, e.g. 60. Half of it (at least 30 s) is used to wait for Booking.com's review session to start.
Maximum seconds for each Booking.com review page request, e.g. 30. Raise it only on very slow connections.
How many times a hotel is retried in direct mode after a temporary browser or network failure, with growing pauses, e.g. 2. The proxy fallbacks get one try each.
Start direct for the lowest cost; if Booking.com blocks the session, retry through the Apify datacenter proxy (included in the price).
Last resort if Booking.com blocks both direct and datacenter access: retry the hotel once through a US residential proxy. Charged $0.10 per residential attempt (event 'residential-hotel'), before the attempt. Off by default.