# Funda.nl Scraper (`one-api/funda-scraper`) Actor

Scrape Funda.nl, the leading Dutch real-estate marketplace. Search homes, apartments, parking, land and berths for sale, for rent or sold by location, Funda geo area, or a funda.nl search URL; pull full listing details, agent/office profiles, and autocomplete Dutch locations.

- **URL**: https://apify.com/one-api/funda-scraper.md
- **Developed by:** [ONE API](https://apify.com/one-api) (community)
- **Categories:** Lead generation, Real estate
- **Stats:** 3 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Funda.nl Scraper

Scrape **Funda.nl**, the leading Dutch real-estate marketplace. Search homes, apartments, parking, land and berths **for sale, for rent or sold**, look up full listing details, fetch estate-agent (makelaar) office profiles, and resolve Dutch locations to Funda geo-identifiers.

### What it does

- **🔎 Search Listings** — three auto-detected modes from one input box:

  - a city / place / neighbourhood / postcode (e.g. `Amsterdam`, `Utrecht`, `1018XS`, `Jordaan`) → search by location
  - a Funda geo-identifier slug — lowercase with a `-` or `/` (e.g. `gemeente-amsterdam`, `provincie-noord-holland`, `amsterdam/jordaan`) → search by area
  - any `funda.nl/zoeken/...` search URL → search by URL

  Deal type (sale / rent / sold), property type, price, bedrooms, rooms, living & plot area, energy label, construction type, sort order and pagination all apply.
- **🏠 Property Details** — auto-detects each input as a listing id (digits) or `funda.nl` URL; returns the full record (price, areas, bedrooms, energy label, coordinates, characteristics, photos, agent contacts).
- **👤 Agent / Office Details** — for each Funda makelaar office id or URL: one profile row (name, affiliation, contact, reviews, employee count).
- **🔍 Autocomplete** — resolve Dutch location names to Funda geo-identifiers you can feed straight back into the Search section's *by area* mode.

### Output

- **One flat dataset row per listing / office / suggestion** — sortable, filterable, CSV-exportable.
- Columns: `Mode`, `Offering`, `Property Type`, `Property ID`, `Address`, `Postcode`, `City`, `Price`, `Bedrooms`, `Rooms`, `Floor Area m²`, `Plot Area m²`, `Energy Label`, `Agent / Office`, `Latitude`, `Longitude`, `Cover Photo`, `Listing URL`.
- Full upstream JSON kept in the `Raw` column for power users.

### Inputs

- Each section is independent — fill only the ones you need.
- Multiple inputs per section: one per line.
- The search filters apply to every Search query.

### Pricing

- Pay per result: **$3 per 1,000 dataset items** — same rate on every Apify plan tier.
- Apify start fee: $0.00005 per run.

### Notes

- Funda serves ~15 listings per page upstream — raise **Pages per search** to fetch more.
- Deal type **Sold / Rented** returns listings with their realised price and sold status.
- Prices are in euros (€).

### Errors

- Failures land in the dataset as rows with `Mode = "ERROR"` and the upstream error message in the `Address` column — nothing is silently dropped.

### Support

Questions or issues? Contact **oneapi.project@gmail.com**.

# Actor input Schema

## `search_inputs` (type: `array`):

Auto-detects each entry and routes to the right `/search/*` endpoint:
• `https://www.funda.nl/zoeken/...` (a funda.nl search URL) → `/search/byurl`
• A Funda geo-identifier slug — lowercase with a `-` or `/` (e.g. `gemeente-amsterdam`, `provincie-noord-holland`, `amsterdam/jordaan`) → `/search/byarea` (get these slugs from the Autocomplete section)
• Anything else — a city, place, neighbourhood or postcode (e.g. `Amsterdam`, `Utrecht`, `1018XS`, `Jordaan`) → `/search/bylocation`

The filters below apply to every search. Each hit returns one row per listing.

## `property_inputs` (type: `array`):

Auto-detects each entry and calls the right endpoint:
• Digits only (e.g. `8050232`) → `/details/byid`
• `https://www.funda.nl/detail/koop/.../` → `/details/byurl`

Each row is one full listing record (price, areas, bedrooms, energy label, coordinates, characteristics, photos, agent contacts). The listing `id` appears in the `Property ID` column of search results.

## `agent_inputs` (type: `array`):

For each Funda estate-agent (makelaar) office, fetch `/agent/details` (one profile row: name, affiliation, contact, reviews, employee count):
• Digits only (e.g. `24131`) → looked up by office id
• `https://www.funda.nl/makelaar/24131-.../` → looked up by URL

Office ids appear in the `Agent / Office` and `Raw` columns of search/details results.

## `autocomplete_inputs` (type: `array`):

Resolve Dutch location names to Funda geo-identifiers via `/autocomplete`. Each row's `Property ID` is the geo-identifier slug you can feed back into the Search section to hit `/search/byarea`. Returns cities, municipalities, neighbourhoods, provinces and postcodes.

## `searchType` (type: `string`):

For sale, for rent, or sold/rented (sold carries the realised price + sold status).

## `propertyType` (type: `string`):

Which Funda category to search. Comma-separated to combine (e.g. `house,apartment`). Leave blank for all.

## `priceRange` (type: `string`):

Format: `min:250000,max:400000` — either half optional. Euros. For rentals this is the monthly rent.

## `bedroomsRange` (type: `string`):

Format: `min:2,max:4` — either half optional.

## `roomsRange` (type: `string`):

Format: `min:3,max:5` — either half optional.

## `floorAreaRange` (type: `string`):

Format: `min:75,max:150` — either half optional.

## `plotAreaRange` (type: `string`):

Format: `min:100` — either half optional. Mainly for houses/land.

## `energyLabel` (type: `string`):

Comma-separated: `A,B,C` (also `A+`, `A++`, … `G`).

## `constructionType` (type: `string`):

New build or resale (existing).

## `sortOrder` (type: `string`):

How to sort search results.

## `pages` (type: `integer`):

How many pages to fetch for each Search query (Funda serves ~15 listings per page upstream).

## `resultCount` (type: `integer`):

Listings requested per Search page (1–75).

## Actor input object example

```json
{
  "search_inputs": [
    "Amsterdam",
    "Utrecht"
  ],
  "property_inputs": [],
  "agent_inputs": [],
  "autocomplete_inputs": [
    "Amsterdam"
  ],
  "searchType": "For_Sale",
  "propertyType": "",
  "priceRange": "",
  "bedroomsRange": "",
  "roomsRange": "",
  "floorAreaRange": "",
  "plotAreaRange": "",
  "energyLabel": "",
  "constructionType": "",
  "sortOrder": "Default",
  "pages": 1,
  "resultCount": 30
}
```

# 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 = {
    "search_inputs": [
        "Amsterdam",
        "Utrecht"
    ],
    "property_inputs": [],
    "agent_inputs": [],
    "autocomplete_inputs": [
        "Amsterdam"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("one-api/funda-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 = {
    "search_inputs": [
        "Amsterdam",
        "Utrecht",
    ],
    "property_inputs": [],
    "agent_inputs": [],
    "autocomplete_inputs": ["Amsterdam"],
}

# Run the Actor and wait for it to finish
run = client.actor("one-api/funda-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 '{
  "search_inputs": [
    "Amsterdam",
    "Utrecht"
  ],
  "property_inputs": [],
  "agent_inputs": [],
  "autocomplete_inputs": [
    "Amsterdam"
  ]
}' |
apify call one-api/funda-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,one-api/funda-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/NHCdGx1bjcNXy194n/builds/BsdhZJpmXofPHErST/openapi.json