Booking.com Hotel Listings & Reviews Scraper

What this Actor scrapes

For each run, this Actor works in one of two modes:

1. Search mode — pass a destination (plus check-in/check-out dates), and it opens Booking.com's search results for that window, capped at your maxHotelsPerSearch. 2. Direct-URL mode — pass a list of hotelUrls, and it visits each hotel's own detail page directly, independent of a destination search.

What we handle for you

• We clear the JS-execution gate Booking.com puts in front of raw HTTP requests — a hardened browser layer renders the page like a real visitor instead of bouncing off an automated bot-control challenge screen.
• We rotate proxy sessions on every block — a fresh exit IP and session id whenever a challenge or mismatch is detected.
• We verify the currency and locale actually match what you asked for before trusting a price — a wrong-geo page never gets emitted as if it were correct.
• We back off when the target pushes back. Partial successes surface with a clear status message — we never silently return an empty dataset.
• Per-hotel fault isolation — one dead page, timeout, or parse error skips that hotel with a logged warning; it never fails the whole run.
• Pydantic v2 input + output validation — every row is a typed, schema-enforced record; nullable fields are always null, never silently dropped.
• Pay-Per-Event pricing — you're charged per hotel row written to your dataset, plus a small per-review charge only when you opt into reviews.

Use cases

• OTA price intelligence — track how a set of hotels prices a given date range across markets.
• Revenue-management benchmarking — hotel revenue managers pull comparable listings to sanity-check their own pricing and positioning.
• Review-signal analysis — pull guest review scores and text at scale for sentiment or competitive analysis.
• Travel-agtech and itinerary tools — bulk-source structured hotel data (name, coordinates, star rating, price) to power a booking or comparison product.

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

{
  "destination": "Paris, France",
  "checkin": "2026-09-10",
  "checkout": "2026-09-12",
  "adults": 2,
  "rooms": 1,
  "maxHotelsPerSearch": 20,
  "scrapeReviews": false,
  "countryCode": "US",
  "currency": "USD"
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

hotel_namebooking_urladdresscitycountrylatitudelongitudestar_ratingreview_scorereview_countpricecurrencyroom_typethumbnail_urlreviews

{
  "hotel_name": "H\u00f4tel Eiffel Trocad\u00e9ro",
  "booking_url": "https://www.booking.com/hotel/fr/eiffel-trocadero.html",
  "address": "35 Rue Benjamin Franklin, 75116 Paris",
  "city": "Paris",
  "country": "France",
  "latitude": 48.8635,
  "longitude": 2.287,
  "star_rating": 4.0,
  "review_score": 8.6,
  "review_count": 1204,
  "price": 189.0,
  "currency": "USD",
  "room_type": "Superior Double Room",
  "thumbnail_url": "https://cf.bstatic.com/xdata/images/hotel/square200/....jpg",
  "checkin": "2026-09-10",
  "checkout": "2026-09-12",
  "reviews": null
}

Pricing

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.