# Booking Attractions Scraper (`romy/booking-attractions-scraper`) Actor

Get things-to-do search results and reviews from Booking. Talks directly to Booking.com's own mobile app API, no login or API key needed. Split from the mature, published booking-all-in-one-api for a focused, single-purpose workflow.

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

## Pricing

from $1.20 / 1,000 attraction chargeds

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

### What does Booking.com Attractions Scraper do?

**Booking.com Attractions Scraper** searches Booking.com things-to-do by destination — confirmed live: a real Bangkok search returned 1994 real results with real prices, ratings, and review counts. Three modes in one Actor: `search` (destination -> attraction list, with optional full detail per result), `detail` (one attraction's full detail by slug), and `reviews` (paginated reviews for one attraction, with an optional review-filter schema).

It talks directly to the same internal API the official [Booking.com](https://www.booking.com/) Android app uses, reverse-engineered by capturing live traffic from a real device. No Booking.com account, no API key of your own. This is the attractions slice of [Booking.com All-in-One API](https://apify.com/romy/booking-all-in-one-api), split out as its own focused Actor.

### Why use Booking.com Attractions Scraper?

- **Real results, confirmed live** — 1994 real things-to-do with real prices, ratings, and review counts for a real Bangkok search
- **Automatic destination resolution** — pass a plain city name; this Actor resolves it to a `ufi` for you (the same id space as hotels' `dest_id`)
- **Real paginated reviews** — confirmed live: 20 review ids per page, zero overlap between pages
- **A dedicated review-topic filter endpoint** — a genuinely separate call from both search and the reviews themselves, confirmed live its rating filter genuinely narrows results
- **No account needed** — every request works fully anonymously
- **Use cases:** things-to-do content aggregation, review analysis, destination research bots

### Input

Mode is auto-detected from which fields are set (`slug` -> `detail`, `id` -> `reviews`, otherwise `search`) if `mode` is left empty.

| Field            | Type    | Description                                                                                                                                                                          |
| ---------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `mode`           | string  | `search` | `detail` | `reviews`                                                                                                                                                    |
| `ufi`            | integer | Search mode. Destination id (same space as hotels' `dest_id`), e.g. `-3414440` for Bangkok.                                                                                          |
| `query`          | string  | Search mode. Free-text destination, resolved to `ufi` automatically. Ignored if `ufi` is set.                                                                                        |
| `page` / `limit` | integer | Search mode: result page/page size. Reviews mode: review page/page size. Default page `1`, limit `20`.                                                                               |
| `includeDetail`  | boolean | Search mode. Fetch full attraction detail for every result. Default `false`.                                                                                                         |
| `maxItems`       | integer | Search mode: max attractions pushed. Reviews mode: max reviews pushed.                                                                                                               |
| `slug`           | string  | Detail mode. The FULL slug string from a search result, e.g. `prvajppfwe7k-the-newest-luxury-5-star-bangkok-chao-phraya-dinner-cruise`. The short `id` alone will NOT resolve (404). |
| `id`             | string  | Reviews mode. The SHORT id field from a search result, e.g. `PRvAjpPfwE7K` — not the slug.                                                                                           |
| `rating`         | string  | Reviews mode. An option id from the review filter schema, e.g. `5`.                                                                                                                  |
| `includeFilters` | boolean | Reviews mode. Also push one row with the review filter/sort schema first. Default `false`.                                                                                           |

Example (search):

```json
{ "query": "Bangkok", "maxItems": 20 }
```

Example (detail):

```json
{ "slug": "prvajppfwe7k-the-newest-luxury-5-star-bangkok-chao-phraya-dinner-cruise" }
```

Example (reviews):

```json
{ "id": "PRvAjpPfwE7K", "rating": "5", "includeFilters": true }
```

### Output

Search mode: one row per attraction. Detail mode: one `{ "type": "detail", ... }` row. Reviews mode: one `{ "type": "review", ... }` row per review (trimmed example):

```json
{
    "id": "PRvAjpPfwE7K",
    "name": "The Newest Luxury 5-Star Bangkok Chao Phraya Dinner Cruise",
    "slug": "prvajppfwe7k-the-newest-luxury-5-star-bangkok-chao-phraya-dinner-cruise",
    "representativePrice": { "currency": "IDR", "chargeAmount": 854312.9 }
}
```

### Known limitations

- **No currency override.** Three different ways of passing a currency override were each tried live by the parent Actor's own README and every one was rejected by the API's own input validation — prices reflect a fixed account-level currency this Actor cannot override.
- **Detail and reviews genuinely need different identifiers from the same search result** (full `slug` vs. short `id`) — this is a real API quirk, not an inconsistency in this Actor.
- 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.0015 per `attraction` result (FREE plan; BRONZE/SILVER/GOLD/PLATINUM/DIAMOND get automatic discounts based on your Apify plan). Covers search results, detail rows, and reviews.

# Actor input Schema

## `mode` (type: `string`):

Auto-detected: slug set -> detail, id set -> reviews, otherwise search.

## `ufi` (type: `integer`):

Search mode. Same id space as hotels' dest\_id, e.g. -3414440 for Bangkok. From query resolution or booking-hotel-search-scraper.

## `query` (type: `string`):

Search mode. Resolved to ufi automatically. Ignored if ufi is set.

## `page` (type: `integer`):

Search mode: result page. Reviews mode: review page.

## `limit` (type: `integer`):

Maximum number of items to return.

## `includeDetail` (type: `boolean`):

Fetch full /attractions/{slug} detail for every search result (one extra request per result).

## `maxItems` (type: `integer`):

Search mode: max attractions pushed. Reviews mode: max reviews pushed. Leave empty for all results.

## `slug` (type: `string`):

The FULL slug string from a search result, e.g. "prvajppfwe7k-the-newest-luxury-5-star-bangkok-chao-phraya-dinner-cruise". The short id alone will not resolve.

## `id` (type: `string`):

The SHORT id field from a search result, e.g. "PRvAjpPfwE7K" — not the slug.

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

An option id from the review filter schema, e.g. "5".

## `includeFilters` (type: `boolean`):

Also push one row with the review filter/sort schema before paginating reviews.

## Actor input object example

```json
{
  "page": 1,
  "limit": 20,
  "includeDetail": false,
  "includeFilters": false
}
```

# Actor output Schema

## `dataset` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/booking-attractions-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("romy/booking-attractions-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 '{}' |
apify call romy/booking-attractions-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/booking-attractions-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/PHjzcFFx6BjOzpWbO/builds/D0vWVR24bbkI91J6c/openapi.json
