Figaro Immobilier Properties and Details Scraper
Pricing
from $3.99 / 1,000 results
Figaro Immobilier Properties and Details Scraper
Authorization-gated Figaro Immobilier Actor. Runs make zero source requests by default, write no diagnostic dataset records, and report canonical native run status in OUTPUT_SUMMARY.
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
18 hours ago
Last modified
Categories
Share
This Actor is currently authorization-gated. Figaro Immobilier's current Conditions générales d’utilisation, Article 6, require prior written authorization for automated collection of site content for commercial purposes and restrict extraction or storage of database content. No applicable written authorization is recorded.
Each run writes only an OUTPUT_SUMMARY with SUCCEEDED / SKIPPED_POLICY, zero source requests, zero property rows, and a WRITTEN_PERMISSION_REQUIRED policy code. The dataset contains property listings only; no diagnostic or dummy records are pushed. The parser and normalization modules remain dormant and are not called by the Actor.
Output
- Default dataset: empty while collection remains policy-gated.
- Key-value store:
OUTPUT_SUMMARY, including canonicalstatus,runStatus, and aggregate counts. - A source failure with no saved property rows is
FAILED/FAILED; real rows saved before a later failure keep nativeSUCCEEDED/PARTIALstatus. A clean authorized run isSUCCEEDED/COMPLETED.
Local development
Do not enable source collection based on an operator checkbox or self-attestation. Reassess the current terms and implement any authorized collection only after applicable written permission is documented.
Runtime storage and dependencies
The runtime uses Node.js HTTPS fetch and Apify’s documented default Dataset/KVS REST APIs. It no longer includes the unused Apify SDK/Crawlee HTTP caching stack. JSON input and records are supported; the platform provides the run token and default storage IDs through environment variables. Credentials are sent only in the Authorization header to api.apify.com. Storage redirects are refused. Dataset writes are not retried after uncertain failures, to prevent duplicates; read and idempotent summary writes may retry once. Local verification uses APIFY_LOCAL_STORAGE_DIR and preserves existing dataset rows. Source permission and access requirements still apply.
