# Booking.com Reviews Scraper: Pros, Cons, Reviewer Country (`arcadium/booking-reviews`) Actor

Booking.com hotel reviews for hotel URLs: score, liked and disliked text, hotel reply, reviewer country, traveler type, stay details; $1.80 per 1,000 reviews. Filters by traveler type, score and season, optional free hotel summary. Only-new mode, free error rows, no reviewer names.

- **URL**: https://apify.com/arcadium/booking-reviews.md
- **Developed by:** [Arcadium Data](https://apify.com/arcadium) (community)
- **Categories:** Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.81 / 1,000 reviews

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 Reviews Scraper: Pros, Cons, Reviewer Country

Give it Booking.com hotel URLs and it returns one JSON row per guest review: score (1-10 and on a 0-5 scale), what the guest liked and disliked as separate fields, title, date, language, traveler type, room type, nights, reviewer country and the hotel's reply. $1.80 per 1,000 reviews on the free plan, less on paid plans; you pay only for rows you get.

**Why this actor**

- **Liked and disliked text arrive split**, so aspect-level analysis needs no guessing.
- **Filters by traveler type, score band and season**, with one charge per review even when it matches several passes.
- **Only new reviews and a free coverage row** per hotel (stated vs delivered), plus a free `error` row with a `code` for an input that failed.
- **Easy switch.** Input names of the other popular Booking reviews actor (`sortReviewsBy`, `cutoffDate`, `reviewScores`, `maxReviewsPerHotel`) are accepted.

Built by Arcadium Data: public data, dated and agent-ready, never personal data.

### Use with AI agents

Returns Booking.com hotel reviews (score, liked and disliked text, hotel reply, reviewer country) for hotel URLs. Agents can call it through the Apify MCP server (`https://mcp.apify.com`, open source as `apify/actors-mcp-server`) as `arcadium/booking-reviews`: the input schema is read from the actor, the result is a dataset of JSON rows.

Input example (minimal):

```json
{
  "startUrls": [
    {
      "url": "https://www.booking.com/hotel/gb/the-savoy.html"
    }
  ],
  "maxReviewsPerHotel": 20
}
```

What comes back: one `review` row per review (charged), free `coverage` rows (stated total vs delivered), an optional free `hotel-summary` row (`includeHotelSummary`) and a free `error` row for an input that could not be read. Filter on the `rowType` field. An input that fails is reported, not hidden (`includeErrorRows`, on by default): the error row carries `rowType: "error"`, a `code` (`invalid_input`, `not_found`, `blocked`, `unavailable`, `filter_unsupported` or `no_match`), a `message` and the `input` it is about. Retry on `blocked` and `unavailable` later; do not retry the other codes with the same input.

Cost of the call above: 20 reviews at $1.80 per 1,000 plus the $0.001 start fee is about $0.04 on the free plan; paid plans pay less. Free rows are never charged.

### What you get

| Field | What it holds |
| --- | --- |
| `reviewId` | Booking's own ID, prefixed `Booking___`. Stable between runs, so weekly exports can be deduplicated. |
| `date` | Review date, ISO format. |
| `title` | The review headline. |
| `pros`, `cons` | What the guest liked and disliked. `text` holds both joined. |
| `ratingOverall` | Score on a 0 to 5 scale (Booking's 1 to 10 score divided by 2). The original is in `extras.score10`. |
| `language` | Review language, empty when Booking could not tell. |
| `helpfulVotes` | How many readers marked the review as helpful. |
| `vendorResponse` | The hotel's reply, with the greeting name removed. |
| `extras` | Traveler type, room type, check-in and check-out dates, nights, photo count. |
| `country` | Reviewer country as a two-letter code. On by default; switch off with `includeReviewerCountry: false`. |
| `entityId`, `productName`, `productUrl`, `product` | Which hotel the review belongs to. |

Output example:

```json
{
  "platform": "booking",
  "reviewId": "Booking___c6397d1e2a854aa3",
  "date": "2026-09-30",
  "title": "Perfect stay",
  "pros": "Staff went out of their way for us.",
  "cons": null,
  "ratingOverall": 5,
  "language": "en",
  "vendorResponse": "Dear [name],\nThank you for staying with us...",
  "extras": { "score10": 10, "travelerType": "COUPLES", "roomType": "Superior King", "nights": 3 },
  "entityId": "280149",
  "productName": "The Savoy"
}
```

### Input

```json
{
  "startUrls": [{ "url": "https://www.booking.com/hotel/gb/the-savoy.html" }],
  "maxReviewsPerHotel": 500,
  "sort": "NEWEST_FIRST",
  "travelerTypes": ["COUPLES"],
  "scoreRanges": ["SUPERB", "GOOD"],
  "languages": ["en", "de"]
}
```

| Field | What it does |
| --- | --- |
| `startUrls`, `hotelIds` | Hotel or reviews page URLs, or numeric hotel IDs. Rows from IDs have no hotel name, and `productUrl` is the Booking.com home page because a hotel page address cannot be built from an ID alone. |
| `maxReviewsPerHotel` | Cap per hotel. |
| `sort` | Newest first (default), oldest first, highest or lowest score, most relevant. |
| `travelerTypes` | Families, couples, groups of friends, solo, business. |
| `scoreRanges` | Superb (9+), good (7-9), passable (5-7), poor (3-5), very poor (1-3). |
| `languages`, `seasons`, `topics`, `keyword` | Language codes, stay season, topic IDs, free-text search. |
| `dateFrom` | Only reviews from this date on. With newest first, reading stops once reviews are older. With any other sort, every page is read and older reviews are filtered out, so it costs more requests. |
| `onlyNewReviews`, `stateKey` | Only reviews not delivered by an earlier run with the same key. |
| `includeHotelSummary` | One free row per hotel with the overall score and the category scores (cleanliness, comfort, location, staff, value, services, wifi) against the city average where Booking publishes it. |
| `includeReviewerCountry` | Adds the reviewer's country as an ISO code. On by default. |

Each traveler type, score band and season in your list is read as its own pass, so a long list multiplies the number of requests. A review that matches several passes is delivered and charged once. With newest first, `dateFrom` and `onlyNewReviews` stop each pass early as soon as a page is older than the cutoff, so extra passes cost a few requests each. With any other sort every pass is read in full.

### Migrating from another Booking reviews actor

These input names of the other popular Booking reviews actor are accepted as they are: `sortReviewsBy` (`f_recent_desc`, `f_score_desc` and so on), `cutoffDate`, `reviewScores` (`review_adj_superb`, `review_adj_good`, ...) and `maxReviewsPerHotel`. Output field names are our own.

### Coverage and edited reviews

A free `coverage` row per hotel says how many reviews the source reports against how many you received, and why reading stopped (your cap, the source's cap, or the end). With `onlyNewReviews`, a review that was edited after it was delivered comes back once more with `extras.changeType` set to `edited`; that row is charged like a new review.

### Use it from an AI assistant

Paste this into your assistant to run the actor for you:

```text
Use the Apify actor "booking-reviews" to collect reviews.
Input: {"startUrls":[{"url":"<hotel page URL>"}],"maxReviewsPerHotel":200,"sort":"NEWEST_FIRST"}
Each dataset row is one review. Key fields: date, title, pros, cons, ratingOverall, extras.travelerType.
Run it, then summarize the main praise and complaints and mention the review count.
```

### Use it from code

Python:

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("arcadium/booking-reviews").call(run_input={
    "startUrls": [{"url": "https://www.booking.com/hotel/gb/the-savoy.html"}],
    "maxReviewsPerHotel": 200,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["date"], item["ratingOverall"], item["pros"])
```

JavaScript:

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

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('arcadium/booking-reviews').call({
  startUrls: [{ url: 'https://www.booking.com/hotel/gb/the-savoy.html' }],
  maxReviewsPerHotel: 200,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, 'reviews');
```

### Pricing

You pay per review delivered, at the price of your Apify plan. Hotel summary rows, coverage rows, error rows and repeats in only-new mode are free.

| Apify plan | Per 1,000 reviews |
| --- | --- |
| Free | $1.80 |
| Starter (Bronze) | $1.71 |
| Scale (Silver) | $1.35 |
| Business (Gold) | $0.81 |
| Platinum | $0.45 |
| Diamond | $0.27 |

Plus a one-off $0.001 per GB of memory when a run starts.

Set a maximum cost per run in the Apify run options and the actor stops before it goes over.

### Related actors and data

- [Hotel Reviews Scraper: Tripadvisor, Booking.com, Google](https://apify.com/arcadium/hotel-reputation)
- [Tripadvisor Reviews Scraper: Ratings, Replies, Translations](https://apify.com/arcadium/tripadvisor-reviews)
- [Booking.com Prices Scraper: Rates, Availability, Monitor](https://apify.com/arcadium/booking-prices)
- [Review Monitor: Negative Review Alerts and Rating Drift](https://apify.com/arcadium/reputation-monitor)
- [Hotel demand peaks report](https://arcadiumdata.io/reports/hotel-demand-peaks/): the next 90 nights of hotel rates by city, with spike nights flagged.
- [Arcadium Data MCP Server](https://apify.com/arcadium/arcadium-mcp): AI agents can ask the same questions as tools (`search_reviews`, `hotel_prices`, `city_rate_curve`, `review_snapshot`).

### Use cases

- Reputation monitoring: pull the newest reviews every week with `onlyNewReviews` and watch what changes.
- Competitor benchmarking: compare category scores (location, staff, value) across hotels in one city with the summary row.
- Complaint mining: filter to poor and very poor scores and read the `cons` column.
- Model training: aspect-level sentiment from the native liked and disliked split.

### Limitations

- Public reviews only. Nothing behind a login.
- Booking only shows roughly the last three years of reviews, so "all reviews" means that window.
- Review language is empty for a small share of reviews where Booking does not know it.
- Searching by hotel name is not supported yet. Paste the hotel page URL or the hotel ID.
- `dateFrom` works with every sort order, but only newest first can stop early; other orders read all matching pages and filter.
- Hotel IDs without a URL give rows without a hotel name; Booking only reports the name through the hotel page.
- Booking publishes category scores (cleanliness, location and so on) per hotel, not per review, so they are in the optional summary row only.
- City averages in the summary row are only available when the hotel is given as a URL.

### Privacy

Reviewer names, usernames, profile photos, guest photos, emails and phone numbers are never collected. Names in greetings and sign-offs (for example 'Dear John' or 'Regards, Anna') are replaced with \[name]; other names in the text are not detected. The reviewer's country is on by default and is a two-letter country code, nothing else about the person; switch it off with `includeReviewerCountry: false`.

### FAQ

**How fresh is the data?**
It is read when you run the actor, so it matches what the site shows at that moment.

**Can I get only new reviews since my last run?**
Yes. Turn on `onlyNewReviews` and keep the same `stateKey`. The state is stored per hotel. Use another `stateKey` to start a separate series.

**A hotel returned no reviews. Why?**
Check that the URL opens a hotel page in your browser. Unknown hotels and hotels without reviews return an error row, which is not charged.

**Something looks wrong in the output. Who do I tell?**
Open an issue on the actor page with the run link. We read them all.

# Actor input Schema

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

Booking.com hotel pages or hotel review pages, for example https://www.booking.com/hotel/gb/the-savoy.html.

## `hotelIds` (type: `array`):

Numeric Booking.com hotel IDs, as an alternative to URLs. Rows from IDs carry no hotel name.

## `maxReviewsPerHotel` (type: `integer`):

Maximum number of reviews to collect for each hotel. Booking only shows about the last three years.

## `sort` (type: `string`):

Order of the reviews. Newest first is required for the date filter and for only-new-reviews mode.

## `travelerTypes` (type: `array`):

Only reviews from these kinds of travelers. Leave empty for all.

## `scoreRanges` (type: `array`):

Only reviews in these score bands: Superb 9+, Good 7-9, Passable 5-7, Poor 3-5, Very poor 1-3.

## `seasons` (type: `array`):

Only reviews of stays in these periods of the year.

## `languages` (type: `array`):

Two-letter language codes such as en or de. Leave empty for all languages.

## `topics` (type: `array`):

Optional numeric topic filters as used by the site, for example 245 for breakfast, 249 for location, 270 for room.

## `keyword` (type: `string`):

Only reviews that mention this word or phrase. Example: breakfast.

## `dateFrom` (type: `string`):

Only reviews on or after this date (YYYY-MM-DD, or a relative span such as 30 days or 2 months; empty = no filter). Works with newest-first sorting.

## `onlyNewReviews` (type: `boolean`):

Return only reviews not delivered by a previous run with the same state key.

## `stateKey` (type: `string`):

Name of the saved state used by only-new-reviews mode. Use different keys for independent monitors. Example: weekly-monitoring.

## `includeHotelSummary` (type: `boolean`):

Add one free row per hotel with the overall score and category scores (cleanliness, location, staff and more) compared with the city average.

## `includeReviewerCountry` (type: `boolean`):

Add the reviewer's country as a two-letter ISO code in the country field. On by default; no names or photos are ever returned.

## `includeErrorRows` (type: `boolean`):

Add a free row to the dataset for each hotel that could not be read.

## `includeCoverageRows` (type: `boolean`):

Add one free row with rowType 'coverage' per source: the review total the site states, how many were delivered, why paging ended and whether anything is missing. Not charged.

## `markEdited` (type: `boolean`):

With 'Only new reviews': also deliver reviews seen before whose text changed in the last 7 days, marked extras.changeType 'edited'. Edited reviews are charged like new ones.

## `maxRetries` (type: `integer`):

How often a failed request is retried before the hotel is skipped.

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

Optional override. By default the actor picks a suitable proxy automatically.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.booking.com/hotel/gb/the-savoy.html"
    }
  ],
  "hotelIds": [],
  "maxReviewsPerHotel": 20,
  "sort": "NEWEST_FIRST",
  "travelerTypes": [],
  "seasons": [],
  "languages": [],
  "topics": [],
  "onlyNewReviews": false,
  "stateKey": "default",
  "includeHotelSummary": false,
  "includeReviewerCountry": true,
  "includeErrorRows": true,
  "includeCoverageRows": true,
  "markEdited": true,
  "maxRetries": 3
}
```

# Actor output Schema

## `results` (type: `string`):

All rows of this run in the default dataset.

## `view_overview` (type: `string`):

No description

## `view_ratings` (type: `string`):

No description

## `view_errors` (type: `string`):

No description

## `record_stats` (type: `string`):

Requests, data volume, retries and cost per result for this run.

## `record_product` (type: `string`):

Hotel profile data collected next to the reviews.

# 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/hotel/gb/the-savoy.html"
        }
    ],
    "maxReviewsPerHotel": 20,
    "sort": "NEWEST_FIRST"
};

// Run the Actor and wait for it to finish
const run = await client.actor("arcadium/booking-reviews").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/hotel/gb/the-savoy.html" }],
    "maxReviewsPerHotel": 20,
    "sort": "NEWEST_FIRST",
}

# Run the Actor and wait for it to finish
run = client.actor("arcadium/booking-reviews").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/hotel/gb/the-savoy.html"
    }
  ],
  "maxReviewsPerHotel": 20,
  "sort": "NEWEST_FIRST"
}' |
apify call arcadium/booking-reviews --silent --output-dataset

```

## MCP server setup

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

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/VvI9qcntoXHIMaVpj/builds/OTJ1h0WZ42Jegr4eB/openapi.json