Booking.com Reviews Scraper

What you get

Extract public guest reviews for Booking.com hotels, apartments, hostels, and resorts. Supply a property name, Booking.com hotel or review URL, URL slug, or numeric property ID. The Actor returns one structured dataset row per unique review, and you're billed only for the rows written. No Booking.com account or login is required.

Input

Field	Default	Description
queries	required	Property names, Booking.com URLs, slugs, or numeric hotel IDs.
maxResults	50	Maximum unique reviews per property, from 1 to 20,000.
sortBy	newest	Newest, oldest, most relevant, score high-to-low, or score low-to-high.
travelerType	all	Optional traveller-segment filter.
reviewLanguages	[]	Optional two-letter review-language codes.
onlyWithText	false	Exclude score-only ratings while continuing pagination.
keyword	empty	Booking.com's review-text relevance filter.
proxyConfiguration	Apify Residential, India	Pre-configured with a default that improves reliability when reading review pages. Custom proxies are supported; turning proxying off entirely can cause some runs to fail.

{
  "queries": [
    "Atlantis The Palm Dubai",
    "https://www.booking.com/hotel/gb/the-savoy-london.html",
    "280149"
  ],
  "maxResults": 100,
  "sortBy": "newest",
  "reviewLanguages": ["en"],
  "onlyWithText": true
}

Output

Each review can include:

• Stable review reference and public review/property URLs.
• Hotel ID, name, city, region, country, country code, coordinates, total review count, filtered review count, and category sub-scores for staff, facilities, cleanliness, comfort, value, location, and Wi-Fi.
• Review title, 1–10 score, positive text, negative text, combined text, original language, published timestamp, helpful votes, translation availability, and approval flag.
• Public reviewer display name, country, country code, avatar URL, and anonymity flag.
• Traveller type, room name and ID, check-in/out dates, nights, and stay status.
• Public property reply plus the largest available guest-photo URLs.
• Original input query and scrape timestamp.

Empty strings are normalized to null; numeric values are emitted as numbers. Duplicate review references are removed within pagination and again across duplicate input properties.

Empty and failure behavior

A property with genuinely zero reviews, or zero reviews matching your filters, finishes as a successful run with zero rows — the run log states why. When onlyWithText excludes every score-only review for a property, the log notes that too.

A temporarily unreachable page or a malformed response is retried automatically and does not count as "no reviews" — it is kept distinct from a true empty result. If every property in a run fails to load, the run itself is marked failed rather than returning an empty dataset silently. A property name that doesn't match anything on Booking.com is logged separately so you can tell a typo from a site with no reviews.

Limitations

• Booking.com does not publish a public API for reviews; this Actor reads the same public pages a visitor would see, and their structure, filters, or fields can change without notice.
• Review pages contain at most 25 cards per request. Large histories need many sequential, rate-limited requests and may finish partially if the run deadline is reached.
• Name lookup returns the first hotel match supplied by Booking.com. For ambiguous names, use a full Booking.com property URL or numeric ID.
• Bare numeric IDs can fetch reviews but do not reliably provide hotel name, city, country, coordinates, or a canonical slug because autocomplete is name-to-ID, not ID-to-name.
• The keyword option is Booking.com's relevance search, not a guaranteed literal substring filter.
• Review text stays in its original language. The feed indicates translatability but does not provide Booking.com's rendered machine translation.
• Reviewer names are limited to the public display name Booking.com exposes, often a first name. No contact details are collected.
• Guest photos and property replies are optional and absent from many reviews.
• This Actor covers reviews only. It does not return room rates, availability, inventory, or bookings.
• Proxy-free access is currently sufficient for moderate jobs, but Booking.com may rate-limit shared networks. A proxy can help with transport failures but does not guarantee access.

Responsible use

Only publicly visible review data is collected. The Actor does not authenticate, access bookings, or bypass a paywall. Review display names and countries can still be personal data; use, retain, and share them in accordance with Booking.com's terms and applicable privacy law.

Use cases

• Travel teams monitoring listings and reviews
• Analysts comparing destinations and operators
• Researchers building travel datasets

Related Actors

• Booking.com Hotel Scraper - Prices, Ratings & Amenities — Thirdwatch

Last verified: 2026-09

More scrapers at thirdwatch.dev.