# Booking.com Reviews Scraper - Hotel Guest Reviews (`thirdwatch/booking-reviews-scraper`) Actor

Extract public Booking.com hotel reviews by property name, URL, slug, or numeric ID, including review text, guest and stay details, replies, photos, and hotel sub-scores.

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

## Pricing

from $2.00 / 1,000 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Booking.com Reviews Scraper

Extract public guest reviews for Booking.com hotels, apartments, hostels, and resorts. Supply a property name, Booking.com hotel or review URL, URL slug, or numeric property ID. The Actor returns one structured dataset row per unique review and bills that row atomically when it is written.

The scraper uses plain HTTP on Python 3.14 in a 256 MB container. It resolves names and slugs through Booking.com's autocomplete JSON endpoint and reads reviews through the site's `ReviewList` GraphQL operation. No browser, login, cookie pool, or private account is used.

### Input

| Field | Default | Description |
|---|---:|---|
| `queries` | required | Property names, Booking.com URLs, slugs, or numeric hotel IDs. |
| `maxResults` | `50` | Maximum unique reviews per property, from 1 to 20,000. |
| `sortBy` | `newest` | Newest, oldest, most relevant, score high-to-low, or score low-to-high. |
| `travelerType` | `all` | Optional traveller-segment filter. |
| `reviewLanguages` | `[]` | Optional two-letter review-language codes. |
| `onlyWithText` | `false` | Exclude score-only ratings while continuing pagination. |
| `keyword` | empty | Booking.com's review-text relevance filter. |
| `proxyConfiguration` | Apify Residential, India | Booking's CloudFront edge challenges direct cloud egress. The proven default combines a residential route with the Actor's Chrome-shaped ReviewList transport; custom proxies are supported, and explicitly disabling proxying can fail closed with HTTP 202. |

```json
{
  "queries": [
    "Atlantis The Palm Dubai",
    "https://www.booking.com/hotel/gb/the-savoy-london.html",
    "280149"
  ],
  "maxResults": 100,
  "sortBy": "newest",
  "reviewLanguages": ["en"],
  "onlyWithText": true
}
```

### Output

Each review can include:

- Stable review reference and public review/property URLs.
- Hotel ID, name, city, region, country, country code, coordinates, total review count, filtered review count, and category sub-scores for staff, facilities, cleanliness, comfort, value, location, and Wi-Fi.
- Review title, 1–10 score, positive text, negative text, combined text, original language, published timestamp, helpful votes, translation availability, and approval flag.
- Public reviewer display name, country, country code, avatar URL, and anonymity flag.
- Traveller type, room name and ID, check-in/out dates, nights, and stay status.
- Public property reply plus the largest available guest-photo URLs.
- Original input query and scrape timestamp.

Empty strings are normalized to `null`; numeric values are emitted as numbers. Duplicate review references are removed within pagination and again across duplicate input properties.

### Empty and failure behavior

A successful ReviewList response with `reviewsCount: 0` is a legitimate empty result. The run log records whether the property has no reviews or no reviews match the selected filters. When `onlyWithText` excludes every score-only card, the log records `no_reviews_with_written_text` after the feed is exhausted.

Network errors, non-JSON challenge pages, GraphQL errors, malformed payloads, stalled pagination, and deadline exhaustion are not treated as successful empty datasets. Requests use bounded exponential backoff and a shared run deadline. When a proxy is enabled, the Apify SDK supplies its credentials and a fresh proxy session for every retry; proxy URLs and passwords are never written to the Actor log. If every requested property fails upstream, the Actor fails the run instead of silently returning zero rows. A property name that validly returns no autocomplete match is logged separately as `no_property_match`.

### Limitations

- Booking.com controls two undocumented public endpoints used by its own website. Request shapes, filter tokens, fields, or access rules can change without notice.
- Review pages contain at most 25 cards per request. Large histories need many sequential, rate-limited requests and may finish partially if the run deadline is reached.
- Name lookup returns the first hotel match supplied by Booking.com. For ambiguous names, use a full Booking.com property URL or numeric ID.
- Bare numeric IDs can fetch reviews but do not reliably provide hotel name, city, country, coordinates, or a canonical slug because autocomplete is name-to-ID, not ID-to-name.
- The keyword option is Booking.com's relevance search, not a guaranteed literal substring filter.
- Review text stays in its original language. The feed indicates translatability but does not provide Booking.com's rendered machine translation.
- Reviewer names are limited to the public display name Booking.com exposes, often a first name. No contact details are collected.
- Guest photos and property replies are optional and absent from many reviews.
- This Actor covers reviews only. It does not return room rates, availability, inventory, or bookings.
- Proxy-free access is currently sufficient for moderate jobs, but Booking.com may rate-limit shared networks. A proxy can help with transport failures but does not guarantee access.

### Responsible use

Only publicly visible review data is collected. The Actor does not authenticate, access bookings, or bypass a paywall. Review display names and countries can still be personal data; use, retain, and share them in accordance with Booking.com's terms and applicable privacy law.

# Actor input Schema

## `queries` (type: `array`):

Hotel names, full Booking.com hotel/review URLs, property slugs, or numeric Booking.com hotel IDs.

## `maxResults` (type: `integer`):

Maximum unique reviews to return for each hotel. Booking serves at most 25 cards per page.

## `sortBy` (type: `string`):

Choose Booking.com's native ordering for the review feed.

## `travelerType` (type: `string`):

Optionally keep reviews from one Booking.com traveller segment.

## `reviewLanguages` (type: `array`):

Optional two-letter language codes such as en, fr, de, ar, or zh.

## `onlyWithText` (type: `boolean`):

Exclude score-only reviews. Pagination continues past excluded cards.

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

Optional Booking.com review-text search, for example breakfast, noise, or parking.

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

Residential proxying is enabled by default because Booking.com's CloudFront edge challenges standard cloud egress. You may provide a custom proxy or explicitly disable proxying, but direct cloud runs can fail closed with HTTP 202.

## Actor input object example

```json
{
  "queries": [
    "Atlantis The Palm Dubai",
    "https://www.booking.com/hotel/gb/the-savoy-london.html"
  ],
  "maxResults": 50,
  "sortBy": "newest",
  "travelerType": "all",
  "reviewLanguages": [],
  "onlyWithText": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "IN"
  }
}
```

# Actor output Schema

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

No description

# 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 = {
    "queries": [
        "Atlantis The Palm Dubai",
        "https://www.booking.com/hotel/gb/the-savoy-london.html"
    ],
    "maxResults": 50,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "IN"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("thirdwatch/booking-reviews-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 = {
    "queries": [
        "Atlantis The Palm Dubai",
        "https://www.booking.com/hotel/gb/the-savoy-london.html",
    ],
    "maxResults": 50,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "IN",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("thirdwatch/booking-reviews-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 '{
  "queries": [
    "Atlantis The Palm Dubai",
    "https://www.booking.com/hotel/gb/the-savoy-london.html"
  ],
  "maxResults": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "IN"
  }
}' |
apify call thirdwatch/booking-reviews-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thirdwatch/booking-reviews-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/ubzNkcUe3uI4AMGXe/builds/88LmaYRfpLhb7eILV/openapi.json