# Booking.com Scraper for Hotel Prices & Reviews (`runtime/booking-scraper`) Actor

Extract Booking.com hotel search results with prices, ratings, review counts, addresses, coordinates, direct hotel URLs, filters, and optional room details.

- **URL**: https://apify.com/runtime/booking-scraper.md
- **Developed by:** [scraping automation](https://apify.com/runtime) (community)
- **Categories:** E-commerce, Travel
- **Features:** Limited permissions
- **Stats:** 97 total users, 4 monthly users, 100.0% runs succeeded, 3 bookmarks
- **User rating**: 1.20 out of 5 stars

## Pricing

from $6.50 / 1,000 hotel results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Booking.com Scraper for Hotel Prices & Reviews

> **中文简介 / Chinese summary**
>
> - **功能：** 抓取 Booking.com 酒店搜索结果：价格、评分、评论数、地址、坐标和酒店链接，可选房型详情。
> - **输入示例：** `{"destination":"Paris","maxHotels":10}`
> - **计费：** 按结果付费（pay-per-result），价格见本页 **Pricing** 标签；可设置单次运行最大费用以控制支出。
> - **支持：** 遇到问题请在 **Issues** 标签提交，并附上输入参数和 Run ID。

Extract Booking.com hotel search results with prices, ratings, review counts,
addresses, coordinates, direct hotel URLs, filters, and optional room details.

### Best for

- Revenue managers comparing hotel prices by date and destination
- Travel market analysts tracking ratings, review counts, and property supply
- Data teams building hotel dashboards, alerts, or enrichment pipelines
- Operators who need a small, repeatable Booking.com dataset instead of a broad crawl

### Quick start

Use a small validation run first. It keeps cost and runtime predictable while you
check the output columns.

```json
{
  "destination": "Paris",
  "checkin": "2026-07-15",
  "checkout": "2026-07-16",
  "groupAdults": "2",
  "groupChildren": "0",
  "noRooms": "1",
  "maxHotels": 5,
  "batchSize": 1,
  "getDetails": false,
  "failOnNoResults": true,
  "timeout": 600,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "FR"
  }
}
```

### Common workflows

- **Price monitoring**: run the same destination and dates daily or weekly, then
  compare `price`, `rating`, `reviewCount`, and `hotelLink`.
- **Market mapping**: collect hotels by city, district, star rating, review
  score, and distance from center.
- **Room research**: enable `getDetails` for selected hotels when you need room
  names, room prices, facilities, and more precise address fields.
- **Travel lead enrichment**: export hotel URLs, names, ratings, coordinates,
  and source metadata to a CRM or BI tool.

### Useful input fields

| Field | Use |
| --- | --- |
| `destination` | City or place to search, such as `Paris` or `New York`. |
| `startUrls` | Use direct Booking.com search URLs when you already have them. |
| `checkin`, `checkout` | Stay dates in `YYYY-MM-DD` format. |
| `groupAdults`, `groupChildren`, `noRooms` | Guest and room settings. |
| `maxHotels` | Keep low for validation runs, then increase gradually. |
| `priceMin`, `priceMax`, `stars`, `minReviewScore` | Market filters. |
| `getDetails` | Visits hotel pages for richer address and room data. |
| `proxyConfiguration` | Residential proxy is recommended for Booking.com. |

### Output fields

The dataset can include:

- `hotelName`
- `hotelLink`
- `price`
- `rating`
- `reviewText`
- `reviewCount`
- `locationScore`
- `description`
- `address`
- `latitude`
- `longitude`
- `rooms`
- `detailFetched`
- `scrapedAt`

When `getDetails` is enabled, the Actor may also save room names, capacity,
prices, facilities, detailed address fields, breadcrumbs, nearby context, and
review breakdown fields when Booking.com exposes them.

### Settings that convert best

- Start with `maxHotels: 5` and `getDetails: false`.
- Use `getDetails: true` only for smaller follow-up runs.
- Match the proxy country to the destination country when possible.
- Keep `batchSize` low for stable browser runs.
- Set `failOnNoResults: true` for scheduled monitoring, so empty runs are easy
  to detect.

### Cost and runtime expectations

Booking.com uses dynamic pages and anti-bot controls, so browser and proxy setup
cost more than a static HTML scraper. Small validation runs should finish first;
large detailed runs should be split by city, date, or hotel subset. If a run is
slow, reduce `maxHotels`, disable `getDetails`, or narrow filters before scaling.

### Limitations

Booking.com can change layout, hide prices, localize fields, or require extra
browser work. Prices and availability are time-sensitive and can differ by
market, currency, date, guest count, and proxy location. Always keep source URLs
and run timestamps when using the data for reporting.

### Support

If a run returns unexpected data, open an issue from the Actor page with the
input used, the run ID, and the result you expected.

# Actor input Schema

## `startUrls` (type: `array`):

URLs to start crawling from. Defaults to Booking.com homepage.

## `destination` (type: `string`):

The city or destination to search for hotels.

## `getDetails` (type: `boolean`):

When enabled, the actor will visit each individual hotel page to extract complete addresses and coordinates. This provides more accurate data but takes longer to run. For quick tests, keep this disabled.

## `checkin` (type: `string`):

Check-in date in YYYY-MM-DD format.

## `checkout` (type: `string`):

Check-out date in YYYY-MM-DD format.

## `groupAdults` (type: `string`):

Number of adults.

## `groupChildren` (type: `string`):

Number of children.

## `noRooms` (type: `string`):

Number of rooms.

## `priceMin` (type: `integer`):

Minimum price per night in euros.

## `priceMax` (type: `integer`):

Maximum price per night in euros.

## `stars` (type: `array`):

Filter by star rating (1-5). Can specify multiple ratings. Example: \[4, 5]

## `minReviewScore` (type: `number`):

Minimum review score (0-10).

## `freeCancellation` (type: `boolean`):

Filter for properties with free cancellation.

## `petsAllowed` (type: `boolean`):

Filter for properties that allow pets.

## `adultsOnly` (type: `boolean`):

Filter for adults-only properties.

## `maxHotels` (type: `integer`):

Maximum number of hotels to extract from the search results. Set to 0 to extract all available hotels. Recommended: 5 for quick tests, 10-50 for production.

## `failOnNoResults` (type: `boolean`):

When enabled, the Actor fails the run if no hotels are saved. Useful for monitoring, saved tasks, and integrations that must detect blocked or empty runs.

## `timeout` (type: `integer`):

Maximum time in seconds for request handler timeout. Note: The Actor Run Timeout (in Settings → Default Run Options) must be higher than this value. Recommended: 1800-3600 seconds for detailed extractions.

## `batchSize` (type: `integer`):

Number of hotels to extract in each batch. Use 1 for one-by-one extraction, or higher for batch processing.

## `proxyConfiguration` (type: `object`):

Choose to use no proxy, Apify Proxy, or provide custom proxy URLs.

## `newUrlFunction` (type: `string`):

Custom function to generate proxy URLs. Advanced users only.

## `districts` (type: `array`):

Filter by specific districts or neighborhoods.

## `maxDistanceFromCenter` (type: `number`):

Maximum distance from city center in kilometers.

## `customFilters` (type: `array`):

Custom filters using Booking.com nflt codes. To find these codes, apply filters manually on Booking.com and inspect the URL. Example: \['ht_id=204', 'ht_id=207']

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.booking.com"
    }
  ],
  "destination": "New York, London, Tokyo, Paris, Rome",
  "getDetails": false,
  "checkin": "2026-07-09",
  "checkout": "2026-07-10",
  "groupAdults": "2",
  "groupChildren": "0",
  "noRooms": "1",
  "priceMin": 160,
  "priceMax": 530,
  "stars": [
    "4",
    "5"
  ],
  "minReviewScore": 8,
  "freeCancellation": false,
  "petsAllowed": false,
  "adultsOnly": false,
  "maxHotels": 5,
  "failOnNoResults": false,
  "timeout": 1800,
  "batchSize": 10,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "FR"
  },
  "districts": [
    "Le Marais",
    "5e arr."
  ],
  "maxDistanceFromCenter": 3,
  "customFilters": [
    "ht_id=204",
    "ht_id=207"
  ]
}
```

# Actor output Schema

## `hotelName` (type: `string`):

Name of the hotel or accommodation

## `price` (type: `string`):

Price per night (formatted string or null if not available)

## `rating` (type: `string`):

Guest rating score (0-10)

## `reviewText` (type: `string`):

Qualitative review label (e.g., 'Wonderful', 'Very Good')

## `reviewCount` (type: `string`):

Total number of reviews

## `locationScore` (type: `string`):

Location rating score

## `description` (type: `string`):

Hotel description and highlights from Booking.com

## `imageUrl` (type: `string`):

URL of the hotel's main image

## `address` (type: `string`):

Hotel address (basic from search results or detailed from hotel page)

## `latitude` (type: `string`):

GPS latitude coordinate

## `longitude` (type: `string`):

GPS longitude coordinate

## `hotelLink` (type: `string`):

Direct link to the hotel page on Booking.com

## `rooms` (type: `string`):

Array of room objects with details (only when getDetails: true)

## `scrapedAt` (type: `string`):

ISO timestamp when the data was scraped

## `pageType` (type: `string`):

Type of page where data was extracted (search_results, hotel_details, individual_hotel)

## `detailRequested` (type: `string`):

Whether detailed information was requested (getDetails: true)

## `detailFetched` (type: `string`):

Whether detailed information was successfully fetched

## `detailPrice` (type: `string`):

Price extracted from detail page

## `detailRating` (type: `string`):

Rating extracted from detail page

## `detailAddress` (type: `string`):

Full address extracted from detail page

## `detailLatitude` (type: `string`):

Latitude extracted from detail page

## `detailLongitude` (type: `string`):

Longitude extracted from detail page

## `detailScrapedAt` (type: `string`):

ISO timestamp when detail page was scraped

## `detailPageUrl` (type: `string`):

URL of the detail page that was scraped

## `detailQualityRating` (type: `string`):

Quality rating from detail page (e.g., '4 out of 5 stars')

## `detailIsPreferredPartner` (type: `string`):

Whether the hotel is a preferred partner

## `detailDescription` (type: `string`):

Full description from detail page

## `detailPopularFacilities` (type: `string`):

List of popular facilities from detail page (array as JSON string)

## `detailPropertyHighlights` (type: `string`):

Property highlights and key features from detail page (array as JSON string)

## `detailSustainability` (type: `string`):

Sustainability information and eco-friendly features (array as JSON string)

## `detailReviewBreakdown` (type: `string`):

Detailed breakdown of review scores by category (array as JSON string)

## `detailFeaturedReviews` (type: `string`):

Featured guest reviews from detail page (array as JSON string)

## `detailNearby` (type: `string`):

Nearby places and attractions (array as JSON string)

## `detailFaq` (type: `string`):

Frequently asked questions and answers (array as JSON string)

## `detailBreadcrumbs` (type: `string`):

Navigation breadcrumbs from detail page (array as JSON string)

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://www.booking.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("runtime/booking-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [{ "url": "https://www.booking.com" }] }

# Run the Actor and wait for it to finish
run = client.actor("runtime/booking-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://www.booking.com"
    }
  ]
}' |
apify call runtime/booking-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,runtime/booking-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/RxQstBaoAK3cLSVW3/builds/rYhg1pQF49GkjsMAa/openapi.json