Booking.com Hotel Scraper
Pricing
from $2.00 / 1,000 hotel scrapeds
Booking.com Hotel Scraper
Scrape Booking.com hotel prices, availability, ratings, rooms, policies, facilities, photos, and review summaries. Export CSV, JSON, Excel, or use the API.
Booking.com Hotel Scraper
Pricing
from $2.00 / 1,000 hotel scrapeds
Scrape Booking.com hotel prices, availability, ratings, rooms, policies, facilities, photos, and review summaries. Export CSV, JSON, Excel, or use the API.
One city, region, landmark, or hotel search phrase. Supply destination, destinations, or hotelUrls; at least one target is required at runtime, and these modes may be combined (25 targets total). Lisbon is a form prefill, not an API default. For multiple searches, use destinations.
Optional Booking.com /hotel/{country}/{slug}.html URLs, using HTTP or HTTPS without credentials or a port. Each URL is resolved from its hotel-name slug and returns at most one stable-ID match; renamed properties or access challenges can prevent a match. Supply these, destination, or destinations.
Adult guests used for availability and price context.
Hard cap across every destination and hotel URL in this run. A hotel-scraped charge occurs only when that base row is saved.
Optional list of destination searches. Each entry has its own maxHotelsPerSearch cap.
Resolve check-in this many days after the current UTC date during input initialization. Use together with stayNights instead of checkIn/checkOut. Cannot be combined with fixed dates.
Resolve check-out from the relative check-in date. Use together with checkInOffsetDays instead of fixed dates.
Number of children. Must equal the number of entries in childrenAges.
One age from 0 to 17 for every child, for example [4, 9].
[]Rooms used for availability and price context.
Three-letter requested currency. The returned currency is recorded separately in every row.
Booking.com language parameter, for example en-us or de-de. Provenance records the applied value.
On Apify, omission uses the existing residential route; omission in local development uses direct access. No default or prefill is injected here. Explicit proxyConfiguration takes precedence: useApifyProxy:false selects direct access; useApifyProxy:true selects managed access with optional nonempty apifyProxyGroups and uppercase two-letter apifyProxyCountry; proxyUrls selects a customer HTTP/HTTPS pool. Do not combine a customer pool with managed fields, or direct opt-out with managed groups/country. Invalid or unsupported settings reject before target work; selected-route failure never enables another pool or paid fallback. Managed access uses countryCode only when apifyProxyCountry is absent. Access and costs depend on the selected service; no route guarantees success. Never post proxy URLs or credentials in issues.
Optional two-letter country code for the omitted residential route on Apify, or managed access when proxyConfiguration.apifyProxyCountry is absent. Explicit direct access and customer proxy pools ignore this value. It does not guarantee target access.
Optional property categories. Multiple values are combined as alternatives.
Optional minimum guest review score.
Optional exact property star ratings as integers from 1 to 5, for example [4, 5]. Multiple values are combined as alternatives.
Keep only listings currently exposing a free-cancellation option for the requested stay context.
Optional lower bound in the requested/returned currency. Calculated from the displayed stay total divided by nights; requires dates.
Optional upper bound in the requested/returned currency. Calculated from the displayed stay total divided by nights; requires dates.
Requests Booking.com ordering: RECOMMENDED uses its default; PRICE_ASC requests price; TOP_REVIEWED requests review score and price; STARS_DESC/STARS_ASC request descending/ascending stars. The requested sorter is recorded in provenance; results are not independently re-sorted, and the upstream service may vary its order. Default RECOMMENDED.
Maximum unpaid candidate rows inspected per destination while applying filters. This must be at least maxHotelsPerSearch and does not change the saved/charged cap.
Maximum rows from each destination target. Direct hotel URL targets can return at most one row each.
Fetch room configurations and matched offers independently for each hotel.
Fetch cancellation, prepayment, pet, and meal-plan signals independently.
Fetch facility/USP highlights independently.
Fetch the available hotel photo set independently.
Fetch score labels, secondary scores, and available review summary metadata independently. This does not return individual guest review text.
Legacy alias that sets both saved-row limits. Do not combine it with maxHotelsPerSearch or maxHotelsPerRun, including values inserted by a form. Omission defaults each saved-row limit to 10; form prefills suggest 5.