# Immowelt Scraper — Germany Rentals & Purchase (`axery/immowelt-property-scraper`) Actor

Scrape Immowelt.de rental and purchase listings with a full Kaltmiete/Nebenkosten/Heizkosten/Warmmiete price breakdown, energy certificate class, and geo-coordinates.

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

## Pricing

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

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 rental and purchase property listings from **immowelt.de** over plain HTTP — no browser, no login, no cookies.

### What makes this different

**Rent is never collapsed into one number.** German rental listings separate Kaltmiete (base rent), Nebenkosten (utilities) and Heizkosten (heating) — Warmmiete, the sum of all three, is what a tenant actually pays each month. Most scrapers surface only one of these. This Actor keeps all four:

```json
"price": {
  "amount": 2290, "currency": "EUR", "period": "month",
  "cold_rent": 2290, "warm_rent": 2700,
  "utilities_cost": 279, "heating_cost": 131,
  "price_per_sqm": 21.99, "raw": "2.290 €"
}
```

For purchase listings (`distribution: BUY`), only `amount` (asking price) and `price_per_sqm` are populated — the rent-only fields are null, since a purchase has no Nebenkosten/Heizkosten split.

**Energy certificate data.** `energy_class` (the EU A+–H efficiency rating), `heating_system`, `energy_source` and `year_built` come straight from the listing's own certificate — data most scrapers skip entirely.

**Geo-coordinates.** `address.latitude`/`longitude` come from the listing's own map pin, not a geocoding guess.

### How it gets through

Detail pages are gated by TLS fingerprint, the same pattern as this suite's ZipRecruiter Actor: Chrome and Chrome-based fingerprints return HTTP 403, while `firefox133` and `safari17_0` return 200 with the full page. The client pins Firefox deliberately. The search page itself is unguarded under any fingerprint.

There is no JSON search API and no useful JSON-LD on detail pages — the full record lives in a JSON-escaped string assigned to `window["__UFRN_LIFECYCLE_SERVERREQUEST__"]`, which the client decodes with two JSON parses (the outer layer is a JS string literal holding the actual JSON).

### Input

| Field | Type | Notes |
|---|---|---|
| `city` | string | A plain German place name Immowelt recognises, e.g. `berlin`, `muenchen`, `hamburg` — use the plain spelling, not `münchen` with an umlaut. |
| `distribution` | enum | `RENT` (mieten) or `BUY` (kaufen). |
| `estateType` | enum | `APARTMENT` (Wohnungen) or `HOUSE` (Häuser). |
| `maxItems` | integer | See the pagination limit below. |
| `incremental` | boolean | Only listings not seen in previous runs. |
| `proxyConfiguration` | object | Residential recommended as a fallback if Immowelt tightens its fingerprint check further. |

### Known limits

- **No reachable pagination.** Thirteen candidate query parameters (`page`, `p`, `sp`, `cp`, `offset`, `start`, `skip`, and others) all returned the identical first page, and appending `/2` to the URL path returns 410 Gone. One run therefore returns at most the first page Immowelt serves for a given city/distribution/type combination — typically ~25 listings — regardless of how many thousands the market actually holds (a Berlin apartment-rental search reports "6.776 Angebote" but only the first page is reachable over HTTP). To reach a different set of listings, narrow by city or switch distribution/estate type rather than expecting deeper pages from the same query.
- **`floor` is a raw German label**, not normalized — expect values like `EG` (ground floor) or `1. OG` (first floor).
- **Not every listing has an energy certificate on file** — `energy_class` and related fields are null when Immowelt has none to show.

### Local development

```bash
pip install -r requirements.txt
python test_local.py berlin --max 10 --out sample_output.json
python test_local.py muenchen --distribution BUY --max 5
python test_local.py hamburg --estate-type HOUSE --max 5
```

`sample_output.json` in this folder is real output from a live run, kept so the schema can be reviewed without running anything.

# Actor input Schema

## `city` (type: `string`):

A German place name as Immowelt itself would recognise it, e.g. `berlin`, `muenchen`, `hamburg`. Immowelt's own search redirect resolves the exact district/region - use the plain city spelling, not `münchen` with an umlaut.

## `distribution` (type: `string`):

Which market to search.

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

Which property type to search.

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

Maximum listings to return. Immowelt exposes no HTTP-reachable pagination lever, so one run returns at most the first page it serves for this city/distribution/type combination - typically around 25, regardless of how many total listings the market holds. To reach a different set, run again with a narrower city, or with the other distribution/estate type.

## `incremental` (type: `boolean`):

Remember listing ids between runs and return only listings not seen before. You are charged only for the new rows. Ids are stored in this Actor's key-value store under `seen_job_ids`.

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

Apify Proxy settings. Detail pages are gated by TLS fingerprint (handled internally) and, if that ever tightens further, by IP reputation - Residential is the safer default.

## Actor input object example

```json
{
  "city": "berlin",
  "distribution": "RENT",
  "estateType": "APARTMENT",
  "maxItems": 25,
  "incremental": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `listings` (type: `string`):

One row per property: address with geo-coordinates, full price breakdown, rooms, living space, energy certificate class, and photos.

# 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 = {
    "city": "berlin",
    "maxItems": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("axery/immowelt-property-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 = {
    "city": "berlin",
    "maxItems": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("axery/immowelt-property-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 '{
  "city": "berlin",
  "maxItems": 25
}' |
apify call axery/immowelt-property-scraper --silent --output-dataset

```

## MCP server setup

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