Booking.com Scraper: Hotel Prices & Reviews

Scrape Booking.com hotel listings for any destination: price per night, star rating, review score and count, distance from the centre and preferred badges — the same data its own search results page shows, with no login and no captcha-solving.

What you can do with it

• Compare prices across destinations: run several cities at once and rank hotels by price per night.
• Track rate changes: run it daily for the same destination and dates to see prices move.
• Shortlist by reputation: filter on review score, review count and star rating before opening a single listing.
• Feed a travel comparison site or alert: Booking.com has no public export for third parties; this Actor reads the same listings its own search page shows.

Input

Field	What it does
Destinations	One or more city or place names, exactly as typed into Booking.com's own search box (for example Paris or New York). Defaults to five major cities worldwide.
Check-in, days from today	How many days from now the stay starts (default 30; a date too close to today has little availability left).
Length of stay (nights)	Number of nights for the search (default 2).
Adults	Number of adult guests for the search (default 2).
Maximum number of hotels	The run stops once this many hotels are saved, across all destinations combined (default 50).

Output

One record per hotel:

{
  "id": "fr/virgina",
  "url": "https://www.booking.com/hotel/fr/virgina.html",
  "title": "Virgina",
  "stars": 3,
  "address": "14th arr., Paris",
  "distanceFromCentre": "4 km from downtown",
  "reviewScore": 8.6,
  "reviewWord": "Excellent",
  "reviewCount": 2602,
  "price": 195,
  "currencySymbol": "€",
  "priceNote": "Includes taxes and fees",
  "isPreferred": false,
  "isGuestFavourite": false,
  "imageUrl": "https://cf.bstatic.com/xdata/images/hotel/square240/587081003.jpg",
  "searchDestination": "Paris"
}

Export the dataset as JSON, CSV or Excel, or read it through the Apify API.

Why this one

• Covers several destinations in one run. Pass a list of cities and get a single combined dataset instead of running one Actor per city.
• No login, no captcha-solving. Booking.com's bot defenses are handled with a real, stealth browser behind residential IPs; nothing about the site's defenses is bypassed by a fake account or solved challenge.
• Review score, word and count in one field each, parsed straight from the same rating badge shown on the search page, not re-derived or estimated.

Good to know

• price is the total shown on the search card for the chosen stay and number of adults, in the currency Booking.com itself displays for that search; it is not a nightly average.
• priceNote carries the card's own wording about taxes and fees (for example "Includes taxes and fees"); read it before comparing prices across hotels, since not every listing includes them the same way.
• Booking.com protects its pages with a JavaScript challenge: this Actor is slower and costs more per result than a simple HTML scraper, because every search needs a full residential-IP browser session, not just a plain HTTP request.
• A destination with little availability for the chosen dates may return fewer than 25 hotels; try a later check-in date or a bigger city.

FAQ

Can I search a specific neighbourhood or a single hotel?
Use the same text you would type into Booking.com's own search box as a destination — it accepts neighbourhoods and landmarks, not just city names.

Why is it more expensive than most hotel scrapers?
Booking.com requires a full browser session behind a residential IP for every search; this costs more per request than a typical site that works with a plain HTTP request.

Does it include private-room or apartment listings?
Yes, whatever Booking.com's own search for that destination and dates returns is included; no personal host or guest data is collected, only the listing's own public price and rating.