Booking.com Hotel Price & Rating Snapshot Scraper

Pull a clean price-and-rating snapshot from Booking.com for a destination or a list of hotel URLs. This actor is built for speed: it reads search cards in search mode, or a hotel's own page in details mode, and returns flat JSON rows you can compare, schedule or load into a spreadsheet.

Two ways to use it

Mode	What it reads	Best for
Search a destination	Booking.com search result cards, expanded with the page's own "Load more results" control	Rate shopping across a city, market snapshots, price monitoring
Load hotel URLs	Each hotel's Booking.com page (price and rating block)	Checking specific properties you already track

Search mode never opens individual hotel pages, so it stays fast even at the 250-row cap. Details mode opens the pages you pass in and returns the property's own current rate, star rating and coordinates.

Output per hotel

Every row uses the same field names in both modes. Fields that do not apply to a mode are omitted.

• hotelId — Booking.com property identifier from the URL
• name — property name
• url — canonical Booking.com property URL
• propertyType — accommodation type (details mode)
• stars — official star rating (1-5)
• address — street address (details) or district and city (search)
• city, country
• latitude, longitude — map coordinates (details mode)
• distance — distance from downtown as shown on the search card
• rating — guest score on Booking.com's 0-10 scale
• reviewCount — number of guest reviews
• reviewWord — score label such as "Wonderful" or "Very Good"
• price — price for the whole stay in the requested currency
• pricePerNight — price divided by the number of nights
• originalPrice, discountPercent — visible struck-through price and discount
• taxesAndFees — taxes and fees shown with the rate
• currency — three-letter currency code
• photoUrl — main property photo
• checkin, checkout, nights, adults, rooms — the search parameters used
• mode — search or details
• detailStatus — search_only or enriched
• source — booking.com
• accessMethod — translate_mirror or browser+translate_mirror when the direct/proxy paths were challenged
• scrapedAt — capture timestamp in ISO 8601

Input

Field	Type	Default	Notes
mode	select	search	search for a destination, details for hotel URLs
destination	string	—	City, region or landmark; required in search mode (prefilled with Paris)
startUrls	array	—	Booking.com hotel links used by details mode (prefilled with one Paris hotel)
checkIn	string	—	YYYY-MM-DD; empty means tomorrow
checkOut	string	—	YYYY-MM-DD, must be after check-in; empty means check-in + 3 nights
adults	integer	2	1-30
rooms	integer	1	1-30
propertyType	select	all	Hotels, apartments, hostels, guesthouses, villas or resorts
minReviewScore	number	0	0-10 exact minimum after Booking.com's own filter
stars	select	0 (any)	1-5
freeCancellation	boolean	false	Only properties with a free-cancellation rate
breakfast	boolean	false	Only properties with a breakfast-included rate
pool	boolean	false	Only properties with a swimming pool
minPrice, maxPrice	number	—	Nightly price bounds in the chosen currency
currency	string	USD	EUR, GBP, JPY, etc.
language	select	en-us	Page language used for the request
maxItems	integer	10	1-250
proxyConfiguration	object	Direct	Optional; without it the actor tries direct, then the free translate-mirror fallback, then Apify proxy

The old input names are still accepted by the code: location maps to destination, checkinDate/checkoutDate map to checkIn/checkOut, and maxResults maps to maxItems.

Examples

Weekend price check for Lisbon:

{
  "mode": "search",
  "destination": "Lisbon",
  "checkIn": "2026-11-20",
  "checkOut": "2026-11-23",
  "currency": "EUR",
  "maxItems": 30
}

Track two specific hotels:

{
  "mode": "details",
  "startUrls": [
    { "url": "https://www.booking.com/hotel/fr/du-printemps-paris.html" },
    { "url": "https://www.booking.com/hotel/fr/sorbonne.html" }
  ],
  "checkIn": "2026-12-01",
  "checkOut": "2026-12-04",
  "adults": 2,
  "rooms": 1
}

Well-rated hotels with free cancellation:

{
  "mode": "search",
  "destination": "Berlin",
  "propertyType": "hotels",
  "minReviewScore": 8.5,
  "freeCancellation": true,
  "maxItems": 20
}

How pagination works

Booking.com returns a first batch of cards and adds more when its own "Load more results" control is clicked. The actor keeps clicking that control and scrolling until it reaches maxItems or the page stops growing. When the live site is WAF-challenged, the translate-mirror fallback reads successive result pages across several sort orders and deduplicates by hotel URL. The practical ceiling is 250 rows per run; split a large market by neighborhood, dates or filters to collect more.

FAQ

Do I need a Booking.com account? No. The actor reads public search and hotel pages. No login, cookie or API key is required.

Do I need to configure a proxy? No. The actor connects directly first. If Booking.com challenges that connection, it retries through Google Translate's public mirror (no proxy or key) and only then falls back to Apify proxy groups. accessMethod tells you which path produced each row.

Is price per night or for the whole stay? price is the full stay price Booking.com shows for your dates. pricePerNight divides it by nights.

Why is a field missing from some rows? Search cards and hotel pages expose different data. Coordinates and propertyType usually come from a hotel page, while distance comes from a search card. Empty values are omitted rather than filled with zeros or placeholders.

What happens when a hotel has no available rate? Details mode skips that hotel and reports a partial result. If every page fails, the run fails with a clear status instead of writing empty rows.

Can I scrape more than one destination in one run? Yes at the task level: one run is one destination. Create one task per city, or use details mode with a URL list.

Are prices guaranteed to match the live site a minute later? No. Availability and prices change continuously. Each row records scrapedAt so you can tell exactly when the snapshot was taken.

Is this affiliated with Booking.com? No. It is an independent third-party tool that reads publicly available Booking.com pages.

Limitations

• Search mode returns what the search page exposes: price, rating, stars, address and distance. It does not open each property, so room types, amenities and full policies are not included.
• Details mode reads the property page but does not wait for every lazy-loaded section; it returns the price/rating snapshot rather than a full facilities catalogue.
• Booking.com caps how many search results it will page through, and the actor caps a single run at 250 rows.
• Sold-out properties can be missing a rate. They are skipped in details mode and may be absent from search results.
• Booking.com serves more than one search layout. Some sessions expose stars and the load-more control, while a stripped mirror variant exposes cards without star icons. The actor reads whatever the page provides and never invents missing values; price, score and review count remain available.
• Booking.com can challenge direct, AUTO and residential exits with HTTP 202. The translate-mirror fallback normally recovers search and hotel pages; it can rate-limit (HTTP 429), serve a cached page, or omit a result batch. If every path fails the run stops with BLOCKED instead of returning empty or invented rows. Mirror rows are marked accessMethod: translate_mirror.