28HSE Properties and Details Scraper

Collects public buy and rent listings from 28Hse and follows each listing to its public detail page. The parser combines the page’s Schema.org data with visible detail tables, so rows include the same fields shown to a browser visitor instead of only the sparse JSON-LD summary.

Detailed rows include the listing reference, asking-price text and numeric price when available, gross and saleable areas with price per square foot, estate and unit details, floor range, room and bathroom counts, orientation, estate age and development profile, primary and secondary school networks, property features, listing dates and views, agent company and contact credentials, nearby places and walking times, recent estate transactions, and gallery photos or floor plans. Negotiable asking prices remain text and are not converted to zero. areaSqFt remains an alias for saleable area for compatibility.

The actor uses public 28Hse HTML pages. It does not log in, contact agents, submit forms, or call private APIs. Set includeDetails to false only when a compact index of listing URLs is preferred; its default is true. maxPages and maxProperties bound search-page and detail-page requests.

Local run

npm install
npm test
apify validate-schema .actor/input_schema.json
apify validate-schema .actor/dataset_schema.json
apify run --input '{"startUrl":"https://www.28hse.com/buy","maxProperties":10,"maxPages":1,"includeDetails":true,"requestDelayMs":150}'

Only property records successfully extracted from a listing or detail page are written to the default dataset. A failed detail request is logged and counted in OUTPUT_SUMMARY, but does not create a diagnostic or placeholder row. A run with some real property records finishes with status: SUCCEEDED, runStatus: PARTIAL, collectionStatus: PARTIAL, and expectedExitCode: 0, even when other detail requests fail; a failure with no real records reports FAILED statuses and expected exit code 1. A valid search with no matching listings completes successfully with an empty dataset. A clean run reports status: SUCCEEDED, runStatus: COMPLETED, collectionStatus: COMPLETED, and expectedExitCode: 0. The expected exit code is the Actor's intended process outcome; it does not claim evidence of a previously observed native process exit.

OUTPUT_SUMMARY.itemCount and its detail counters describe the current run. They are not cumulative counts of all rows already stored in the default dataset.

Runtime dependency remediation

Batch input and JSON storage use the documented Apify REST API and isolated local JSON storage, with environment-only credentials, bounded requests, no platform redirects, and no automatic dataset-POST retry. The Actor does not import the full Apify/Crawlee SDK. Source collection rules and authorization gates are unchanged. This adapter does not provide request queues, proxies, browser automation, encrypted input fields, or long-running system-event migration. Those capabilities are not used by this implementation.