# Willhaben Immobilien Scraper - Austrian Property · $1/1K (`listingworks/willhaben-immobilien-scraper`) Actor

Scrape Willhaben.at apartments and houses for sale: price, size, rooms, location and agency. No proxy needed, one flat price per result, no contact details collected.

- **URL**: https://apify.com/listingworks/willhaben-immobilien-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 $0.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

## Willhaben Immobilien Scraper — Austrian property listings, prices and agencies

Willhaben is Austria's largest marketplace, and its property section is where
most Austrian homes for sale are listed, by estate agencies and by private
sellers. This Actor turns the apartment and house listings into a clean table:
what the property is, what it costs, where it is, and which agency is selling
it.

Press Start. The defaults return apartments and houses for sale across all of
Austria, with no configuration needed.

### What a row looks like

```json
{
  "title": "Helle 3-Zimmer-Wohnung mit Balkon",
  "property_type": "apartment",
  "price": 349000,
  "currency": "EUR",
  "living_area_sqm": 78.5,
  "rooms": 3,
  "floor": 2,
  "postal_code": "1120",
  "city": "Wien",
  "state": "Wien",
  "address": "Meidlinger Hauptstraße",
  "agency": "Beispiel Immobilien GmbH",
  "posted_at": "2026-09-15T09:41:12Z",
  "source_url": "https://www.willhaben.at/iad/immobilien/d/…",
  "image_urls": ["https://cache.willhaben.at/mmo/…", "…"],
  "external_id": "1234567890"
}
```

#### `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 |

Willhaben writes a room count of `0` where the advertiser left it blank (7 of 60 ads on 2026-09-24); this Actor publishes that as `null`, not as 0 rooms.

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.

`image_urls` is a list of the ad's photo URLs, up to twelve, not a single
thumbnail.

Agency names are included, but only where Willhaben itself marks the ad as an
agency listing — about 92 rows in 100 on a sample run. A private seller, or an
ad Willhaben leaves unmarked, gets an empty `agency`, because guessing there
would mean publishing a person's name. Contact persons, phone numbers and email
addresses are never collected, for anyone. For private sellers the street, postcode and map point are not published — that is their home. Town, district and state are.

### What people use it for

Price monitoring, where you re-run a saved search on a schedule and watch a
district or a state move. Agency and inventory research, where the agency
column matters as much as the homes. And feeding a valuation or comparison
tool that needs Austrian market data it cannot get from an official API.

### Input

| Field | What it does |
|---|---|
| `propertyType` | `apartment`, `house`, or both (the default). |
| `location` | An Austrian state slug, such as `wien`, `niederoesterreich` or `tirol`. Uses Willhaben's own state pages. Leave empty for the whole country. |
| `postedAfter` | Only keep listings published after this date-time (ISO 8601). Willhaben publishes timestamps to the second, so this filter works to the minute. Handy for daily runs that should return just what is new. |
| `maxItems` | Hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need one. |

### Pricing

$1.00 per 1,000 listings, dropping to $0.50 per 1,000 on higher Apify plans,
plus $0.005 each time a run starts. There is no separate charge for agency
details, and 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. Plot size and year built
are not on that page, so they are not in the output. Street addresses appear
only when the advertiser publishes one (about a third of listings), and
"price on request" listings have an empty `price`.

If the state slug is not one Willhaben recognises, the run fails and tells
you, rather than quietly returning every listing in Austria and charging you
for them.

Willhaben's search is not strictly sorted by date, so `postedAfter` checks two
full pages of older listings before it stops, to avoid missing new ones that
sit behind promoted ads.

If Willhaben 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: `array`):

Which lists to walk: apartment, house, or both. Leave empty for both.

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

An Austrian federal state as willhaben spells it in its own URL: wien, niederoesterreich, oberoesterreich, steiermark, tirol, kaernten, salzburg, vorarlberg, burgenland. Leave empty for the whole country. Anything else fails the run instead of returning unfiltered results.

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

Return only listings published at or after this time, e.g. 2026-09-01T00:00:00Z.

## `sinceDays` (type: `integer`):

Keep only listings posted in the last N days, counted in UTC from the day the run starts: 1 = yesterday and today. Made for a daily schedule. Ignored when Posted after is set.

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

Stop after this many records. Keeps your cost predictable.

## `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": [],
  "location": "",
  "postedAfter": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

All Austrian properties 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 focused on who is 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 = {
    "propertyType": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

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

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

```

## MCP server setup

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