# Immowelt Property Scraper (Germany) (`scrapyx/immowelt-properties-scraper`) Actor

Scrapes apartment and house listings from Immowelt, Germany's #2/#3 property portal. Search by city, estate type and buy/rent; returns price, address, rooms and floor area from a single search call, with an optional detail pass for full description, features and energy data.

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

## Pricing

from $0.56 / 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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Immowelt Property Scraper (Germany)

Scrapes apartment and house listings from
**[Immowelt](https://www.immowelt.de)** — Germany's #2/#3 property portal
(AVIV Group). ImmoScout24 (Germany's #1) is already flagged in this
portfolio's research as saturated (6+ independent sellers already scrape
it); Immowelt is a different company, untouched here.

Public data only. No login, no cookies, no browser.

### The one thing you need to know before using this

**No JSON data source exists anywhere on this site** — checked in
priority order: no JSON-LD carrying listing fields, no `__NEXT_DATA__`,
no Apollo state, no RSC flight stream. Both search and detail pages are
plain server-rendered HTML with a rich, **stable** `data-testid`
attribute vocabulary — this actor is pure HTML parsing (`selectolax`),
the same tier as `property24-properties-scraper`/`adp-jobs-scraper`
elsewhere in this portfolio.

**There is no HTTP-only pagination.** Immowelt's real "next page" route
is an AJAX endpoint its own `robots.txt` disallows
(`Disallow: /liste/getlistitems`). Every search therefore returns **one
fixed batch** (~30 listings, 40 for houses) — the same situation this
portfolio already solved for `quintoandar-properties-scraper`. Use the
**Cities** list to fan out across multiple places rather than expecting
depth pagination within one city.

### What you get

Three record types share one dataset, told apart by `recordType`.

#### `PROPERTY` — one row per listing

List cards already carry price, address, room count and floor area. Turn
on **Fetch listing detail pages** to also attach `propertyDetail`, which
adds the full description, an itemised features list, energy certificate
data (year built, condition, heating type) and a detailed price breakdown
(notary fees, transfer tax, buyer's commission) — none of which are on
the search results page.

#### `SEARCH_SUMMARY` — one row per (city, estate type, buy/rent) query

How many listings the single batch contained, and `segmentResolved` —
whether the city/type/transaction combination actually matched anything.

#### `ERROR` — one row per input that failed

So every entry in **Cities** maps to at least one output row.

### Input

| Field | What it does |
| --- | --- |
| **Cities** | German city slugs (`berlin`, `muenchen`, `hamburg`) — one search per entry, each returning its own fixed batch |
| **Property type** | apartments or houses — applies to every city |
| **Buy or rent** | applies to every city |
| **Fetch listing detail pages** | adds description/features/energy/price-breakdown (off by default — one extra request per listing) |
| **Max properties per city** | caps how many of the single batch to keep — there is no deeper page to fetch |

#### Example

```json
{
  "cities": ["berlin", "muenchen", "hamburg"],
  "estateType": "wohnungen",
  "transactionType": "kaufen",
  "includePropertyDetails": true
}
```

### Notes on reliability

- **Filters are genuinely honest, a rare case in this portfolio's
  REAL\_ESTATE family**: an unrecognised city answers a clean HTTP 410
  (Gone), and an unrecognised property-type path segment answers a clean
  HTTP 404 — neither silently widens to a national/parent baseline the
  way most other targets in this portfolio's REAL\_ESTATE family do.
- **`?page=N` is completely inert** (verified live: page 1 and page 2
  return byte-identical listing ids) — see "no HTTP-only pagination"
  above for why, and use multiple cities instead.
- **A de-listed property answers a clean HTTP 410** — the search row is
  still emitted, with `propertyDetail: null`.
- **No WAF or bot-mitigation gate was observed** — 8 TLS profiles across
  both surfaces, all clean, cold.

### Output envelope

Every record carries `_input`, `_source` and `_scrapedAt`. Since there is
no upstream JSON object to pass through verbatim (see above), each
`PROPERTY` row's fields are this actor's own explicit extraction from the
page's `data-testid` structure — not a renamed/reshaped copy of a JSON
blob, because none exists.

See [`CRAWLING_METHOD.md`](CRAWLING_METHOD.md) for the full
reverse-engineering trail.

# Actor input Schema

## `cities` (type: `array`):

German city slugs, e.g. 'berlin', 'muenchen', 'hamburg' -- one search per entry, each with its own SEARCH\_SUMMARY row. Immowelt's own pagination endpoint is disallowed by its robots.txt, so each city returns ONE fixed batch of listings (~30, 40 for houses), not a deep crawl -- use more cities for broader coverage. An unrecognised city is reported as segmentResolved=false rather than erroring out the whole run.

## `estateType` (type: `string`):

Applies to every city in this run.

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

Applies to every city in this run.

## `includePropertyDetails` (type: `boolean`):

Also fetch each listing's detail page for the full description, itemised features, energy certificate data and a detailed price breakdown -- none of which are on the search results page. Costs one extra request per listing. Off by default.

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

Cap on how many of the single returned batch to keep (that batch is the whole result set for this city -- there is no deeper page to fetch). Set to 0 for the full batch.

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight at once, across searches and detail fetches. No bot-mitigation gate was observed for this target in recon, so this can be raised more freely than most actors in this portfolio.

## `minRequestInterval` (type: `integer`):

Paces request starts (not held inside a concurrency slot) rather than raw concurrency. Kept small by default as a courtesy -- no request-velocity sensitivity was observed for this target.

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

No WAF or bot-mitigation gate was observed for Immowelt.de in recon. Residential proxy pinned to Germany is still the default, as this portfolio's standard baseline for a single-country public site.

## Actor input object example

```json
{
  "cities": [
    "berlin"
  ],
  "estateType": "wohnungen",
  "transactionType": "kaufen",
  "includePropertyDetails": false,
  "maxItems": 0,
  "maxConcurrency": 5,
  "minRequestInterval": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "DE"
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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 = {
    "cities": [
        "berlin"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/immowelt-properties-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 = { "cities": ["berlin"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/immowelt-properties-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 '{
  "cities": [
    "berlin"
  ]
}' |
apify call scrapyx/immowelt-properties-scraper --silent --output-dataset

```

## MCP server setup

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