# Immoweb Scraper — Belgium Property, Prices & Agencies (`logiover/immoweb-scraper`) Actor

Scrape Immoweb, Belgium's largest property portal: sale price or monthly rent with charges, bedrooms, habitable and land surface, EPC rating, full address with coordinates and the listing agency. Sale and rental. Keyless. JSON, CSV or Excel.

- **URL**: https://apify.com/logiover/immoweb-scraper.md
- **Developed by:** [Logiover](https://apify.com/logiover) (community)
- **Categories:** Real estate, Lead generation
- **Features:** Limited permissions
- **Stats:** 40 total users, 0 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 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?

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

## Immoweb Scraper — Belgium Property, Prices & Agencies

![Apify Actor](https://img.shields.io/badge/Apify-Actor-00A67E?logo=apify\&logoColor=white) ![No API key](https://img.shields.io/badge/No%20API%20key-required-2ea44f) ![Pay per result](https://img.shields.io/badge/Pricing-Pay%20per%20result-1C7ED6) ![Export](https://img.shields.io/badge/Export-JSON%20%7C%20CSV%20%7C%20Excel-F59E0B)

**Scrape Immoweb, Belgium's largest property portal: sale price or monthly rent with charges, bedrooms, habitable and land surface, EPC rating, full address with coordinates and the listing agency. Sale and rental. Keyless. JSON, CSV or Excel.**

***

### What does the Immoweb Scraper do?

This Actor turns Immoweb into a structured dataset you can actually work with. You give it a search, it walks the result pages, and it writes one clean row per record into your dataset — ready to export as JSON, CSV or Excel, or to pull straight from the Apify API.

It runs on plain HTTP with no browser and no login, which keeps it fast and cheap, and it works the same on a free account as on a paid one. Every field documented below came from a real verification run of this Actor, so what you read here is what you get.

The current build returns **36 populated fields** per record, of which **26 are present on virtually every row**.

### Who is it for?

- **Analysts** who need Immoweb data as a spreadsheet instead of a browser tab.
- **Operations and research teams** tracking how Immoweb listings change over time.
- **Developers** wiring a live data feed into an internal tool or database.
- **Growth and sales teams** building prospect and market lists from public data.
- **AI teams** assembling structured training or grounding data.

### Use cases

- Export a full Immoweb search into a spreadsheet for analysis.
- Track how prices, volumes or availability move week over week by scheduling the run.
- Feed a dashboard or internal database with a repeatable, structured source.
- Build a market map by running several searches in one job.
- Enrich an existing list by matching on the identifiers in the output.

### Why use this Immoweb Scraper?

- 🔑 **No API key and no login** — nothing to authenticate, nothing to expire.
- 📦 **36 verified fields** — every column below was confirmed against live output.
- 📄 **Real pagination** — it walks the result set instead of returning the first screen.
- 🎯 **Bounded runs** — caps in the input stop the job exactly where you want, so the bill is predictable.
- 💸 **Tiered pay-per-result** — you pay per row, and higher Apify plans pay less per row.
- 📊 **Export anywhere** — JSON, CSV, Excel, HTML, the API, or any Apify integration.

### What data can you extract?

One row per record. These columns come from a live run, with the share of rows that carried a value:

| Field | Type | Typically filled | Description |
|-------|------|------------------|-------------|
| `agencyLogoUrl` | string | 95% | Agency logo url |
| `agencyName` | string | 100% | Agency name |
| `bedroomCount` | number | 100% | Bedroom count |
| `country` | number | 100% | Country |
| `currency` | string | 100% | Currency |
| `district` | string | 100% | District |
| `hasVideo` | boolean | 100% | Has video |
| `hasVirtualTour` | boolean | 100% | Has virtual tour |
| `imageCount` | number | 100% | Image count |
| `imageUrl` | string | 98% | Image url |
| `lastModified` | string | 100% | Last modified |
| `listingFlag` | string | 95% | Listing flag |
| `locality` | string | 100% | Locality |
| `postalCode` | string | 100% | Postal code |
| `priceAmount` | number | 100% | Price amount |
| `priceKind` | number | 100% | Price kind |
| `priceLabel` | number | 100% | Price label |
| `propertyId` | string | 100% | Property id |
| `propertySubtype` | string | 100% | Property subtype |
| `propertyType` | string | 100% | Property type |
| `propertyUrl` | string | 100% | Property url |
| `province` | string | 100% | Province |
| `region` | string | 100% | Region |
| `scrapedAt` | string | 100% | Scraped at |
| `source` | string | 100% | Source |
| `transactionType` | string | 100% | Transaction type |
| `energyCertificate` | string | 23% | Energy certificate |
| `habitableSurfaceSqm` | number | 85% | Habitable surface sqm |
| `landSurfaceSqm` | number | 60% | Land surface sqm |
| `latitude` | number | 88% | Latitude |
| `longitude` | number | 88% | Longitude |
| `previousPrice` | number | 5% | Previous price |
| `roomCount` | number | 3% | Room count |
| `street` | string | 88% | Street |
| `streetNumber` | number | 88% | Street number |
| `title` | string | 50% | Title |

Fields below 90% are genuinely optional at the source — Immoweb does not publish them for every record. An empty value means the source did not show it, not that extraction failed.

### How to use

1. Open the Actor and fill in the search fields — the defaults below are a working example.
2. Set the result cap so the run stops where you want it.
3. Click **Start**, then export from the **Output** tab or pull the dataset through the API.

```json
{
  "propertyType": "house-and-apartment",
  "transactionType": "for-sale",
  "minPrice": 0,
  "maxPrice": 0,
  "minBedrooms": 0,
  "sortBy": "newest",
  "maxResults": 500,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

### Input parameters

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `propertyType` | string | `house-and-apartment` | Which kind of property to search for. |
| `transactionType` | string | `for-sale` | Sale or rental listings. |
| `postalCodes` | string | `–` | Comma-separated Belgian postal codes, e.g. |
| `minPrice` | integer | `0` | Sale price or monthly rent, depending on the transaction. |
| `maxPrice` | integer | `0` | Sale price or monthly rent, depending on the transaction. |
| `minBedrooms` | integer | `0` | Only return properties with at least this many bedrooms. |
| `sortBy` | string | `relevance` | Result order. |
| `maxResults` | integer | `500` | Stop after this many properties. |
| `proxyConfiguration` | object | `–` | Immoweb embeds its listings in the page source; the default datacenter proxy is enough. |

### Tips for best results

- Broad searches return the deepest result sets; very narrow ones run out after a page or two.
- Use the result cap rather than the page cap when you want a predictable bill.
- Schedule the same input daily or weekly to build a history instead of a one-off snapshot.
- Lower the concurrency if you see retries — the source rate-limits aggressive crawling.
- Run several searches in one job instead of one search with a huge page count.
- Empty optional fields are normal; filter on the columns that matter to you after export.
- Deduplicate on the identifier column if you merge several runs together.
- Keep the proxy setting on the default unless the source blocks your region.

### Integrations

Push results straight into **Google Sheets**, **Slack**, **Zapier**, **Make**, **Airtable** or any **Webhook**. You can also **schedule** the Actor and have each run append to the same dataset, which is how you turn a single export into a time series.

### API usage

Replace `<YOUR_TOKEN>` with your Apify API token.

**cURL**

```bash
curl -X POST "https://api.apify.com/v2/acts/logiover~immoweb-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"propertyType": "house-and-apartment", "transactionType": "for-sale", "minPrice": 0, "maxPrice": 0, "minBedrooms": 0, "sortBy": "newest", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true}}'
```

**Python**

```python
from apify_client import ApifyClient

client = ApifyClient('<YOUR_TOKEN>')
run = client.actor('logiover/immoweb-scraper').call(run_input={"propertyType": "house-and-apartment", "transactionType": "for-sale", "minPrice": 0, "maxPrice": 0, "minBedrooms": 0, "sortBy": "newest", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true}})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)
```

**Node.js**

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_TOKEN>' });
const run = await client.actor('logiover/immoweb-scraper').call({"propertyType": "house-and-apartment", "transactionType": "for-sale", "minPrice": 0, "maxPrice": 0, "minBedrooms": 0, "sortBy": "newest", "maxResults": 500, "proxyConfiguration": {"useApifyProxy": true}});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

### Use with AI agents (MCP)

This Actor is reachable through the Apify MCP server, so an AI agent can call it as a tool. Point the agent at `https://mcp.apify.com` and ask it something like *"pull the first 200 listings from Immoweb and summarise them"* — it receives the same structured rows you would get from the UI.

### FAQ

#### Do I need a Immoweb account or API key?

No. The Actor reads publicly available pages only. There is nothing to authenticate and no credentials to rotate.

#### Does it work on the free plan?

Yes. Every feature is available on a free Apify account — nothing is gated behind a paid tier. Pricing is per result, and higher plans simply pay less per row.

#### How many listings can I get in one run?

As many as the search exposes. Raise the page and result caps together; the run stops at whichever limit it reaches first.

#### Why did I get fewer rows than I asked for?

The search ran out of records. That is normal for narrow queries — broaden the search or add more searches to one run.

#### Why are some fields empty?

Immoweb does not publish every attribute for every record. The table above shows how often each field is filled in practice.

#### What export formats are supported?

JSON, CSV, Excel, HTML and RSS from the Output tab, plus the Apify API and any integration you connect.

#### How fast is it?

It is pure HTTP with no browser, so a page of results typically takes a second or two.

#### Can I schedule it?

Yes. Use the Apify scheduler to run it on any interval and append each run to the same dataset.

#### Does it use a proxy?

It routes through Apify Proxy by default. You can switch groups or supply your own proxies in the input.

#### Is the output schema stable?

Yes. Field names and types are fixed, so downstream pipelines will not break between runs.

#### How often is the data refreshed?

Every run reads the live source. There is no cache, so the data is as current as the website itself.

#### What if the site changes its layout?

Open an issue on the Issues tab and it gets fixed — the Actor is actively maintained.

### Is it legal?

This Actor reads only publicly available pages on Immoweb — the same content any visitor sees without logging in. It does not bypass authentication and does not collect private data. You remain responsible for how you use the output: respect the source's terms of service, applicable copyright, and data-protection law such as GDPR where personal data is involved.

This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Immoweb; Immoweb and all other trademarks mentioned here are the property of their respective owners.

### Output example

One row from a real run of this Actor:

```json
{
  "propertyId": "21862570",
  "title": "Renovated 3-bedroom house",
  "propertyUrl": "https://www.immoweb.be/en/classified/house/for-sale/mouscron/7700/21862570",
  "transactionType": "sale",
  "propertyType": "HOUSE",
  "propertySubtype": "HOUSE",
  "priceAmount": 169000,
  "priceLabel": "€169,000",
  "currency": "EUR",
  "priceKind": "Price",
  "monthlyCosts": null,
  "previousPrice": null,
  "bedroomCount": 3,
  "roomCount": null,
  "habitableSurfaceSqm": 156,
  "landSurfaceSqm": 147,
  "energyCertificate": "B",
  "street": "Rue des Tisserands",
  "streetNumber": "15",
  "postalCode": "7700",
  "locality": "Mouscron",
  "district": "Mouscron",
  "province": "Hainaut",
  "region": "Wallonie"
}
```

### Related scrapers

Other Actors from the same collection:

- [Otodom](https://apify.com/logiover/otodom-scraper)
- [reality.idnes.cz](https://apify.com/logiover/reality-idnes-cz-scraper)
- [Lamudi](https://apify.com/logiover/lamudi-philippines-property-scraper)
- [Rightmove](https://apify.com/logiover/rightmove-scraper)

### How much Immoweb data can you extract in one run?

A single run returned **975 rows** in 268 seconds on the example input. That is roughly **218 rows a minute**. Widen the search — more queries, more pages, a broader location — and the same run goes deeper.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Immoweb itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

### 📝 Changelog

#### 2026-11-01

- Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
- README refreshed: independence disclaimer added.
- README refreshed: duplicate "Related scrapers" sections merged.

#### 2026-10-15

- Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
- A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
- A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
- Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
- Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.

#### 2026-09-23

- Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
- Output verified on a live run: 37 columns returned, 86.1% of cells populated.
- Run reliability reviewed: 97.2% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.
- Noted that 1 column(s) came back empty in this sample (`monthlyCosts`); these are under review.

#### 2026-09-01

- Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
- Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
- No change to input, output fields or scraping logic.

#### 2026-08-11

- Maintenance release: refreshed the build and dependencies.
- Re-verified live execution, non-empty structured output and dataset field/type integrity.
- Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.

# Changelog

This Actor's version history is a separate document: https://apify.com/logiover/immoweb-scraper/changelog.md

# Actor input Schema

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

Which kind of property to search for.

## `transactionType` (type: `string`):

Sale or rental listings.

## `postalCodes` (type: `string`):

Comma-separated Belgian postal codes, e.g. "1000, 2000, 9000". Leave empty to search the whole country.

## `minPrice` (type: `integer`):

Sale price or monthly rent, depending on the transaction. 0 disables the filter.

## `maxPrice` (type: `integer`):

Sale price or monthly rent, depending on the transaction. 0 disables the filter.

## `minBedrooms` (type: `integer`):

Only return properties with at least this many bedrooms. 0 disables the filter.

## `sortBy` (type: `string`):

Result order. Newest first is the usual choice when monitoring a market.

## `maxResults` (type: `integer`):

Stop after this many properties. Immoweb renders about 60 per page and the Actor walks pages until the target is met.

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

Immoweb embeds its listings in the page source; the default datacenter proxy is enough.

## Actor input object example

```json
{
  "propertyType": "house-and-apartment",
  "transactionType": "for-sale",
  "postalCodes": "",
  "minPrice": 0,
  "maxPrice": 0,
  "minBedrooms": 0,
  "sortBy": "newest",
  "maxResults": 200,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All records from this run.

# 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 = {
    "propertyType": "house-and-apartment",
    "transactionType": "for-sale",
    "postalCodes": "",
    "minPrice": 0,
    "maxPrice": 0,
    "minBedrooms": 0,
    "sortBy": "newest",
    "maxResults": 200,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("logiover/immoweb-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 = {
    "propertyType": "house-and-apartment",
    "transactionType": "for-sale",
    "postalCodes": "",
    "minPrice": 0,
    "maxPrice": 0,
    "minBedrooms": 0,
    "sortBy": "newest",
    "maxResults": 200,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("logiover/immoweb-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 '{
  "propertyType": "house-and-apartment",
  "transactionType": "for-sale",
  "postalCodes": "",
  "minPrice": 0,
  "maxPrice": 0,
  "minBedrooms": 0,
  "sortBy": "newest",
  "maxResults": 200,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call logiover/immoweb-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,logiover/immoweb-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/m0LEAhkyKSbmcbPnl/builds/mYr1J52qlBhiIjZfE/openapi.json