# Willhaben.at Scraper: immobilien, autos, jobs (search + alerts) (`datahamster/willhaben-at-listings`) Actor

Willhaben scraper for willhaben.at: marktplatz, immobilien, autos, motorrad and jobs by keyword or by any willhaben search URL with your own filters. Flat rows with price, city, postcode, district, Bundesland, coordinates, seller type, photos. Monitor mode alerts on new ads and price cuts.

- **URL**: https://apify.com/datahamster/willhaben-at-listings.md
- **Developed by:** [Viktor Dubnytskiy](https://apify.com/datahamster) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 result items

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Willhaben.at Scraper: immobilien, autos, jobs (search + alerts)

A willhaben scraper for **willhaben.at**, Austria's biggest classifieds platform: marktplatz, immobilien, gebrauchtwagen, motorräder and jobs. Search by keyword, or paste the path of any willhaben search URL so every filter you clicked on the site (area, category, attributes) is kept — each ad comes back as one flat row, and monitor mode returns only what is new or re-priced since your last run.

### What you get — example output

One row per ad. Real values from the example dataset (query `fahrrad`, marktplatz):

| Field | Example value | What it is |
|---|---|---|
| `id` | `willhaben-1780807171` | Stable row key (`willhaben-` + ad id) |
| `title` | `Puch Olympian 12 im Top Zustand` | Ad headline |
| `price` / `priceLabel` | `290` / `€ 290` | Numeric price in euros and the label willhaben prints |
| `city` / `postcode` | `Perchtoldsdorf` / `2380` | Town and Austrian postcode |
| `district` / `region` | `Mödling` / `Niederösterreich` | Bezirk and Bundesland (`lat` `48.12079`, `lon` `16.26427`) |
| `sellerType` | `private` | `private` or `business` — separate dealers from individuals |
| `createdAt` / `validTo` | `2026-09-04T07:31:57Z` / `2026-10-19T07:31:49Z` | When the ad went live and when it expires |
| `adStatus` | `active` | Ad state as willhaben reports it |
| `categoryTreeIds` | `["4390;4525;4552;4554"]` | Full willhaben category path as ids |

Full field list: `id`, `url`, `platform`, `country`, `title`, `description` (search snippet), `price`, `currency`, `priceLabel`, `priceType`, `categoryId`, `categoryTreeIds[]`, `condition`, `city`, `postcode`, `district`, `region`, `lat`, `lon`, `images[]`, `sellerId`, `sellerName`, `sellerType`, `createdAt`, `refreshedAt`, `validTo`, `isPromoted`, `deliveryAvailable` (PayLivery), `adStatus`, `verticalId`, `params{}`, `query`, `rank`, `source`, `scrapedAt`.

### Use cases

- **Real-estate and car watchers**: paste a filtered willhaben search URL, schedule it, and be alerted the moment a matching Wohnung or Gebrauchtwagen appears or drops price.
- **Reselling**: follow a keyword across the marktplatz with a price ceiling and postcode-level location on every row.
- **Market research**: pull a category with price, Bundesland and seller type to see supply and pricing across Austria.

### How it works

The actor reads willhaben's own search pages and takes the structured data the site embeds in them, so each row arrives with coordinates, postcode and category ids instead of scraped text. willhaben blocks datacenter IPs, so traffic goes through Apify's residential proxy automatically — nothing to configure, but Apify bills that traffic on top (about 0.7 MB per page of 30 ads). Pass `searchPath` to reuse any filter combination from the website; otherwise pick a `vertical` and keywords. In `monitor` mode only new and re-priced ads are pushed, with an optional webhook or Telegram summary.

### Input

| Field | Meaning | Default |
|---|---|---|
| `queries` | Keywords, e.g. `["fahrrad"]`; each is paginated separately | `["fahrrad"]` |
| `vertical` | `marktplatz`, `immobilien`, `auto`, `motorrad`, `jobs` | `marktplatz` |
| `searchPath` | Any willhaben search path after `/iad/`, filters included | — |
| `priceFrom` / `priceTo` | Price range in whole euros, e.g. `100` / `900` | — |
| `sortBy` | `newest`, `price_asc`, `price_desc`, `relevance` | `newest` |
| `maxPages` | Pages per query, 30 ads each | `5` |
| `maxItems` | Stop after this many ads | `20` |
| `mode` | `scrape`, or `monitor` for new/changed only | `scrape` |
| `webhookUrl`, `telegramBotToken`, `telegramChatId` | Where monitor-mode change summaries are sent | — |

### Pricing

| Event | Price |
|---|---|
| result | $0.001 per listing ($1 per 1,000) |
| monitor-check | $0.005 per monitor run |
| change | $0.001 per new/changed listing |

Charged only for listings actually pushed — an empty run costs you nothing. willhaben blocks datacenter IPs, so the actor uses residential proxy (Apify bills that traffic on top; ~0.7 MB per page of 30 listings).

### Why this actor

- Any willhaben search URL works as input, so the filters you already trust on the site are preserved exactly.
- All five verticals — marktplatz, immobilien, auto, motorrad, jobs — behind one input.
- Postcode, Bezirk, Bundesland and coordinates on every row, so Austrian rows map and group without geocoding.
- Monitor mode with new-ad and price-drop alerts, delivered by webhook or Telegram.
- Residential handling is built in — no proxy setup, no cookies, no willhaben account.

### Limits

- Ad detail pages are not opened: full description and seller phone are not included.
- Real-estate and car attributes arrive as raw willhaben attribute names in `params` (e.g. `ESTATE_SIZE/LIVING_AREA`, `MILEAGE`).
- Residential traffic is billed by Apify on top of the per-result price.

### FAQ

**Can I monitor new listings for a search?** Yes. Save your input (keywords or a `searchPath`) as a Task, set `mode: monitor` and schedule it. Each run then returns only ads that appeared or changed price since the previous run, and can POST a summary to `webhookUrl` or a Telegram chat.

**Can I use my own willhaben filter URL?** Yes — copy everything after `willhaben.at/iad/` from your filtered search and put it in `searchPath`. Area ids, category and attribute filters are all kept.

**Do I need a willhaben account or my own proxy?** No. The actor reads public search pages and routes through Apify's residential proxy automatically.

### Changelog

- 0.1: initial release — keyword search, custom search paths, monitor mode.

***

If this actor saved you time, please leave a review on its Store page — it is the main way other buyers find it. Bug reports and field requests are welcome in the **Issues** tab.

# Actor input Schema

## `queries` (type: `array`):

Keywords to search, one string per phrase, each paginated separately. Example: \["fahrrad", "e-bike"]. Leave empty to list a whole vertical or searchPath.

## `vertical` (type: `string`):

Which willhaben section to search when no searchPath is given. Accepted values: marktplatz (Kaufen und Verkaufen), immobilien, auto (Gebrauchtwagenboerse), motorrad, jobs. Example: "marktplatz".

## `searchPath` (type: `string`):

Any willhaben.at search URL path after /iad/, filters included; overrides vertical and keeps every filter you set on the site. Example: "immobilien/eigentumswohnung/eigentumswohnung-angebote?areaId=900". Optional.

## `priceFrom` (type: `integer`):

Minimum price in whole euros. Example: 100. Optional.

## `priceTo` (type: `integer`):

Maximum price in whole euros. Example: 900. Optional.

## `sortBy` (type: `string`):

Result order: newest (newest first), price\_asc (cheapest first), price\_desc, relevance. Example: "newest".

## `maxPages` (type: `integer`):

How many result pages to fetch per query, 30 ads per page. Example: 5.

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

Stop the run after this many ads; you are charged only for ads actually pushed. Example: 20.

## `mode` (type: `string`):

scrape = return all matching ads; monitor = return only ads that are new or changed price/status since the previous run of this saved Task. Example: "scrape".

## `monitorKey` (type: `string`):

Optional state key for monitor mode when the actor is started directly instead of from a saved Task; any stable string, e.g. "fahrrad-wien".

## `webhookUrl` (type: `string`):

Optional HTTPS URL that receives a POST with the monitor-mode change summary (JSON). Example: "https://hooks.example.com/willhaben".

## `telegramBotToken` (type: `string`):

Optional Telegram bot token used to send monitor-mode change summaries. Format: "123456789:AA...".

## `telegramChatId` (type: `string`):

Optional Telegram chat id that receives monitor-mode summaries. Example: "-1001234567890".

## Actor input object example

```json
{
  "queries": [
    "fahrrad"
  ],
  "vertical": "marktplatz",
  "sortBy": "newest",
  "maxPages": 5,
  "maxItems": 20,
  "mode": "scrape"
}
```

# Actor output Schema

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

All pushed rows (dataset, JSON)

## `resultsTable` (type: `string`):

Dataset in the Console viewer

## `runSummary` (type: `string`):

RUN\_SUMMARY record (pushed, skipped, emptyReason)

# 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 = {
    "queries": [
        "fahrrad"
    ],
    "vertical": "marktplatz",
    "maxItems": 20,
    "mode": "scrape"
};

// Run the Actor and wait for it to finish
const run = await client.actor("datahamster/willhaben-at-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 = {
    "queries": ["fahrrad"],
    "vertical": "marktplatz",
    "maxItems": 20,
    "mode": "scrape",
}

# Run the Actor and wait for it to finish
run = client.actor("datahamster/willhaben-at-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 '{
  "queries": [
    "fahrrad"
  ],
  "vertical": "marktplatz",
  "maxItems": 20,
  "mode": "scrape"
}' |
apify call datahamster/willhaben-at-listings --silent --output-dataset

```

## MCP server setup

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