# Funda.nl Scraper — Dutch Property Listings | No Proxy (`bovi/funda-listings`) Actor

Scrape Funda.nl Dutch real estate listings. Returns price, address, city, rooms, area, energy label, construction year, is\_auction flag, coordinates and photos. No proxy needed. Pay per listing.

- **URL**: https://apify.com/bovi/funda-listings.md
- **Developed by:** [Vitalii Bondarev](https://apify.com/bovi) (community)
- **Categories:** Real estate, Lead generation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.26 / 1,000 funda.nl scraper — dutch property listings | no proxies

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## Funda.nl Scraper — Dutch Property Listings | $1.50/1K | No Proxy

For Dutch property investors, housing analysts, and real estate platforms who need structured data from Funda — the Netherlands' dominant portal with 95%+ of all residential listings.

**$1.50 per 1,000 listings**. First ~10 listings free for trial runs.

Scrape Dutch real estate listings from **Funda.nl** — the Netherlands #1 property portal. Extract structured data from any search URL: price, address, area, rooms, energy label, coordinates, and photos.

**No proxy required.** No authentication. Pay per listing.

### What you get

Each listing record includes:

| Field | Description |
|---|---|
| `listing_id` | Funda global object ID |
| `title` | Full address title |
| `description` | Listing description text |
| `price` | Display price (e.g. "€ 450.000 k.k.") |
| `price_numeric` | Numeric price in EUR |
| `currency` | Always `EUR` |
| `address` | Street address |
| `city` | City name |
| `postcode` | Dutch postcode (e.g. "1053 DM") |
| `province` | Province (e.g. "Noord-Holland") |
| `neighborhood` | Neighborhood name |
| `bedrooms` | Number of bedrooms |
| `bathrooms` | Number of bathrooms |
| `property_type` | "Apartment", "House", etc. |
| `property_sub_type` | More specific Dutch type |
| `floor_area_m2` | Living area in m² |
| `energy_label` | EU energy label (A–G) |
| `construction_year` | Year built |
| `is_auction` | True if property is auctioned |
| `lat`, `lng` | GPS coordinates |
| `url` | Full Funda listing URL |
| `image_url` | Main listing photo URL |
| `images` | All photo URLs |
| `date_listed` | Publication date (ISO 8601) |
| `scraped_at` | Scrape timestamp (ISO 8601 UTC) |
| `parse_confidence` | Data quality score 0.0–1.0 |
| `warnings` | List of quality issue codes |

### How it works

Funda uses **Nuxt4 SSR** (Vue). Each search page exposes listing URLs via Schema.org `ItemList` (ld+json). Each detail page contains full property data in a dehydrated Nuxt4 state JSON array — no proxy, no JavaScript execution needed.

Flow: search page → extract listing URLs → detail page → parse Nuxt4 state array → normalize.

**2 requests per listing** (search page + detail page). This is normal and expected.

### Input

```json
{
  "searchUrl": "https://www.funda.nl/koop/amsterdam/",
  "maxItems": 50
}
```

**searchUrl** — paste any Funda search URL from your browser (koop/huur, area filters, price filters all work).

**maxItems** — limit total listings (0 = all pages).

### Output sample

```json
{
  "listing_id": 89234512,
  "title": "Kinkerstraat 141-A",
  "price": "€ 450.000 k.k.",
  "price_numeric": 450000,
  "currency": "EUR",
  "city": "Amsterdam",
  "postcode": "1053 DM",
  "province": "Noord-Holland",
  "bedrooms": 2,
  "floor_area_m2": 68.0,
  "property_type": "Apartment",
  "energy_label": "C",
  "construction_year": 1924,
  "is_auction": false,
  "lat": 52.3681,
  "lng": 4.8713,
  "url": "https://www.funda.nl/detail/koop/amsterdam/appartement-kinkerstraat-141-a/89234512/",
  "parse_confidence": 0.95,
  "warnings": []
}
```

### Pricing example

| Run size | Cost |
|---|---|
| 50 listings | ~$0.075 |
| 1,000 listings | ~$1.50 |
| 10,000 listings | ~$15.00 |
| + auction listing | +$2.00/1K |
| + energy-label data | +$0.50/1K |

### FAQ

**Do I need a Funda account or proxy?**
No account, no proxy. Works from Apify cloud IPs. Use `/en/` URLs for English results.

**What output formats are available?**
JSON, CSV, Excel, XML — all via Apify dataset download or API.

**Can I filter by huur (rental) or only koop (sale)?**
Paste any Funda search URL — both `/koop/` (sale) and `/huur/` (rental) URLs work.

**What if it returns empty results?**
Check that your `searchUrl` is a valid Funda search URL (e.g. `https://www.funda.nl/koop/amsterdam/`). The actor logs the issue and exits cleanly with 0 results rather than crashing.

### Why this actor vs. competitors

| Feature | This actor | epctex/funda-scraper ($3/1K) | Typical Funda scraper |
|---|---|---|---|
| parse\_confidence field | Yes | No | No |
| Energy label (EU A–G) | Yes | No | Rarely |
| Construction year | Yes | No | Rarely |
| is\_auction flag | Yes | No | No |
| GPS coordinates | Yes | Yes | Sometimes |
| Source: Nuxt4 embedded state | Yes (stable) | DOM | Usually DOM |
| Price per 1K listings | $1.50 | $3.00 | varies |

Works with both Dutch (`/koop/`, `/huur/`) and English (`/en/`) Funda URLs.

**EU compliance note:** Netherlands has strict energy efficiency disclosure requirements. The `energy_label` field makes this actor useful for PropTech and investment firms tracking EU Green Deal compliance.

### parse\_confidence

Every listing includes a `parse_confidence` score (0–1). Score < 0.8 means one or more critical fields are missing — check the `warnings` array before relying on those records.

### Use with AI agents (MCP)

Tag: `MCP_SERVERS`. Returns clean JSON — drop into any n8n / Make / LangChain workflow without post-processing.

```json
{
  "mcpServer": "https://mcp.apify.com/?tools=bovi/funda-listings"
}
```

### Competitive edge

- `parse_confidence` field on every record (no competitor has this)
- Extracts from Nuxt4 embedded state — not brittle CSS selectors
- Energy label, construction year, GPS coordinates included
- `is_auction` flag for high-intent investor filtering
- No proxy COGS — clean from Apify cloud IPs

### Pricing

Pay-Per-Event (PPE):

| Event | Price |
|---|---|
| `listing-item` (primary) | **$1.50 / 1,000 listings** |
| `auction-listing` (premium) | **$2.00 / 1,000 auction listings** |
| `energy-label-data` (premium) | **$0.50 / 1,000 labelled listings** |

Auction listings and energy-labelled listings each fire their respective premium event in addition to the base charge. You only pay for actual results returned.

### Integrations

Built for Dutch property investors and housing analysts tracking Funda listing prices, specs, and market availability — the JSON/dataset output drops into the tools you already run, no glue code:

- **n8n / Make / Zapier** — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: [n8n](https://docs.apify.com/platform/integrations/n8n), [Make](https://docs.apify.com/platform/integrations/make), [Zapier](https://docs.apify.com/platform/integrations/zapier).
- **Webhooks** — fire your own endpoint the moment a run finishes, to push results straight into your pipeline ([docs](https://docs.apify.com/platform/integrations/webhooks)).
- **MCP server** — expose this actor as a tool to Claude, Cursor, or any [MCP client](https://mcp.apify.com) so an AI agent can pull this data mid-conversation ([guide](https://blog.apify.com/how-to-use-mcp/)).
- **API & SDKs** — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all [Apify integrations](https://apify.com/integrations).

# Actor input Schema

## `searchUrl` (type: `string`):

Full Funda search URL to scrape. Example: https://www.funda.nl/koop/amsterdam/ or https://www.funda.nl/koop/rotterdam/?selected\_area=\["rotterdam"]\&price="0-500000"

## `maxItems` (type: `integer`):

Maximum number of listings to return (0 = no limit, scrapes all pages). Default 50.

## `proxyConfiguration` (type: `object`):

Optional Apify proxy. Funda works without proxy from Apify cloud IPs. Only needed if you observe 403 errors.

## Actor input object example

```json
{
  "searchUrl": "https://www.funda.nl/koop/amsterdam/",
  "maxItems": 50,
  "proxyConfiguration": {}
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset containing Funda Listings records (title, price, price\_numeric, address, city, bedrooms, floor\_area\_m2, property\_type, energy\_label, url, date\_listed, parse\_confidence).

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchUrl": "https://www.funda.nl/koop/amsterdam/",
    "maxItems": 50,
    "proxyConfiguration": {}
};

// Run the Actor and wait for it to finish
const run = await client.actor("bovi/funda-listings").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchUrl": "https://www.funda.nl/koop/amsterdam/",
    "maxItems": 50,
    "proxyConfiguration": {},
}

# Run the Actor and wait for it to finish
run = client.actor("bovi/funda-listings").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 '{
  "searchUrl": "https://www.funda.nl/koop/amsterdam/",
  "maxItems": 50,
  "proxyConfiguration": {}
}' |
apify call bovi/funda-listings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bovi/funda-listings"
        }
    }
}

```

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 <APIFY_API_TOKEN>` 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/rsgQmbfFE56dU1M4N/builds/dqEhcWBwfVWacfp7f/openapi.json