Immoweb Properties Scraper

Scrape Immoweb (Belgium's #1 real estate portal) for property listings by operation, property type, and location. Returns rich structured data — title, price, operation (sale/rent), property type, bedrooms, living area m², EPC/energy rating, location, agency details, image URLs, and more.

Features

• Scrape for-sale and for-rent listings across all Belgian property types (houses, apartments, land, garages, offices)
• Filter by postal codes, price range, and minimum bedrooms
• Returns 30+ fields per listing: price, EPC score (A–G), surface m², agency name/logo/phone, GPS coordinates, images, publication dates, flags
• Uses Immoweb's own internal JSON API — clean data, no HTML parsing, no JavaScript rendering needed
• Pay per result — you only pay for property records actually extracted
• Handles 30 results/page with automatic pagination up to maxItems

Input

Field	Type	Default	Description
operation	select	for-sale	for-sale or for-rent
propertyType	select	house	house, apartment, land, garage, office, industry
postalCodes	string	(all Belgium)	Comma-separated Belgian postal codes, e.g. 1000,1030,1050 for Brussels, 9000 for Ghent, 2000 for Antwerp
priceMin	integer	—	Minimum price (EUR)
priceMax	integer	—	Maximum price (EUR)
minBedrooms	integer	—	Minimum number of bedrooms
maxItems	integer	100	Max listings to return (0 = unlimited)
proxyConfiguration	proxy	RESIDENTIAL BE	Apify Residential proxy, Belgium recommended

Output fields

Each record contains:

Field	Description
property_id	Immoweb internal listing ID
title	Listing title
url	Direct URL to the listing
operation	FOR_SALE or FOR_RENT
property_type	HOUSE, APARTMENT, LAND, GARAGE, etc.
property_subtype	MANSION, VILLA, BUNGALOW, STUDIO, etc.
price	Price in EUR
price_old	Previous/crossed-out price (if available)
monthly_charges	For-rent: monthly charges (if set)
price_display	Formatted price string (e.g. €269,000)
bedrooms	Number of bedrooms
rooms	Total room count
living_area_m2	Net habitable surface (m²)
land_surface_m2	Land/plot surface (m²)
epc_score	Energy performance certificate: A/B/C/D/E/F/G
epc_logo_url	EPC certificate image URL
locality	City/municipality
postal_code	Belgian postal code
region	Region (Brussels, Flanders, Wallonia)
province	Province name
latitude	GPS latitude (when available)
longitude	GPS longitude (when available)
agency_name	Agency or seller name
agency_type	AGENCY, PRIVATE, DEVELOPER
agency_logo_url	Agency logo URL
agency_phone	Agency phone number
images	List of large image URLs
image_count	Number of photos
thumbnail	First/preview image URL
features	Dict of notable features (garden, parking, lift, heating, etc.)
publication_date	When the listing was first published
last_modification_date	Last update timestamp
flags	List of listing flags (e.g. new)
has_360_tour	Whether a 360° tour is available
has_virtual_tour	Whether a virtual tour is available
has_video	Whether a video is available
scraped_at	Run timestamp (UTC ISO)

Example input

{
  "operation": "for-sale",
  "propertyType": "apartment",
  "postalCodes": "1000,1030,1050",
  "priceMin": 200000,
  "priceMax": 500000,
  "minBedrooms": 2,
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "BE"
  }
}

Proxy

Apify RESIDENTIAL proxy with country BE is recommended for reliable access. The proxy cost is billed to your Apify run — no external proxy account needed.

Pricing

This actor uses Pay Per Event pricing: you are charged per property record returned. Default ~$2 per 1,000 records.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.