Complete Guide: How to Scrape Immoweb Listings Using Python
Run the Immoweb Scraper Apify Actor from Python and turn immoweb.be searches for houses and apartments into structured rows.

This guide shows how to extract Belgian property listings from immoweb.be with Python: houses and apartments, for sale or for rent, searched by postal code and price, returned as one structured row per listing. The tool is the Immoweb Scraper Apify Actor (reventadata/immoweb-scraper), and you drive it from Python with the official Apify API client.
By the end you will know which inputs the Actor accepts, how a search is split, what a row contains, where its limits are and how to read a run's output. The prerequisites are minimal: Python 3.11 or newer, an Apify account and an API token. Every sample row in this guide comes from a real run of a postal code 9000 search (Gent), copied from its dataset.
TL;DR
- Install
apify-client3.x, setAPIFY_API_TOKEN, and callreventadata/immoweb-scraperwith arun_inputdictionary. - Inputs:
propertyType(houseorapartment),transaction(buyorrent), optionalpostalCodes, optional price limits, and caps on rows and pages. - Output: one row per listing with price, address, living area, bedrooms, EPC label, agency name and photo links. Agency contact fields are added only when
fetchDetailsis on. - Limits: Immoweb pages any one search to 9,960 listings, so a bigger search is split by postal code or by price band.
Prerequisites and setup
You need three things before the first run.
- Python 3.11 or newer. The Apify client for Python 3.x requires it.
- A free Apify account, created with an email address or a GitHub login.
- Your API token, from Settings > API & Integrations in Apify Console.
Install the client and export the token:
pip install -U "apify-client~=3.0"
export APIFY_API_TOKEN="your_apify_token_here"
No scraping code is needed on your side. The Actor reads public pages, with no login, and does the fetching. The Actor is not affiliated with Immoweb.
Understanding Immoweb Scraper
Immoweb is the Belgian real-estate portal. Its search results cover houses and apartments, for sale and for rent, and each result links to a listing page. The Actor reads those public results and returns one row for each listing.
A run takes one propertyType and one transaction. A search across both types therefore needs one run per type, and the rows of the runs are kept in separate datasets. Each run is one search per postal code in postalCodes, one after another, plus a single search when the list is empty.
The Actor keeps each listing id once. If the same listing shows up in two searches or on two pages, the second copy is not pushed again.
Step-by-step walkthrough
Step 1: Open Immoweb Scraper
Open the Immoweb Scraper page on Apify Store. The Try for free button there opens the Actor in Apify Console. This guide calls the Actor from the API, so you only need its name, reventadata/immoweb-scraper.
Step 2: Choose the search
The search is described by these input fields:
propertyType:houseorapartment. Any other value is refused before the run starts.transaction:buyorrent. On a rent search,priceis the monthly rent.postalCodes: a list of four-digit Belgian postal codes such as9000(Gent) or1000(Brussels). An empty list searches all of Belgium in one search.minPriceandmaxPrice: optional limits in EUR. An empty field means no limit, and0is a valid value.maxItems: a cap on rows across all searches. The default is 1000.maxPages: an optional cap on result pages per search, with 60 listings on each page.fetchDetails: off by default. It adds the agency's public contact fields.
Two inputs are checked up front. A minPrice above maxPrice ends the run as failed before any search. A postal code that Immoweb does not know is skipped with an error in the log, so it never returns rows for another area. When that leaves no rows, the run ends as failed.
A search with more matches than Immoweb pages is reported in the log. Splitting it by postal code or by a price band reaches the rest.
For a rent search over two postal codes, the input looks like this:
{
"propertyType": "apartment",
"transaction": "rent",
"postalCodes": ["9000", "1000"],
"maxPrice": 1200,
"maxItems": 50,
"maxPages": 2
}
Step 3: Run it from Python
This script starts the Actor with a search for houses for sale in postal code 9000, waits for it to finish, reads the dataset and prints two lines per listing. The first two input values are the Actor's defaults, so they could be left out.
import os
from apify_client import ApifyClient
# 1. Initialise the client with your token from the environment
client = ApifyClient(os.environ["APIFY_API_TOKEN"])
# 2. Describe the search: houses for sale in postal code 9000, ten rows
run_input = {
"propertyType": "house",
"transaction": "buy",
"postalCodes": ["9000"],
"maxItems": 10,
"maxPages": 1,
}
# 3. Start the Actor and wait for it to finish
run = client.actor("reventadata/immoweb-scraper").call(run_input=run_input)
if run is None or run.status != "SUCCEEDED":
status = run.status if run else "unknown"
raise SystemExit(f"Run did not succeed (status: {status}).")
# 4. Read the rows from the run's default dataset
items = client.dataset(run.default_dataset_id).list_items().items
print(f"Retrieved {len(items)} listings.\n")
# 5. Print two lines per listing, with a price per square metre worked out here
for item in items:
street = " ".join(part for part in (item.get("street"), item.get("houseNumber")) if part)
price, area = item.get("price"), item.get("livingAreaM2")
per_m2 = f"{price / area:,.0f} EUR/m2" if price and area else "no living area"
print(f"{street}, {item.get('locality')} | {price} EUR | {area} m2 | {per_m2}")
print(f" {item.get('propertySubtype')}, bedrooms: {item.get('bedrooms')}, EPC: {item.get('epcLabel')}")
The run reads its results page by page, so keep maxPages small while you test.
Step 4: Read the output
The loop prints one block per listing. Here are the first three listings of the example run's ten rows:
Sint-Denijslaan 359, Gent | 949000 EUR | 188 m2 | 5,048 EUR/m2
VILLA, bedrooms: 3, EPC: C
Wijmenstraat 16, Gent | 248000 EUR | 162 m2 | 1,531 EUR/m2
HOUSE, bedrooms: 3, EPC: F
Koningin Elisabethlaan 76, Gent | 1900000 EUR | 558 m2 | 3,405 EUR/m2
HOUSE, bedrooms: 3, EPC: B
One complete row from the same run, the second listing, follows. imageUrls is cut to its first entry, and agencyLogoUrl and searchUrl are left out.
{
"id": "21993768",
"url": "https://www.immoweb.be/en/classified/house/for-sale/gent/9000/21993768",
"title": "Home with an open-plan feel and a large garden",
"propertyType": "HOUSE",
"propertySubtype": "HOUSE",
"transaction": "FOR_SALE",
"price": 248000,
"currency": "EUR",
"priceLabel": "€248,000",
"priceKind": "residential_sale",
"priceMin": null,
"priceMax": null,
"previousPrice": null,
"monthlyCharges": null,
"bedrooms": 3,
"rooms": null,
"livingAreaM2": 162,
"landAreaM2": 875,
"epcLabel": "F",
"street": "Wijmenstraat",
"houseNumber": "16",
"box": null,
"postalCode": "9000",
"locality": "Gent",
"district": "Gent",
"province": "East Flanders",
"region": "Flanders",
"latitude": 51.0866374,
"longitude": 3.6650255,
"agencyName": "Cornelis Goeman Merelbeke",
"isProject": false,
"projectName": null,
"listingFlag": "new",
"hasVideo": false,
"hasVirtualTour": false,
"lastModifiedAt": "2026-11-16T16:00:20.044Z",
"imageUrls": [
"https://media-resize.immowebstatic.be/classifieds/6ec69a41-f934-4ba7-8e15-cb6597c88d5b/736x736/357beab8464da3e96487a2f79c340ae5.jpg"
],
"agencyId": null,
"agencyType": null,
"agencyPhone": null,
"agencyMobile": null,
"agencyEmail": null,
"agencyWebsite": null,
"contactDetailsFetched": false
}
Working with the API
The Python client calls the Actor and waits for it. client.actor(...).call(run_input=...) returns the run, or None, and the code above checks both before it reads anything. run.status is the Actor's run status, and run.default_dataset_id names the dataset that holds the rows. list_items() returns a page of dataset items, and its items attribute is the list of rows.
The input dictionary uses the field names of the Actor's input schema, so the same dictionary can be saved, reused or built in a loop. A loop over postal codes is the simplest way to cover several areas: one call per code, each with its own maxItems, and the rows appended into one list.
Each row is a flat dictionary. Nested data from the site is already flattened into fields such as street, houseNumber and locality, so no further parsing is needed.
Advanced usage patterns
Price per square metre. The row has no such field. Divide price by livingAreaM2 yourself, skipping rows where either is null, as the loop in Step 3 does.
Rent and charges. On a rent search price is the monthly rent. monthlyCharges is the charges shown beside it, and it stays null where the listing shows none. Add the two only when you want a total.
Agency contacts. Set fetchDetails to true to add the publishing agency's public phone, mobile, email and website. The run is much slower, because each listing's own page is read as well. contactDetailsFetched tells you which rows have those fields filled.
Splitting a large search. Run one search per postal code by listing several in postalCodes, or run one search per price band by setting minPrice and maxPrice in separate runs. Each run keeps its own rows.
Understanding your data
Every row carries these groups of fields. Money is in EUR.
- Price:
priceandpriceLabelgive the asking price as a number and as shown on the listing.priceMinandpriceMaxcarry the range the listing shows, when it shows one.previousPricecarries the old price value, when the listing has one. - Type:
propertyType,propertySubtypeandtransaction, using Immoweb's own categories, such asHOUSEwith subtypeVILLAandFOR_SALE. - Address:
street,houseNumber,box,postalCode,locality,district,provinceandregion, split into fields. - Size:
livingAreaM2,landAreaM2,bedroomsandrooms, as published. - Energy:
epcLabel, the energy performance label, as published. - Agency:
agencyName, plusagencyId,agencyType,agencyPhone,agencyMobile,agencyEmailandagencyWebsitewhenfetchDetailsis on. - Listing:
imageUrls,lastModifiedAt,listingFlag,isProject,projectName,hasVideoandhasVirtualTour.
The ten rows of the example run show these things:
- Every row is a
HOUSEtype listing for sale in postal code 9000, with locality Gent. - The subtype is
HOUSEon 7 rows,VILLAon 1,MANSIONon 1 andAPARTMENT_BLOCKon 1. - EPC labels are C on 4 rows, B on 2, D on 2, A on 1 and F on 1.
- Bedrooms are 3 on 7 rows, and 2, 4 and 6 on one row each.
- Asking prices run from 248,000 to 1,900,000 EUR.
- Carlo Eggermont is the agency on 4 rows and Immo Da Vinci on 2. Vastgoedkantoor IMMO-HOME, Cornelis Goeman Merelbeke, Wolff Real Estate and LE CLAIR are on one row each.
- One row has an empty
title. Four titles end in "...". Titles are in Dutch and in English. box,monthlyCharges,priceMin,priceMax,previousPrice,projectName,agencyId,agencyType,agencyPhone,agencyMobile,agencyEmailandagencyWebsiteare empty on every row.contactDetailsFetchedis false on every row.listingFlagisnewon every row.isProject,hasVideoandhasVirtualTourare false on every row.- The
lastModifiedAtdates fall between 15 and 17 November 2026.
Troubleshooting guide
Zero rows with status SUCCEEDED. The site answered and no listing matched. The run's status message says so. Check the postal code and the type and transaction pair against the Immoweb search page.
Zero rows with status FAILED. The run ends as failed when no row was saved and one of these happened: an input the site cannot use (a postal code it does not know, or a minPrice above maxPrice), or pages that could not be read. The status message gives the reason. Fix the input, or run again later.
Fewer rows than expected. Check maxItems, which caps the rows across all searches, and maxPages, which caps the pages per search. If the run stopped on its run-time limit, the rows already saved are kept and the run log says so.
An empty field on a row. Contact fields are empty unless fetchDetails is on, and the row says so in contactDetailsFetched.
A title that ends in "...". Four titles in the example run end that way. Use id or url to find the listing.
Best practices
Start every new search with maxItems at 10 and maxPages at 1, and read the rows before you raise either cap. Keep one postal code or one price band per run when you need to know which area a row came from. Store the raw rows of each run with its input, so you can see later which search produced which listing.
Compute ratios in your own code and check the inputs before the run. Use fetchDetails only for the listings you will contact, because it makes the run much slower.
Conclusion and next steps
You now have a Python script that runs the Immoweb Scraper for one postal code, reads the rows and prints the price per square metre for each listing. Changing postalCodes, transaction or the price limits gives you a different search with the same script.
For current pricing and details, see the Store page.
Which postal code would you search first? Leave a comment and tell me what you are comparing.
About the author: reventadata builds and publishes data extraction Actors on the Apify Store.
About the author
- Hi, I'm the engineer behind ReventaData. I build pay-per-event Apify Actors that turn public marketplace, classifieds, jobs and real-estate sites into clean, reliable datasets. Here on Hashnode, I share practical tutorials on collecting structured web data with Python and Apify, and on putting it to work: price tracking, lead lists and market analysis. Explore our turnkey scrapers: https://apify.com/reventadata
Comments
Join the discussionNo comments yet. Be the first to comment.




