FazWaz Access Status Scraper
Pricing
from $3.99 / 1,000 results
FazWaz Access Status Scraper
Access-status mode. FazWaz terms require express authorization for content extraction; no applicable permission is recorded, so the runtime writes a policy summary and makes zero source requests or dataset writes.
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
FazWaz Access Status Actor
Current behavior
The official FazWaz Terms and Conditions were rechecked on 2026-09-30 at https://www.lifullconnect.com/legal-notice-fazwaz/. Section 3 prohibits reproducing, compiling, copying, extracting, distributing, transmitting, selling, and reselling site content. No applicable written authorization is recorded. The Actor therefore makes zero source requests, writes SUCCEEDED / SKIPPED_POLICY to the SUMMARY key, and produces no dataset items.
There is no input that can self-attest permission or re-enable collection. The listing parser remains for offline tests only and is not called by the runtime. Diagnostics and failure details are kept in the aggregate summary, never in the dataset. A historical HTTP 403 diagnostic was removed from active dataset storage after an exact external archive; it does not establish live extraction. The saved summary preserves that known zero-row HTTP 403 failure as FAILED / FAILED, with native exit code 1. New default runs report SUCCEEDED / SKIPPED_POLICY, zero requests, and zero rows.
Offline verification
Run npm test, npm run check, and apify validate-schema. These checks do not contact FazWaz or establish current property coverage. Do not use --purge or make a live request without applicable written permission.
Dependency review — October 3, 2026
The production dependency lock has been refreshed within compatible declared ranges. The get-uri dependency uses patched basic-ftp@6.2.1; offline tests cover the Client methods consumed by get-uri, valid listing fields, and the adversarial listing parser case. Source permissions and access gates remain unchanged.
The remaining http-cache-semantics security advisory GHSA-ch52-4w7c-c8xp has no published patched release. It remains present through the Apify/Crawlee request stack. This project does not claim the finding is fixed or unreachable, and the audit remains part of the release limitations.
