Booking.com Hotel Search Scraper

What does Booking.com Hotel Search Scraper do?

Booking.com Hotel Search Scraper searches Booking.com hotels by destination — free-text destinations are resolved to a destId automatically, then real price/sort filters (confirmed live: a price range genuinely narrows results, sort order genuinely reorders them) are applied. Optionally fetches full hotel detail (rooms, photos, amenities) for every result in one run. Falls back to the app's own Home tab feed when no destination is given.

It talks directly to the same internal API the official Booking.com Android app uses, reverse-engineered by capturing live traffic from a real device. Auth uses a standard, publicly-documented token-exchange mechanism, generated fresh server-side — no Booking.com account, no API key of your own. This is the hotel-search slice of Booking.com All-in-One API, split out as its own focused Actor.

Why use Booking.com Hotel Search Scraper?

• Real filters and sort that genuinely work — price range and sort order confirmed live by comparing results before/after
• Real multi-region pricing — the exact same search with different currency codes returns genuinely different prices for the same rooms, not a symbol swap
• Automatic destination resolution — pass a plain city name; this Actor resolves it to Booking's internal destId for you
• Optional full hotel detail in the same run — no separate Actor call needed for room-level detail
• No account needed — every request works fully anonymously
• Use cases: travel content aggregation, price monitoring across currencies, destination research bots

Input

Field	Type	Description
query	string	Free-text destination, e.g. Bangkok. Resolved to a destId automatically. Ignored if destId is set.
destId	string	Exact Booking.com dest_id, e.g. -3414440 for Bangkok. Skips resolution.
destName	string	Optional, only used with destId.
checkin / checkout	string (date)	YYYY-MM-DD, default tomorrow/day-after
adults	integer	Default 2
rooms	integer	Default 1
priceMin / priceMax	integer	Confirmed live to genuinely narrow results
sort	string	popularity | best_value | price
currency	string	ISO code, default USD. Confirmed live to change returned prices for any region.
includeHotelDetail	boolean	Fetch full hotel detail (rooms, photos, amenities) per result. Default false.
maxItems	integer	Stop once this many hotels have been pushed. Default: push every result from the search.

If both query and destId are empty, this Actor pushes one row with the app's own Home tab feed instead of searching.

Example:

{
    "query": "Bangkok",
    "checkin": "2026-09-08",
    "checkout": "2026-09-10",
    "adults": 2,
    "priceMax": 150,
    "currency": "USD",
    "includeHotelDetail": true,
    "maxItems": 10
}

Output

One dataset row per hotel (trimmed example):

{
    "id": 27229,
    "name": "Ambassador Hotel Bangkok",
    "reviewScore": 7.2,
    "detail": { "...": "full room/amenity/photo data, only present when includeHotelDetail is true" }
}

Known limitations

• No offset/page parameter on /hotels. The underlying search endpoint returns its full result set in one call (rows: 'auto', confirmed in the parent Actor's proven implementation) rather than paging — this Actor exposes maxItems to cap how many results get pushed, not maxPages.
• Destination resolution takes the first autocomplete match. For an ambiguous free-text query, pass the exact destId instead (from a manual /search lookup on the parent Actor, or a previous run's resolved id).
• This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Booking.com B.V. Behavior may change if Booking.com changes its API.

Pricing

Pay-per-event: $0.0020 per hotel result (FREE plan; BRONZE/SILVER/GOLD/PLATINUM/DIAMOND get automatic discounts based on your Apify plan). Billed per hotel (or per home-feed row) pushed to the dataset.