# ImmoScout24 Property Listings Scraper (`xtracto/immoscout24-listings`) Actor

Scrape German property listings from ImmoScout24 by city and type: price, living space, rooms, price per m², address with coordinates, agent, energy class and photos. No login, no browser.

- **URL**: https://apify.com/xtracto/immoscout24-listings.md
- **Developed by:** [Farhan Febrian Nauval](https://apify.com/xtracto) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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

## ImmoScout24 Property Listings Scraper

Scrape German property listings from ImmoScout24 by city and property type: price, living space,
rooms, price per m², address with coordinates, energy efficiency class, photos and listing flags.
Ten property types from apartments to retail space. No login, no browser.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `places` | array | — | German place names — `Berlin`, `München`, `Hamburg-Altona`. Resolved to region codes automatically |
| `geocodes` | array | — | Raw ImmoScout24 region codes, if you have them |
| `realEstateTypes` | array | `apartment-rent` | `apartment-rent`, `apartment-buy`, `house-rent`, `house-buy`, `flatshare-room`, `garage-rent`, `garage-buy`, `office`, `store-rent`, `investment` |
| `maxItemsPerSearch` | integer | `200` | One search = one region × one type. 50 listings per request |

### Output

```jsonc
{
  "_input": "Berlin / apartment-rent",
  "_source": "S1-is24-mobile-api",
  "_scrapedAt": "2026-09-12T10:22:04Z",

  "listingId": "153605035",
  "url": "https://www.immobilienscout24.de/expose/153605035",
  "title": "Home & Co – Easy Living | Fully Furnished Living",
  "realEstateType": "apartment-rent", "listingType": "STANDARD",

  "price": 569.0, "currency": "EUR",
  "livingSpaceSqm": 16.0,
  "rooms": 1.0,
  "pricePerSqm": 35.56,

  "addressLine": "Clayallee 336, 14169 Berlin, Zehlendorf",
  "latitude": 52.43719, "longitude": 13.26222,
  "addressIsIncomplete": false,

  "realtorLogoUrl": "https://pictures.immobilienscout24.de/usercontent/….PNG/…",
  "isPrivate": false, "isNewObject": false, "isProject": false,
  "energyEfficiencyClass": "E",
  "liveVideoTourAvailable": false, "listedOnlyOnIs24": true,
  "publishedLabel": "Published today", "tags": [],

  "titlePictureUrl": "…", "pictureCount": 12,
  "page": 1
}
```

### Four things worth knowing

**Price, size and rooms arrive with no labels.** The API returns
`attributes: [{label: "", value: "€569"}, {label: "", value: "16 m²"}, {label: "", value: "1 rms"}]`
— every label an empty string. The order was consistent across 97 real listings, but this actor
matches on the **unit inside the value** (`€`, `m²`, `rms`) rather than the position, because the
one entry that broke the pattern turned out not to be a listing at all.

**Not everything in `results` is a property.** Nine entries in 200 were house-construction group
cards: no `id`, an `isNewHomeBuilder` flag, and a single attribute holding a builder's name. Read
positionally, that puts *"Build with massa haus – Nancy Ehrhard-Richter"* into the price column.
They are skipped, and the run log says how many.

**A missing coordinate is explained, not mysterious.** ImmoScout24 marks addresses the seller left
vague with a literal `(incomplete address)` suffix, and those are precisely the listings with no
`lat`/`lon`. In one Munich run the correlation was exact: 18 incomplete addresses, 0 with
coordinates; 82 complete addresses, 82 with coordinates. `addressIsIncomplete` carries that so an
empty `latitude` reads as a fact about the listing rather than a bug in the scraper.

**There is no agent name in the search response.** The `realtor` object holds a logo URL and a brand
colour — on every listing checked — and nothing else. The agency name lives only on the listing's
own detail page. Rather than emit a permanently-null `realtorName`, this actor ships
`realtorLogoUrl`, which is what the API actually returns.

### The locale is pinned, deliberately

The same listing renders as `€569` / `1 rms` under `en-US` and `569 €` / `1 Zi.` under `de-DE` —
and German number formatting swaps the meaning of `.` and `,`, so `4.115 €` and `€4,115` are the
same number written two incompatible ways. The requests pin `en-US` so the parser has one contract
instead of two. Prices are always euros regardless.

### How it works

Two hosts. `www.immobilienscout24.de/geoautocomplete/v3/locations.json` turns a place name into the
numeric region code the search needs (`berlin` → `1276003001`). `api.mobile.immobilienscout24.de/search`
returns the listings, 50 per page, and answers JSON only for the mobile app's client identifier —
without it the same path returns a `200` with a zero-byte body rather than an error.

### Errors

| `_error` | Meaning |
|---|---|
| `invalid_input` | An empty place name |
| `place_not_found` | The geocode autocomplete matched no region |
| `no_results` | The search ran and this region has none of that property type |
| `blocked` | The API refused, or returned a 200 that was not usable |
| `network_error` | Never reached the server |

If every search fails, the run itself fails rather than reporting success over an empty dataset.

# Actor input Schema

## `places` (type: `array`):

German place names, e.g. Berlin, München, Hamburg-Altona. Each is resolved to an ImmoScout24 region code automatically.

## `geocodes` (type: `array`):

ImmoScout24 region codes if you already have them, e.g. 1276003001 for Berlin. Used in addition to any place names.

## `realEstateTypes` (type: `array`):

Each type is a separate search per region.

## `maxItemsPerSearch` (type: `integer`):

One search is one region and one property type. 50 listings per request.

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

German residential or datacenter proxies both work. Useful for larger runs.

## Actor input object example

```json
{
  "places": [
    "Berlin"
  ],
  "realEstateTypes": [
    "apartment-rent"
  ],
  "maxItemsPerSearch": 200,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

One row per scraped record, stored in the run's default dataset.

# 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 = {
    "places": [
        "Berlin"
    ],
    "realEstateTypes": [
        "apartment-rent"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("xtracto/immoscout24-listings").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 = {
    "places": ["Berlin"],
    "realEstateTypes": ["apartment-rent"],
}

# Run the Actor and wait for it to finish
run = client.actor("xtracto/immoscout24-listings").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 '{
  "places": [
    "Berlin"
  ],
  "realEstateTypes": [
    "apartment-rent"
  ]
}' |
apify call xtracto/immoscout24-listings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,xtracto/immoscout24-listings"
        }
    }
}
```

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/6sZ4ARzRPjcLu5O17/builds/nwPJHTb34ey43iy9l/openapi.json