# Changelog of Funda.nl Scraper - Dutch Real Estate Listings Extractor (`haketa/funda-scraper`) Actor

- **URL**: https://apify.com/haketa/funda-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/haketa/funda-scraper.md

## Changelog

All notable changes to the **Funda.nl Scraper** are documented here.

### 1.1.0 — 2026-11-01

#### Fixed

- **Restored data collection after Funda tightened its DataDome anti-bot wall.** Funda.nl now hard-blocks residential proxies (HTTP 403) and serves a DataDome JS interstitial ("Je bent bijna op de pagina die je zoekt…") to datacenter traffic, so the previous residential/datacenter default returned **0 listings**. The default proxy group is now Apify's **anti-blocking proxy (`UNBLOCKER`)**, which solves the challenge and returns the real server-rendered page. No input fields were renamed — only the default `proxyConfiguration` value changed.

#### Changed

- Raised the per-request timeout to 60s to accommodate the anti-blocking proxy's challenge-solving latency.
- Updated the in-code strategy comment to reflect the DataDome / UNBLOCKER approach.

#### Verified

- Fresh end-to-end run (koop / for-sale, Amsterdam + Rotterdam + Den Haag + Utrecht + Eindhoven + Groningen): paginated across 25+ search-result pages and returned a large, **0%-duplicate** set of listings. Core identity fields — `url`, `address`, `city`, `price`, `priceType`, `listingType`, `livingArea`, `propertyType` — populated at ~100%, with rich extras (`postalCode`, `province`, `rooms`, `bedrooms`, `energyLabel`, `yearBuilt`, `neighbourhood`, `brokerId`, `photos`).
- Rewrote the README to the current field set grounded in the fresh sample, added this changelog, and confirmed the build.
