# Funda Scraper — Netherlands Real Estate Listings (`axery/funda-property-scraper`) Actor

Scrape Funda.nl property listings: address, price, property type and photos, via a two-step search-then-detail crawl over plain HTTP.

- **URL**: https://apify.com/axery/funda-property-scraper.md
- **Developed by:** [Axery](https://apify.com/axery) (community)
- **Categories:** Real estate, Automation, Integrations
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.01 / 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.
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 Property Scraper (Netherlands)

Scrapes property listings from **funda.nl** over plain HTTP — no browser, no login.

### Two-step scrape, same pattern as Bayt in this suite

Funda's search page carries a JSON-LD `ItemList` of listing URLs, but no price or address. Each listing's own page carries a full schema.org `Product` block. This Actor fetches both: the search page for the URL list, then each listing page for the complete record — one listing costs two HTTP fetches, reflected honestly in the per-item charge.

### What you get per listing

```json
{
  "listing_id": "44563617",
  "property_type": "Appartement",
  "address": { "street": "Jan Evertsenstraat 149-1", "city": "Amsterdam", "region": "Noord-Holland" },
  "price": { "amount": 425000.0, "currency": "EUR" },
  "photo_count": 6
}
```

`property_type` is Funda's own Dutch classification (`Appartement`, `Woonhuis`, `Herenhuis`, ...) — Funda's JSON-LD gives it as the first element of a two-item `@type` array (`["Appartement", "Product"]`), which this Actor pulls out directly rather than collapsing to the generic `Product` type.

### Input

| Field | Type | Notes |
|---|---|---|
| `areas` | array | Funda area slugs: city, neighbourhood or region (`amsterdam`, `rotterdam-centrum`). |
| `listingType` | enum | Buy (`koop`) or rent (`huur`). |
| `maxItems` | integer | Per area. `0` = unlimited, bounded by pagination depth. |
| `incremental` | boolean | Only listings not seen in previous runs. |
| `proxyConfiguration` | object | Datacenter is normally enough — no anti-bot layer encountered. |

### Known limits

- **Two fetches per row**, like Bayt in this suite — the cost of a complete record instead of a URL list.
- **No floor area or room count.** schema.org's generic `Product`/`PostalAddress` vocabulary doesn't carry Funda's floor-area or bedroom-count fields; only what's shown above is available from this JSON-LD alone. A future detail-page HTML parse could add it if needed.
- **No postal code on most listings** — Funda's JSON-LD often omits it even when the street address is present.

### Local development

```bash
pip install -r requirements.txt
python test_local.py amsterdam --max 20 --out sample_output.json
python test_local.py utrecht --rent --max 10
```

`sample_output.json` in this folder is real output from a live run, kept so the schema can be reviewed without running anything.

# Actor input Schema

## `areas` (type: `array`):

One or more Funda area slugs (city, neighbourhood or region), e.g. amsterdam, utrecht, rotterdam-centrum. Matches what Funda's own search box would send for a place name.

## `listingType` (type: `string`):

Whether to search for-sale or for-rent listings.

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

Maximum listings to return per area. Set to 0 for unlimited, bounded by Funda's own pagination depth.

## `incremental` (type: `boolean`):

Remember listing ids between runs and return only listings not seen before. You are charged only for the new rows. Ids are stored in this Actor's key-value store under seen\_listing\_ids.

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

Apify Proxy settings. Funda showed no anti-bot layer in testing, so Apify's automatic proxy selection is normally sufficient.

## Actor input object example

```json
{
  "areas": [
    "amsterdam"
  ],
  "listingType": "koop",
  "maxItems": 100,
  "incremental": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `listings` (type: `string`):

One row per property listing.

## `coverage` (type: `string`):

What the run asked for versus what it returned.

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

// Run the Actor and wait for it to finish
const run = await client.actor("axery/funda-property-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 = {
    "areas": ["amsterdam"],
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("axery/funda-property-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 '{
  "areas": [
    "amsterdam"
  ],
  "maxItems": 100
}' |
apify call axery/funda-property-scraper --silent --output-dataset

```

## MCP server setup

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