# immowelt Scraper - German Property Listings, Prices & Agencies (`listingworks/immowelt-scraper`) Actor

Scrape immowelt.de flats and houses for sale: price, rooms, living area, postcode, city, state and agency. One results page per place, all 16 states by default. No proxy, one flat price per result, no contact details.

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

## Pricing

from $1.50 / 1,000 result items

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

## immowelt Scraper — German property for sale, prices and agencies

immowelt is one of Germany's two big property portals. This Actor turns its
for-sale search results into a clean table: what the property is, what it
costs, where it is, and which agency is selling it.

Press Start. With no location, the Actor walks the sixteen federal states,
largest first — flats, then houses, for each state. The default `maxItems` of
100 stops it after about three searches (Bayern flats and houses, then
Baden-Württemberg flats); set `maxItems` to 1,200 to get all sixteen states.

### Read this first: one page per search

immowelt's `robots.txt` allows its search pages but not the endpoint that
serves page 2 and sorting. This Actor stays on the allowed pages, so **each
search returns one page** — about 30 flats or up to 40 houses — in the site's
default order. There is no page 2, no "newest first", and `postedAfter`
filters only what that page contains.

That makes this Actor a snapshot tool, not a full-inventory crawler. Breadth
comes from places: all sixteen states, flats and houses, come to 32 searches
and about 1,100 listings (with `maxItems` raised to 1,200). Add the large cities and you have a daily
picture of what immowelt puts in front of buyers across Germany.

### What a row looks like

```json
{
  "title": "gemütliche 2-Zimmer-Wohnung in ruhiger Lage im Stadtteil Milbertshofen",
  "property_type": "apartment",
  "listing_type": "sale",
  "price": 349500,
  "currency": "EUR",
  "rooms": 2,
  "living_area_sqm": 60,
  "address": "Christoph-von-Gluck-Platz 13",
  "postal_code": "80807",
  "city": "München",
  "state": "Bayern",
  "agency": "BLAU-WEISS Hausverwaltungen - Immobilien GmbH",
  "posted_at": "2020-03-31T12:03:24.483Z",
  "updated_at": "2026-06-27T09:07:25.181Z",
  "source_url": "https://www.immowelt.de/expose/2416c476-4ec5-424d-b321-bcb7621b123f",
  "external_id": "23U4L2CJRV3U"
}
```

#### `rooms` and `bedrooms`

Property portals in different countries count different things, so this
catalogue keeps the two apart rather than putting whichever number a site
happens to publish into one column. `rooms` is a real room count. `bedrooms`
is a bedroom count. A site that publishes only one of the two leaves the other
out of the row entirely, so you never have to guess which quantity you are
looking at:

| Site | `rooms` | `bedrooms` |
|---|---|---|
| Willhaben (Austria) | yes | not published |
| Immowelt (Germany) | yes | not published |
| Bezrealitky (Czech Republic) | yes, from the `2+kk` layout | not published |
| Immoweb (Belgium) | not comparable, so left out | yes |
| Rightmove (UK) | not published | yes |

Immoweb does publish a `roomCount`, and it is not a room count in the sense the
other countries use: on one Gent search page a 102 m² three-bedroom flat
reported 1 and an 81 m² one-bedroom reported 9. Rather than ship a column that
cannot be compared, this Actor leaves `rooms` out and gives you `bedrooms`.
Rightmove publishes bedrooms and bathrooms and no total room count at all,
which is the British convention.

Agency names are included where immowelt marks the provider as an agency, which
it did for every listing in a 100-row sample. A private owner, or a provider
immowelt labels some other way, gets an empty `agency`, and a proprietor's
personal name is removed from a company name ("Inh. …"). Contact persons, phone numbers and email addresses
are never collected, and image URLs are deliberately not included: immowelt's
terms reserve the platform's content, and this Actor respects that.

### What people use it for

Watching which agencies dominate a city or a state, and at what price level.
Feeding a valuation or comparison tool with a regular German sample it cannot
get from an official API. And checking, day by day, what immowelt's default
ranking shows a buyer in Berlin, Hamburg or Bayern.

### Input

| Field | What it does |
|---|---|
| `propertyType` | `apartment`, `house`, or `both` (the default; flats first, then houses, for each place). |
| `location` | A federal state (`Bayern`, `Nordrhein-Westfalen`), one of immowelt's large cities (`München`, `Köln`, `Hamburg`; `ae/oe/ue` spellings work too), an immowelt place id (`AD08DE6345`), or an immowelt.de search URL for any other place. Leave empty for all sixteen states. |
| `postedAfter` | Keep only listings created on immowelt at or after this date-time (ISO 8601). Filters within the page each search returns; it does not reach further back. |
| `maxItems` | Hard stop, so your bill is predictable. The default of 100 covers about three searches; all sixteen states need about 1,200. |
| `proxyConfiguration` | Off by default. Most runs do not need one. |

Berlin, Hamburg and Bremen are cities and states at once; either name gives
you the city search. The place name in an immowelt URL is decorative — the
place id decides what you get.

### Pricing

$3.00 per 1,000 listings, dropping to $1.50 per 1,000 on higher Apify plans,
plus $0.005 each time a run starts. Platform usage is not passed on to you.

You are charged for rows you actually receive. If you set a maximum charge for
the run, it stops cleanly at that limit instead of overshooting it.

### Scope and limits

Public listings only, from the search results page. Year built is not on that
page, so it is not in the output; the description is there only as a short
teaser and is deliberately not collected. Plot size (`plot_area_sqm`) is
included where the listing gives one, which is usual for houses. Street
addresses appear only when the advertiser publishes one — on the day this
Actor was built, about one listing in five across three sample searches,
ranging from 1 in 20 houses to half of a page of flats; otherwise `address` is
empty and the postcode and city still tell you where it is. "Preis auf
Anfrage" (price on request) listings have an empty `price`.

`posted_at` is the date the listing was created on immowelt, which can be
years ago for long-running offers; `updated_at` is the last change.

On every page this Actor checks that immowelt echoed back the place, the
property type, page 1 and the default order it asked for, and fails the run if
they do not match. An unknown place id fails the run (immowelt answers it with
410 Gone) rather than returning something else and charging you for it.

If immowelt changes its page structure, the run goes red. It does not return
zero rows and report success — a silent scraper is worse than a broken one,
because you find out weeks later.

A run that is blocked or cut short partway also goes red, even though the rows
it did collect are in the dataset and yours to keep. Red here means "this is
not the complete answer", not "you lost the data" — on a schedule, a run that
quietly came back short is the thing you most need to hear about.

Every run also publishes the site's own result count next to the rows it
delivered, so you can see "60 rows of 9,969 the site reports" without going
back to the site to check. That number is what the site says, not a promise
about what one run returns.

### Same data, other countries

Property listings from other sites in this catalogue come back in exactly
this shape, so a parser you write once keeps working when you add a country.

### Support

Open an issue on this Actor with the run ID and your input. Answered within
one business day.

# Actor input Schema

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

Flats, houses, or both (flats first, then houses, for each place).

## `location` (type: `string`):

A German federal state (e.g. Bayern, Nordrhein-Westfalen), one of immowelt's large cities (e.g. München, Köln, Hamburg), an immowelt place id (e.g. AD08DE6345), or an immowelt.de search URL for any other place. Leave empty to walk all sixteen federal states.

## `postedAfter` (type: `string`):

Keep only listings created on immowelt at or after this date-time, e.g. 2026-09-01T00:00:00Z. It filters the listings each search returns; it does not reach further back.

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

Stop after this many listings. Each search returns one page (about 30 flats or 40 houses), so the default 100 covers about three searches; all 16 states (32 searches) need about 1,200.

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

Off by default. Turn on (residential, in the site's country) only if runs start getting blocked with 403/429.

## Actor input object example

```json
{
  "propertyType": "both",
  "location": "",
  "postedAfter": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

All German flats and houses for sale from this run: what each one is, what it costs, and where.

## `pricing` (type: `string`):

The same listings reduced to the fields used for price analysis.

## `agencies` (type: `string`):

The same listings ordered around the estate agency selling them.

## `runReport` (type: `string`):

Pages read, records delivered, errors, and the verdict (ok, degraded or broken).

# 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 = {
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/immowelt-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 = { "proxyConfiguration": { "useApifyProxy": False } }

# Run the Actor and wait for it to finish
run = client.actor("listingworks/immowelt-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 '{
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call listingworks/immowelt-scraper --silent --output-dataset

```

## MCP server setup

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