Fang Properties and Details Scraper
Pricing
from $3.99 / 1,000 results
Fang Properties and Details Scraper
Fang access-status Actor. No applicable written permission is recorded; runtime writes AUTHORIZATION_REQUIRED to RUN_METADATA, emits no dataset rows, and makes zero Fang requests. The retained parser is offline only.
Pricing
from $3.99 / 1,000 results
Rating
0.0
(0)
Developer
Real Estate API
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Current behavior
This Actor is in access-status mode. Fang's public service agreement and copyright declaration were reviewed in Chrome on 2026-09-25. They restrict unauthorized copying, commercial use, and derivative works; no applicable written permission is recorded. The Actor therefore emits one AUTHORIZATION_REQUIRED diagnostic and a SKIPPED_POLICY run summary with zero source requests. Its input schema exposes no way to self-attest or enable scraping.
The community parser remains available for offline regression tests only. The Actor runtime does not call it and does not contact Fang. Policy diagnostics and failures are stored in RUN_METADATA, never in the dataset. The only saved local artifact is historical RUN_METADATA from a 2026-09-23 failed fetch; no community dataset is present. The old summary is preserved and is not current extraction evidence.
New runs use SUCCEEDED / SKIPPED_POLICY with exit code 0 for the no-request policy gate. A completed empty run is SUCCEEDED / COMPLETED; a later failure after saved community rows is SUCCEEDED / PARTIAL; a failure with zero saved rows is FAILED / FAILED with exit code 1.
Offline verification
Run npm test, npm run lint, and apify validate-schema. Synthetic parser tests do not prove current source coverage. Do not use --purge or run a live source request without applicable written permission.
Runtime dependency remediation — 2026-10-03
The full Actor SDK and its unused crawler, HTTP cache, FTP and proxy dependency chains were removed. The batch entrypoint now uses native fetch for the documented Apify dataset and key-value-store APIs, awaits storage acknowledgements, confines the platform credential to api.apify.com, refuses redirects, and uses the official standalone @apify/log logger. The build performs a production dependency audit and stores its exact locked application graph as RUNTIME_DEPENDENCIES. This evidence concerns the application graph, not operating-system packages. Node.js 22 or later is required.
Source permission gates, allowed hosts, advertised extraction scope, and historical storage remain unchanged. A clean dependency audit or a successful closed-gate run does not qualify source extraction. The existing written-authorization and no-retry instructions still apply.
Storage API documentation: https://docs.apify.com/api/v2/dataset-items-post and https://docs.apify.com/api/v2/key-value-store-record-put.
