# Funda Netherlands Real Estate Scraper (`devilscrapes/funda-netherlands-real-estate-scraper`) Actor Scrape normalized sale and rent listings from Funda.nl, the leading Dutch property portal. Get clean price, living area, energy label, room counts, and photo data per listing while we handle blocks, retries, and fingerprint rotation for you. - **URL**: https://apify.com/devilscrapes/funda-netherlands-real-estate-scraper.md - **Developed by:** [DevilScrapes](https://apify.com/devilscrapes) (community) - **Categories:** Real estate - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing Pay per event This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README
Devil Scrapes mark ## Funda Netherlands Real Estate Scraper **💰 $1.25 / 1 000 results**  ·  pay only for results  ·  no credit card to try *We do the dirty work so your dataset stays clean.* 😈 Scrape normalized sale and rent listings from Funda.nl, the leading Dutch property portal — clean price, living area, energy label, room counts, and photo data per listing.
*** ### 🎯 What this scrapes Funda.nl is the dominant property portal in the Netherlands, and its existing scraper field is crowded but untrusted: `easyapi/funda-nl-scraper` runs 4,870 jobs a month on a 5★ rating built from just 2 reviews, and `ivanvs/funda-scraper` runs 4,975 jobs with 0★ in a crowded field where nobody has earned trust at scale. This Actor mirrors the schema conventions of our other real-estate Actors (idealista, Rightmove, Bayut, Domain.com.au, Suumo) so buyers already comparing markets get the same clean shape here — normalized EUR pricing, m² living area, EU energy-label letters, room and bathroom counts, and photo galleries per listing, for both koop (sale) and huur (rent), backed by page- and listing-level fault isolation and a geo-splash guard neither named incumbent documents. ### 🔥 What we handle for you - 🛡️ **Browser fingerprint rotation** — `curl-cffi` impersonates real Chrome / Firefox / Safari TLS handshakes, rotated across requests, so the target sees a browser, not Python. - 🌐 **Proxy session rotation** via Apify Proxy — fresh session and exit IP on every block, always pinned to a Dutch (`NL`) exit so you never get a wrong-country page silently. - 🔁 **Retries with exponential backoff** on `408 / 429 / 5xx` — up to 5 attempts per page, `Retry-After` honoured. - 🧱 **Page- and listing-level fault isolation** — one blocked page or one bad listing is skipped and logged, never crashes the run. - 🧊 **Clean, typed dataset rows** — Pydantic-validated, ISO-8601 timestamps, `listing_id` always sourced from the URL (never Funda's own occasionally-mismatched internal ID). - 💰 **Pay-Per-Event pricing** — you only pay for results that hit your dataset. No data, no charge. ### 💡 Use cases - **Home-buyer market research** — pull current koop listings for a Dutch city, normalized price-per-m² included, to compare neighborhoods fast. - **Rental market benchmarking** — track huur listing prices and living area across Amsterdam, Rotterdam, and other cities. - **PropTech and real-estate analytics** — feed a clean, deduped listings dataset into a pricing or valuation model. - **Relocation services** — build client-facing property shortlists with energy label and HOA fee data included. ### ⚙️ How to use it 1. Click **Try for free** at the top of the page. 2. Fill in the input form — most fields have sensible defaults. 3. Click **Start**. Output streams into the run's dataset. 4. Export from **Storage → Dataset** as JSON, CSV, or Excel — or fetch via the API. ### 📥 Input | Field | Type | Required | Default | Notes | |---|---|:--:|---|---| | `searchUrls` | `array` | no | None | Direct funda.nl/zoeken/(koop|huur) search URLs to scrape as-is, paginated from their start page. Up to 50. One of… | | `location` | `string` | no | None | City slug (e.g. 'amsterdam'), used when Search URLs is unset. | | `operation` | `string` | no | 'sale' | Sale (koop) vs. rent (huur). | | `maxResults` | `integer` | no | 100 | Cap on rows this run. | | `enrich` | `boolean` | no | True | True: fetch each listing's detail page for the full kenmerken field set (area, rooms, bathrooms, year built, energy… | | `proxyConfiguration` | `object` | no | {'useApifyProxy': True} | No proxy group forced by default (RESIDENTIAL availableCount=0 on FREE tier). The Actor pins country\_code='NL'… | #### Example input ```json { "location": "amsterdam", "operation": "sale", "maxResults": 5, "enrich": true, "proxyConfiguration": { "useApifyProxy": true } } ``` ### 📤 Output Every row is one dataset item. | Field | Type | Notes | |---|---|---| | `listing_id` | `string` | URL-path numeric ID — never the ld+json internal id, which is observed to differ. | | `url` | `string` | Canonical detail URL. | | `operation` | `string` | 'sale' or 'rent', as requested. | | `property_type` | `['string', 'null']` | 'appartement'/'huis' from ld+json type or URL slug prefix. | | `title` | `string` | Street address, e.g. 'Afrikanerplein 5-3'. | | `price` | `['number', 'null']` | Vraagprijs / offers.price. | | `currency` | `string` | Always 'EUR'. | | `price_per_sqm` | `['number', 'null']` | Computed when both price and area\_sqm are known. | | `area_sqm` | `['number', 'null']` | Woonoppervlakte (detail) or card text (summary). | | `plot_area_sqm` | `['number', 'null']` | Perceeloppervlakte, houses only, detail-only. | | `rooms` | `['integer', 'null']` | Aantal kamers, detail-only. | | `bathrooms` | `['integer', 'null']` | Aantal badkamers, detail-only. | | `year_built` | `['string', 'null']` | Bouwjaar, raw string (may be a range), detail-only. | | `energy_label` | `['string', 'null']` | Energielabel, EU EPC letter, detail-only. | | `city` | `string` | Breadcrumb / address.addressLocality. | | `neighborhood` | `['string', 'null']` | Breadcrumb, detail-only. | | `listed_since` | `['string', 'null']` | Aangeboden sinds, raw string, detail-only. | | `hoa_fee` | `['number', 'null']` | Bijdrage VvE, apartments only, detail-only. | | `image_urls` | `array` | photo\[] gallery URLs (empty OK). | | `scraped_at` | `string` | ISO 8601 UTC row-creation timestamp. | #### Example output ```json { "listing_id": "44551250", "url": "https://www.funda.nl/detail/koop/amsterdam/appartement-afrikanerplein-5-3/44551250/", "operation": "sale", "property_type": "appartement", "title": "Afrikanerplein 5-3", "price": 835000.0, "currency": "EUR", "price_per_sqm": 8186.27, "area_sqm": 102.0, "plot_area_sqm": null, "rooms": 3, "bathrooms": 1, "year_built": "1925", "energy_label": "C", "city": "Amsterdam", "neighborhood": "Transvaalbuurt-West", "listed_since": "3 dagen", "hoa_fee": 150.0, "image_urls": [ "https://cloud.funda.nl/valentina_media/232/899/160_1440x960.jpg" ], "scraped_at": "2026-08-13T12:00:00+00:00" } ``` ### 💰 Pricing Pay-Per-Event — you pay only when these events fire: | Event | USD | What it is | |---|---:|---| | `actor-start` | $0.05 | One-off warm-up charge per run | | `result-row` | $0.0012 | Per unique dataset item | Example: 1 000 results at the rates above ≈ **$1.25**. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit. ### 🚧 Limitations v1 covers the Netherlands only. Agent/broker name and phone enrichment, mortgage calculators, new-development ('nieuwbouw') microsites, saved searches/alerts, historical price-change tracking, map/geo-coordinate fields, and postal code are out of scope for v1. year\_built and listed\_since ship as raw strings (Funda's own format, including ranges) rather than normalized values. ### ❓ FAQ **Do I need a Funda account or API key?** No. This Actor scrapes Funda.nl's own publicly listed property data — no login, no API key. **What's the difference between enrich on and off?** Enrich on fetches each listing's detail page for the full field set (rooms, bathrooms, year built, energy label, plot area, HOA fee, neighborhood, listed-since). Enrich off returns summary rows straight from the search results — faster and cheaper, but those detail-only fields come back null. **Why is listing\_id sometimes different from the ID Funda shows elsewhere on the page?** Funda's own detail-page metadata occasionally carries an internal ID that differs from the ID in the page's own URL. We always use the URL-path ID — it's the stable, visible, dedup-safe one. **Can I scrape a specific search (filters already applied)?** Yes — pass your own funda.nl/zoeken/koop or /zoeken/huur URL via Search URLs and we paginate from there. ### 💬 Your feedback Spotted a bug, hit a weird edge case, or need a new field? Open an issue on the Actor's **Issues** tab on Apify Console — we ship fixes weekly and we read every report. ***
Built by **[Devil Scrapes](https://apify.com/DevilScrapes)** 😈 — a small fleet of opinionated public-data Actors. Honest pricing, real engineering, zero fine print.
# Actor input Schema ## `searchUrls` (type: `array`): Direct funda.nl/zoeken/(koop|huur) search URLs to scrape as-is, paginated from their start page. Up to 50. One of Search URLs or Location is required. ## `location` (type: `string`): City slug (e.g. 'amsterdam'), used when Search URLs is unset. ## `operation` (type: `string`): Sale (koop) vs. rent (huur). ## `maxResults` (type: `integer`): Cap on rows this run. ## `enrich` (type: `boolean`): True: fetch each listing's detail page for the full kenmerken field set (area, rooms, bathrooms, year built, energy label, plot area, HOA fee, neighborhood, listed-since). False: summary-only rows from search cards, zero detail fetches. ## `proxyConfiguration` (type: `object`): Defaults to the RESIDENTIAL proxy group. The Actor pins country\_code='NL' internally whenever a proxy is used (never user-configurable) and the datacenter group has no Dutch exits, so an NL pin against it is refused with CONNECT 407. ## Actor input object example ```json { "location": "amsterdam", "operation": "sale", "maxResults": 20, "enrich": true, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `datasetItems` (type: `string`): All dataset items as JSON. ## `datasetItemsCsv` (type: `string`): Same data exported to CSV. ## `datasetView` (type: `string`): Open the run dataset in the Console. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "location": "amsterdam", "operation": "sale", "maxResults": 20, "enrich": true, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }; // Run the Actor and wait for it to finish const run = await client.actor("devilscrapes/funda-netherlands-real-estate-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "location": "amsterdam", "operation": "sale", "maxResults": 20, "enrich": True, "proxyConfiguration": { "useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"], }, } # Run the Actor and wait for it to finish run = client.actor("devilscrapes/funda-netherlands-real-estate-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "location": "amsterdam", "operation": "sale", "maxResults": 20, "enrich": true, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }' | apify call devilscrapes/funda-netherlands-real-estate-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,devilscrapes/funda-netherlands-real-estate-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/r3SD4TwmTI8PFkHe9/builds/8pqQQL5J4jTjjDMux/openapi.json