Anjuke New Home Properties and Details Scraper

This Actor contains a parser for public Chinese Anjuke new-home development pages, including project names, location, developer, property type, pricing, area, room fields, and media when present. Anjuke's current user agreement requires prior written permission for automated collection and copying of platform data. The Actor therefore makes zero source requests by default, finishes SUCCEEDED with collectionStatus: SKIPPED_POLICY, and writes no dataset rows. Its checkbox is an operator attestation, not permission.

The run summary uses only SUCCEEDED or FAILED for status and runStatus; it includes exitCode, failureCount, and bounded failureDetails. A valid empty source response succeeds without a placeholder row. A source or parsing failure with no real development rows is FAILED with a nonzero native exit; if a later request or storage write fails after a real row was saved, the run remains SUCCEEDED with collectionStatus: PARTIAL and a successful native exit. Policy, HTTP, redirect, challenge, parse, and storage diagnostics stay in the OUTPUT key-value summary and never become dataset rows.

Dataset rows require an Anjuke HTTPS project URL and at least one substantive development fact in addition to a name. Title-and-link-only candidates are rejected and summarized as failures rather than emitted as property records.

npm test
npm run lint
npx apify validate-schema

Do not enable collection without current written permission from Anjuke/58.com. If permission is obtained, use only the exact HTTPS Anjuke URLs it covers. The Actor refuses off-site redirects and rejects non-Anjuke input URLs. Parser tests use synthetic fixtures and are not live-source evidence.

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.