# Immowelt Scraper - Real Estate Germany (`igolaizola/immowelt-scraper`) Actor

Scrape Immowelt Germany real estate listings for apartments, houses, plots and commercial properties. Search by city or location ID, filter by buy/rent, price, rooms and area, and export clean JSON/CSV data for market analysis, lead generation and price monitoring.

- **URL**: https://apify.com/igolaizola/immowelt-scraper.md
- **Developed by:** [Iñigo Garcia Olaizola](https://apify.com/igolaizola) (community)
- **Categories:** Real estate, Lead generation, Travel
- **Stats:** 94 total users, 57 monthly users, 98.4% runs succeeded, 1 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $0.70 / 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 Scraper - Real Estate Germany

Scrape public property listings from **Immowelt** in Germany and export them as clean data for **market research, lead generation, price tracking, and investment analysis**.

This actor is designed for both:

- **Non-technical users** who want ready-to-download data in Apify.
- **Data teams** that need structured JSON/CSV via API.

### ✅ What does this actor do?

The actor searches Immowelt listing result pages and returns structured records for properties such as:

- Apartments (`Wohnung`)
- Houses (`Haus`)
- Plots (`Grundstueck`)
- Parking / garage
- Commercial categories (selected combinations)

It supports:

- Location search (city / district / postcode style queries)
- Direct property fetch by explicit property IDs
- Buy or rent mode
- Rich filters (price, rooms, space, energy class, etc.)
- Optional listing details under `_details`
- Pagination up to your `maxItems`

### 🏠 Use cases

- **Real estate market monitoring** in Germany
- **Immowelt price tracking** by city and property type
- **Lead generation** for agencies and investors
- **Property dataset creation** for BI dashboards and alerts
- **Competitor and supply analysis** for PropTech teams

### 🚀 How to use

1. Open the actor in Apify and click **Try for free**.
2. Set these 3 fields first:

- `maxItems` (how many listings you want)
- `location` (for example: `Berlin`, `Hamburg`, `Muenchen`), `locationID`, or `latitude` + `longitude`
- `operation` (`buy` or `rent`)

3. Optionally add filters (price, rooms, space, estate type).
4. Run the actor.
5. Download results from **Dataset** as JSON/CSV/Excel.

### 🧾 Input parameters

| Field                    | Type    | Required | Description                                                                                                                               |
| ------------------------ | ------- | -------: | ----------------------------------------------------------------------------------------------------------------------------------------- |
| `maxItems`               | integer |      Yes | Maximum number of listings to return. Above 570 items, the actor automatically uses a price sort.                                         |
| `properties`             | array   |       No | List of explicit Immowelt property IDs. When set, location and filters are ignored and each item includes `_details`.                     |
| `location`               | string  |     No\* | Search location text (city, district, postcode, etc.).                                                                                    |
| `locationID`             | string  |     No\* | Optional single location ID. Can be used by itself.                                                                                       |
| `locationType`           | string  |       No | Optional location type filter: `country`, `state`, `region`, `city`, `district`, `neighborhood`, `postal_code`, `street`, `house_number`. |
| `latitude` / `longitude` | number  |     No\* | Center point for coordinate-based search. Use both together; coordinates take precedence over named locations.                            |
| `distanceKm`             | integer |       No | Radius around the coordinate point in kilometers. Defaults to `20`.                                                                       |
| `operation`              | string  |       No | `buy` or `rent`.                                                                                                                          |
| `estateType`             | string  |       No | Main property family (e.g., `APARTMENT`, `HOUSE`, `PLOT`).                                                                                |
| `order`                  | string  |       No | Sorting (`Default` or `DateDesc`). Above 570 items, non-price sorts are automatically overridden.                                         |
| `fetchDetails`           | boolean |       No | If `true`, adds `_details` with full detail payload per listing.                                                                          |

#### Common Filters

- `minPrice`, `maxPrice`
- `minRooms`, `maxRooms`
- `minSpace`, `maxSpace`
- `energyScores`
- `features`
- `subEstateTypes`
- `classifiedBusiness`

#### Property IDs mode

If you already know listing IDs, use `properties` and skip search filters.

```json
{
  "maxItems": 2,
  "properties": ["251KK5W8ERLI", "26PD7QUELGE1"]
}
```

In this mode:

- `location`, `locationID`, and all filters are ignored.
- Results are fetched directly by ID.
- Each output item includes `_details`.

#### Example Input

```json
{
  "maxItems": 100,
  "location": "Berlin",
  "operation": "buy",
  "estateType": "APARTMENT",
  "minPrice": 250000,
  "maxPrice": 900000,
  "minRooms": 2,
  "maxRooms": 5,
  "minSpace": 55,
  "order": "DateDesc",
  "fetchDetails": false
}
```

#### Coordinate radius example

```json
{
  "maxItems": 100,
  "latitude": 53.1435,
  "longitude": 8.2146,
  "distanceKm": 30,
  "operation": "buy",
  "estateType": "HOUSE"
}
```

### 📊 Output Data

Each dataset item is a listing object (Immowelt payload) with a convenience image field:

- `id`
- `type`
- `mainDescription.headline`
- `mainDescription.description`
- `hardFacts.price.formatted`
- `rawData.price`, `rawData.nbroom`, `rawData.surface.main`
- `location.address.city`, `location.address.zipCode`, `location.address.street`
- `rawData.propertyType`, `rawData.distributionType`
- `provider.publisherType`, `cardProvider.title`
- `url`
- `_image` (first gallery image URL, added by this actor)
- `_details` (only when `fetchDetails=true`)

### ⚠️ Notes and tips

- `fetchDetails=false` is faster and cheaper.
- `fetchDetails=true` enriches each record with `_details`, useful for deeper analysis.
- Above 570 items, the actor automatically switches to a price sort.
- When using `location`, the actor logs possible location matches with their IDs and types before selecting one.
- Use specific `location` terms for better relevance (district > city center > broad region).
- For trend monitoring, keep filters stable and run periodically.
- For broad discovery, start with fewer filters and higher `maxItems`.
- Provide either `properties` or (`location`/`locationID`) depending on your workflow.

### ⚖️ Legal

Use responsibly and comply with applicable laws, website terms, and data regulations (including GDPR where relevant).

This actor is an independent tool and is **not affiliated with or endorsed by Immowelt**.

# Actor input Schema

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

Maximum number of listings to extract. Above 570 items, the actor automatically uses a price sort.

## `properties` (type: `array`):

List of Immowelt property IDs to fetch directly. When set, location and filters are ignored. Each result includes '\_details'.

## `fetchDetails` (type: `boolean`):

Fetch detailed data per listing and store it under \_details.

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

City, postcode, borough, or neighborhood. The actor resolves it to a location ID automatically.

## `locationID` (type: `string`):

Optional single location ID override

## `locationType` (type: `string`):

Optional location type filter used when selecting a location suggestion.

## `latitude` (type: `number`):

Latitude of the center point for coordinate-based search. Use together with longitude. When set, this takes precedence over location and locationID.

## `longitude` (type: `number`):

Longitude of the center point for coordinate-based search. Use together with latitude.

## `distanceKm` (type: `integer`):

Search radius around the latitude/longitude point, in kilometers.

## `order` (type: `string`):

Sort order. Above 570 items, non-price sorts are automatically overridden.

## `operation` (type: `string`):

Property operation.

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

Property type.

## `subEstateTypes` (type: `array`):

Optional subtype filters.

## `features` (type: `array`):

Optional features.

## `energyScores` (type: `array`):

Optional energy score filters.

## `furnished` (type: `string`):

Furnished status.

## `subsidized` (type: `string`):

Optional subsidized filter value.

## `classifiedBusiness` (type: `string`):

Business classification filter.

## `commissionFree` (type: `boolean`):

Only commission-free listings.

## `radius` (type: `number`):

Optional search radius.

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

Minimum price.

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

Maximum price.

## `minRooms` (type: `number`):

Minimum rooms.

## `maxRooms` (type: `number`):

Maximum rooms.

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

Minimum bedrooms.

## `maxBedrooms` (type: `integer`):

Maximum bedrooms.

## `minFloors` (type: `integer`):

Minimum number of floors.

## `maxFloors` (type: `integer`):

Maximum number of floors.

## `minSpace` (type: `integer`):

Minimum living space in square meters.

## `maxSpace` (type: `integer`):

Maximum living space in square meters.

## `minPlotSpace` (type: `integer`):

Minimum plot size.

## `maxPlotSpace` (type: `integer`):

Maximum plot size.

## `minYearOfConstruction` (type: `integer`):

Minimum construction year.

## `maxYearOfConstruction` (type: `integer`):

Maximum construction year.

## `projectTypes` (type: `array`):

Optional project type filters.

## `locationsInBuilding` (type: `array`):

Optional in-building location filters.

## `classifiedDisplay` (type: `array`):

Optional classified display filter.

## `energyHeating` (type: `array`):

Optional energy heating filter.

## `keywords` (type: `array`):

Optional search keywords.

## `matchAnyKeyword` (type: `boolean`):

If true, listing can match any keyword; otherwise all keywords should match.

## `isSaleGoodwill` (type: `boolean`):

Optional goodwill sale filter.

## `availableFromMax` (type: `string`):

Optional latest availability date/value.

## `availableFromIsLooseMode` (type: `boolean`):

Optional loose-mode availability matching.

## `preferredWarmRent` (type: `boolean`):

Optional preferred warm-rent filter.

## Actor input object example

```json
{
  "maxItems": 30,
  "properties": [],
  "fetchDetails": false,
  "location": "Berlin",
  "locationType": "",
  "distanceKm": 20,
  "order": "default",
  "operation": "buy"
}
```

# Actor output Schema

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

No description

# 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 = {
    "location": "Berlin"
};

// Run the Actor and wait for it to finish
const run = await client.actor("igolaizola/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 = { "location": "Berlin" }

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

```

## MCP server setup

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