# Funda.nl Search Scraper (`javiereaw/funda-nl-search-scraper`) Actor

Dutch real estate search on funda.nl (Netherlands). Homes to buy or rent: price as a number and as published, address, postcode, city, living area, rooms, bedrooms, construction year, energy label, property type, broker ID. Search by city and price, or from a funda URL. An empty run is free.

- **URL**: https://apify.com/javiereaw/funda-nl-search-scraper.md
- **Developed by:** [Javier Jimenez](https://apify.com/javiereaw) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 75.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 results

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/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 Search Scraper

Searches [funda.nl](https://www.funda.nl), the Dutch real-estate portal, by city, price and
listing type, and returns the listings it finds.

It reads the public pages the same way a browser does — no headless browser and no private
search API — so a run is quick and there is nothing to time out or fall out of sync with.
New-build listings, which write their measurements as "ca. 67 m²", are parsed too rather than
skipped. You are charged per listing returned, so a search that finds nothing costs nothing.

### Input

| Field | Type | Description |
|---|---|---|
| `location` | string | Dutch city to search in, e.g. `amsterdam`. Ignored if `searchUrls` is set. Default `amsterdam`. |
| `operationType` | string | `buy` (koop) or `rent` (huur). Default `buy`. Ignored if `searchUrls` is set. |
| `minPrice` | integer | Lower bound of the asking price, in euros. Optional. |
| `maxPrice` | integer | Upper bound of the asking price, in euros. Optional. |
| `searchUrls` | array | Optional. Exact funda.nl search-result or single-listing URLs, as plain strings or `{"url": "..."}` objects. Overrides the fields above. |
| `maxItems` | integer | Maximum number of listings to return. Default `20`. |

Press Start with the defaults and it searches Amsterdam for properties for sale. Calling the
actor with a genuinely empty input (no `location` and no `searchUrls`, e.g. via the API) fails
fast with a clear message instead of guessing a destination.

### Output

One item per listing.

| Field | Description |
|---|---|
| `url` | Link to the listing. |
| `address` | Street name and house number. |
| `city` | City. |
| `postalCode` | Dutch postal code, `null` if funda didn't expose it for this listing. |
| `price` | Asking price in euros as a number, `null` when the listing says "price on request". |
| `priceText` | Price exactly as funda shows it, including cost conditions. |
| `livingArea` | Living area in m². |
| `rooms` | Total number of rooms. |
| `bedrooms` | Number of bedrooms, when funda breaks it out separately. |
| `builtText` | Construction date exactly as funda publishes it: an exact year or a period (e.g. "1931-1944"). |
| `yearBuilt` | Exact year of construction as a number, `null` when funda only gives a period (see `builtText`). Never guessed from a period. |
| `energyLabel` | Dutch energy label (A–G), `null` if not available. |
| `propertyType` | Kind of house or apartment. |
| `brokerId` | Numeric id of the listing agency on funda.nl, `null` if not found. See Limits for why this is the only broker field. |

### Pricing

Pay per result: $0.004 per listing actually written to the dataset. Nothing is charged for a
search that returns zero listings, and the run respects whatever spending cap you set.

### Data source and limits

- Source: the public HTML of funda.nl, read with an HTTP client that identifies itself as
  Chrome. No headless browser, and no use of funda's internal search API.
- Rate: a few seconds between requests, one session reused across a run.
- The date a listing first went online, and the agency's name and contact details, are hidden by
  funda from every anonymous visitor on every listing — this is a limit of the source, not a
  parsing gap. Neither field is returned. `brokerId`, a numeric id visible in the listing's
  "report this ad" link, is the only honest way to tell listings from the same broker apart.
- No personal data of individual real-estate agents (name, phone, email) is collected.
- If funda ever starts blocking these requests, the run reports an unreachable-source error
  and does not charge, rather than guessing.
- If a single listing fails to parse, it's skipped and counted, and the run continues with the
  rest — the status message reports how many were skipped. If more than 20% of the requested
  listings fail to parse, the run fails instead: at that point it's not one odd listing, funda's
  page layout has likely changed.

### Support

If a run fails or a field comes back wrong, open a ticket in the **Issues** tab of this Actor: it is the only channel where the author can see your report, and it gets answered. Every failed run carries a status message that says what went wrong. Results are pushed in a single batch at the end of the run, so a run that fails is never charged.

# Actor input Schema

## `location` (type: `string`):

Dutch city to search in, e.g. 'amsterdam' or 'den haag'. Ignored if searchUrls is set.

## `operationType` (type: `string`):

Whether to search properties for sale or for rent. Ignored if searchUrls is set.

## `minPrice` (type: `integer`):

Lower bound of the asking price, in euros. Leave empty for no minimum.

## `maxPrice` (type: `integer`):

Upper bound of the asking price, in euros. Leave empty for no maximum.

## `searchUrls` (type: `array`):

Optional. One or more funda.nl URLs, either search result pages (e.g. https://www.funda.nl/zoeken/koop?selected\_area=\["amsterdam"]) or single listing pages (.../detail/koop/...). Overrides location, operationType, minPrice and maxPrice. Accepts plain strings or {"url": "..."} objects.

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

Maximum number of listings to return. Only listings actually written to the dataset are charged for.

## Actor input object example

```json
{
  "location": "amsterdam",
  "operationType": "buy",
  "searchUrls": [],
  "maxItems": 20
}
```

# Actor output Schema

## `resultados` (type: `string`):

Items del dataset por defecto.

# 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 = {
    "location": "amsterdam",
    "searchUrls": [],
    "maxItems": 20
};

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

# Prepare the Actor input
run_input = {
    "location": "amsterdam",
    "searchUrls": [],
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("javiereaw/funda-nl-search-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",
  "searchUrls": [],
  "maxItems": 20
}' |
apify call javiereaw/funda-nl-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,javiereaw/funda-nl-search-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 <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/QXDdfodi5VmafnMdG/builds/whtfMRCIkaeTbAQy0/openapi.json