Booking.com Stay Details Properties and Details Scraper

CSV rank: 976. Store listing: 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 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

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. 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.