Funda.nl Property Scraper (Netherlands)

Collect homes for sale (koop) from Funda.nl, the main Dutch property portal. Pick one or more cities and get one clean record per listing: asking price in euros, street address with postcode, living area in m², number of rooms, photos and the listing URL. Built for property investors, agents, valuation analysts and anyone tracking the Dutch housing market.

What you can do with it

• Track asking prices by city. Run the same cities every week and follow asking prices and price per m² in Amsterdam, Rotterdam, Utrecht or any other Funda area.
• Spot new listings. Schedule a daily run and compare listing URLs with the previous dataset to see which homes came on or went off the market.
• Feed a valuation model. Price, area and rooms are typed numbers, ready for a spreadsheet, BI tool or database.
• Build a shortlist. Pull a city's current for-sale stock, filter by price and size in your own tool, and open the listing URLs you like.

Quick start

1. Open the Actor in Apify Console. The form starts with five cities.
2. Keep them, or replace them with the cities you want.
3. Click Start, then download the dataset as JSON, CSV or Excel.

{"cities": ["Amsterdam"], "maxPages": 1, "maxResults": 15}

An empty input ({}) uses the defaults: Amsterdam, Rotterdam, Den Haag, Utrecht and Eindhoven, one results page each, stopping at 50 listings.

Input

Name	Type	Default	What it does
cities	array	Amsterdam, Rotterdam, Den Haag, Utrecht, Eindhoven	Dutch cities or Funda area names to search. Case and spaces don't matter ("Den Haag" works).
maxPages	integer	1	Results pages per city, 1 to 10 (about 15 listings per page).
maxResults	integer	50	Maximum listings for the whole run, 1 to 200.
requestDelaySecs	number	1.0	Pause between results pages, 0.5 to 10 seconds.
proxyUrl, proxyUsername, proxyPassword	string	empty	Optional connection settings. Leave empty to use the Actor's default connection.

Cities are searched in the order you give them; the run stops as soon as maxResults is reached, so later cities may get fewer listings.

Output

One record per listing: url, price_eur, address, city, area_m2, rooms, listing_type, images, source and scraped_at.

Example record (an Amsterdam listing, image list trimmed):

{
  "url": "https://www.funda.nl/detail/koop/amsterdam/appartement-wittgensteinlaan-268/44669476/",
  "price_eur": 585000,
  "address": "Wittgensteinlaan 268, 1062 KG Amsterdam",
  "city": "Amsterdam",
  "area_m2": 88,
  "rooms": 3,
  "listing_type": "koopwoning",
  "images": ["https://cloud.funda.nl/tiara-media/28c92727-b754-4ae1-b07e-cebd2daf719d/6ee80649-a12a-4f41-b64b-6a450d36c2bf?options=width=720"],
  "source": "funda.nl",
  "scraped_at": "2026-11-02T10:15:00+00:00"
}

• price_eur: the asking price as a number (€ 585.000 k.k. becomes 585000), or empty when the listing shows no price.
• area_m2 and rooms: living area and room count as shown on the listing.
• listing_type: always koopwoning (home for sale).
• url: the canonical listing page, without tracking parameters. Use it as a stable key to de-duplicate and to compare runs.
• scraped_at: when the run collected the record (UTC).

Pricing

Current price: $0.0006 per listing plus a $0.00005 start fee, so 1,000 listings cost about $0.60.

You pay for the listings the run saves; the current rates are on the Actor's Pricing tab. Start with one city and maxResults of 15 to see what a run costs on your plan before scheduling larger runs.

Scheduling

Save your input as a task and add a schedule (for example every morning). Each run returns the listings online at that moment with the same fields, so datasets from different days line up. Compare url values between runs to find new and removed homes.

FAQ

How fresh is the data? Each run reads Funda's search results live when it starts. Nothing is cached between runs.

Which cities are supported? Any city or area name Funda's own search accepts. A name Funda doesn't know returns no listings, and the run status says to check the city name.

How many listings can I get? Up to 10 pages per city and 200 listings per run. For more, split the work into several runs, for example one per city.

Does it include rentals or new-build projects? No. It collects homes for sale (koop) only.

Does it open each listing page? No. Records carry the details shown in the search results. Energy label, year built, description and agent details are not included.

What if some pages can't be read? The run saves the listings it did collect and the status names the cities or pages that were skipped. If no page can be read at all, the run fails with a clear message and saves nothing.

Which export formats are available? JSON, CSV, Excel, XML and the other dataset formats Apify offers, or read the dataset from your own code with the Apify API.

For help, contact Apify Support and include the run URL. If this Actor saves you time, a Store review helps keep it maintained; problems go to the Issues tab.