Ademe DPE Properties and Details Scraper
Pricing
from $3.99 / 1,000 results
Ademe DPE Properties and Details Scraper
Ademe DPE Properties and Details Scraper — Read bounded public French energy-performance diagnostics from the official ADEME Data Fair dataset, with DPE/GES classes, address, surface, construction, energy-use, emissions, and geolocation fields.
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
14 days ago
Last modified
Categories
Share
This Actor reads bounded rows from the official ADEME Data Fair dpe03existant dataset. It exposes public DPE/GES classes, address, city, surface, construction year, energy use, emissions, property type, validity date, and coordinates. Optional filters are applied locally after fetching a bounded public result page.
It uses no credentials, private endpoint, proxy rotation, challenge solving, or remote Apify operation. Source-backed DPE certificates are the Actor's real property records (the French DPE certificate itself is a diagnostic); access and failure diagnostics are never written as dataset records. A source failure before any record is saved ends the run as status=FAILED, runStatus=FAILED, with a nonzero process exit. Partial source-backed results keep native status=SUCCEEDED and exit zero while runStatus and collectionStatus report PARTIAL. A valid empty response reports status=SUCCEEDED and runStatus=COMPLETED with no dataset rows.
fieldCoverage lists only populated ADEME property fields, excluding Actor metadata. dataQuality.sourceBackedFields and dataQuality.emptyFields are calculated from those fields for each new record. Historical rows retain their original coverage metadata.
Input
Supported filters include city, postal code, department, DPE/GES class, surface bounds, and construction year.
Offline verification
Dependency security
The locked dependency graph overrides basic-ftp with the patched 6.2.1 release. The SDK’s unpatched HTTP cache policy is replaced with the readable local vendor/noncaching-http-policy adapter, which refuses cache reads and writes and forces fresh network responses. This is an explicit removal of caching, not a claimed upstream security patch. Source transports, permission gates and request limits are unchanged. npm run test:dependencies checks cross-user cache isolation, imported stale policy rejection, FTP integration methods and adversarial listing parsing. Cloud builds run npm audit --omit=dev --audit-level=low against the installed production graph.
