# Booking.com Stay Details Properties and Details Scraper (`realestateapi/booking-com-staydetails-properties-and-details-scraper`) Actor

Booking.com Stay Details Properties and Details Scraper — source requests require prior express written permission; only verified stay-detail records are emitted.

- **URL**: https://apify.com/realestateapi/booking-com-staydetails-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Stay Details Properties and Details Scraper

CSV rank: **976**. Store listing: [nifty.codes/booking-com-staydetails-scraper](https://apify.com/nifty.codes/booking-com-staydetails-scraper).

This folder is not yet a verified Booking.com stay-detail extractor. The current page parser produces generic page metadata, which the output filter rejects because it is not a source-backed stay record. Until a target-specific parser exists, a page response without a verified stay record is reported as a failure in `OUTPUT_SUMMARY`; it is never added to the dataset.

### Scope

The [Booking.com Terms of Service](https://www.booking.com/content/terms.html) were updated September 15, 2025. Section A15.2 prohibits accessing, monitoring, scraping/crawling, downloading, reproducing, or otherwise using Platform content with automated means for any purpose without prior express written permission. Section A15.3 also warns Booking.com may block systems it suspects of gathering prices or other information. This Actor therefore requires a default-false written-permission confirmation and explicit HTTPS URLs on `booking.com` or `www.booking.com`.

The default-false `contentUseAuthorized` input and explicit HTTPS URL requirements are retained. The checkbox is an operator attestation and does not itself grant permission. The Actor refuses redirects and does not bypass CAPTCHAs, IP blocks, authentication, or paywalls. Only a source-backed record marked `stay_detail` with a non-empty property name and matching Booking.com source URLs can be saved. Failure and policy details remain in `OUTPUT_SUMMARY`, never in the dataset.

### Run status

- `SUCCEEDED / SKIPPED_POLICY`: default behavior; no permission confirmation and zero source requests.
- `SUCCEEDED / COMPLETED`: requested work completed with no failures.
- `SUCCEEDED / PARTIAL`: at least one verified stay record was saved before a later error; native exit code is 0.
- `FAILED / FAILED`: no verified stay record was saved and an operation failed; native exit code is 1.
- `SUCCEEDED / SKIPPED_NO_INPUT`: no valid URLs were supplied and no source requests were made.

The 2026-08-31 active row was a real capture of the Apify Store Markdown page, not a Booking.com accommodation. It was archived outside this Actor folder and removed from the active dataset during the 2026-09-28 local reconciliation. The prior summary said `SUCCEEDED`; the reconciled summary now records `FAILED / FAILED` for the Booking.com stay-data objective, zero valid stay rows, and no current source requests. No source request or Actor run was made during that reconciliation.

### Local checks

```bash
npm test
npm run check
apify validate-schema
```

Without the permission confirmation, it writes `OUTPUT_SUMMARY` with `SUCCEEDED / SKIPPED_POLICY` and zero requests. Offline tests verify the status mapping and that generic metadata cannot enter the dataset. Local source-policy review and the historic-data reconciliation do not establish live extraction capability.

### Dependency security — October 3, 2026

Compatible dependency updates and the patched `basic-ftp` 6.2.1 are locked in `package-lock.json`. Offline regression checks exercise the API used by `get-uri` and bound adversarial listing parsing in a subprocess. The Docker build uses Node 24 and `npm ci --omit=dev --ignore-scripts`; it does not silently re-resolve dependency ranges.

`http-cache-semantics` currently has no published patched version for [GHSA-ch52-4w7c-c8xp](https://github.com/advisories/GHSA-ch52-4w7c-c8xp). It remains a transitive SDK dependency and an unresolved release-security prerequisite. Do not treat closed policy gates or an untested claim of unreachable code as a security fix. Applicable source permission/access and current-build extraction proof are also still required.

# Actor input Schema

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

Explicit HTTPS URLs on booking.com or www.booking.com. There is no default URL.

## `contentUseAuthorized` (type: `boolean`):

Confirm that prior express written permission from Booking.com covers automated access and the intended use of its content. Requests are disabled unless checked.

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

Maximum number of unique pages to inspect after written permission is confirmed.

## `timeoutMs` (type: `integer`):

Maximum time allowed for each public request.

## `userAgent` (type: `string`):

Optional transparent HTTP user-agent string.

## `acceptLanguage` (type: `string`):

Optional language preference for the public HTTP request.

## Actor input object example

```json
{
  "startUrls": [],
  "contentUseAuthorized": false,
  "maxItems": 1,
  "timeoutMs": 30000,
  "acceptLanguage": "en-US,en;q=0.8"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (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("realestateapi/booking-com-staydetails-properties-and-details-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("realestateapi/booking-com-staydetails-properties-and-details-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 realestateapi/booking-com-staydetails-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/booking-com-staydetails-properties-and-details-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/4UbJZRpliRVsxilpg/builds/Bn59XOeod1WGoTETe/openapi.json