# willhaben Listing Scraper: Austria Marketplace Data (`accountable_eel/willhaben-listing-lookup`) Actor

Look up any willhaben.at listing by URL: price, title, status, and full category attributes (mileage, make, model, fuel type, transmission for vehicles; raw attributes for every other category). Charged only for listings that resolve.

- **URL**: https://apify.com/accountable\_eel/willhaben-listing-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.52 / 1,000 successful lookups

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 Listing Lookup

Look up any listing on [willhaben.at](https://www.willhaben.at), Austria's largest
online marketplace for vehicles, real estate, and general classifieds — price,
title, status, and the full category attribute set (mileage, make, model, fuel
type, transmission for vehicles; the equivalent raw attributes for every other
category). This is not an official willhaben API: the actor fetches the public
listing page and reads the same structured data the page itself renders from.

### Features

- **URL → structured listing record.** Ad ID, title, status, price (numeric and
  as-displayed), and currency.
- **Vehicle-specific fields.** Make, model, mileage (km), fuel type, transmission,
  and model year, pulled straight out of the listing's own attribute set.
- **Every category attribute, raw.** A `attributes` map with every name/value pair
  willhaben stores on the listing, so non-vehicle categories (real estate, general
  marketplace) aren't left with empty fields.
- **Pay only for hits.** Removed, expired, or invalid listing URLs cost nothing —
  see [Pricing](#pricing).
- **Built for bulk.** Feed in thousands of listing URLs; concurrency and proxy
  group are both configurable.

### How to use willhaben Listing Lookup — Price & Vehicle Attribute API

1. **In the Apify Console.** Open the actor page and click **Start** — the `items` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~willhaben-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"items":["https://www.willhaben.at/iad/gebrauchtwagen/d/auto/vw-touran-comfortline-1-6-tdi-comfortline-dsg-1731057880"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "items": [
    "https://www.willhaben.at/iad/gebrauchtwagen/d/auto/alfa-romeo-mito-...-991753367",
    "/iad/gebrauchtwagen/d/auto/some-other-listing-123456789"
  ],
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

`items` is a list of willhaben listing identifiers — full listing URLs (the
`/iad/.../d/...` permalink) or bare paths, which are resolved against
`https://www.willhaben.at` automatically. `maxConcurrency` (default 5, max 20)
controls how many listings are fetched in parallel; keep it conservative, since
this target has no browser fallback if it starts blocking. `proxyConfiguration`
defaults to the Residential proxy group — plain datacenter IPs get a 403 from
this target, so leave the default in place unless you know your setup works
around it.

### Output

One row per input item, for example:

```json
{
  "query": "https://www.willhaben.at/iad/gebrauchtwagen/d/auto/alfa-romeo-mito-...-991753367",
  "found": true,
  "data": {
    "adId": "991753367",
    "title": "Alfa Romeo MiTo 1.4 TB MultiAir Distinctive",
    "status": "ACTIVE",
    "price": 8990,
    "priceDisplay": "€ 8.990,-",
    "currency": "EUR",
    "make": "Alfa Romeo",
    "model": "MiTo",
    "mileageKm": 87000,
    "fuelType": "Benzin",
    "transmission": "Manuell",
    "yearModel": "2010",
    "attributes": { "...": "every raw attribute name/value pair from the listing" },
    "image": "https://cache.willhaben.at/...",
    "url": "https://www.willhaben.at/iad/gebrauchtwagen/d/auto/alfa-romeo-mito-...-991753367"
  },
  "scrapedAt": "2026-08-20T12:00:00.000Z"
}
```

A listing that's been removed, expired, or was never valid — willhaben 308-redirects
those to an unrelated category page with no listing data — comes back as
`{ "query": "...", "found": false, "scrapedAt": "..." }` and is never charged.

### Use cases

- Track price changes on specific vehicle, real estate, or marketplace listings over time.
- Pull mileage, fuel type, and transmission across a shortlist of cars for side-by-side comparison.
- Check whether a batch of previously-seen listings is still active or has been removed/sold.
- Build a structured dataset from category attributes for local market research.
- Verify a listing URL is live and resolvable before linking to it elsewhere.

### Pricing

$2 per 1,000 results, plus a $0.00005 start fee. Misses (`found:false`) are never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~willhaben-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"items":["https://www.willhaben.at/iad/gebrauchtwagen/d/auto/vw-touran-comfortline-1-6-tdi-comfortline-dsg-1731057880"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~willhaben-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"items":["https://www.willhaben.at/iad/gebrauchtwagen/d/auto/vw-touran-comfortline-1-6-tdi-comfortline-dsg-1731057880"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~willhaben-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"items":["{{value}}"]}`, mapping the row's value into the `items` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "willhaben Listing Lookup | Apify" — the agent will find and run this actor.

### FAQ

**What can I put in `items`?** Full willhaben listing URLs (the `/iad/.../d/...`
permalink), or a bare path starting with `/iad/...` — those get the
`https://www.willhaben.at` domain prepended automatically.

**What happens if a listing was removed or the URL is wrong?** willhaben
308-redirects invalid or expired listing IDs to an unrelated category page that
has no `advertDetails` in its data. The actor treats that as not-found, records
`found: false`, and does not charge for it.

**Is this using an official willhaben API?** No — willhaben doesn't publish one.
The actor requests the public listing page and reads the same `__NEXT_DATA__`
JSON the page uses to render itself, which is more stable than parsing rendered
HTML but is still a page scrape, not a documented API contract.

**Why do vehicle listings have more fields than other categories?** The
`make`/`model`/`mileageKm`/`fuelType`/`transmission`/`yearModel` fields are
convenience shortcuts pulled from vehicle-specific attribute keys. Every
category — vehicles included — also gets the full raw `attributes` object, so
real estate or general marketplace listings aren't missing data, just the
named shortcuts.

**Do I need to change the proxy configuration?** No, and you generally shouldn't.
This target returns HTTP 403 through the shared datacenter proxy pool but works
through Residential, which is the default — only touch it if you have a specific
reason to.

**How high can I set `maxConcurrency`?** Up to 20, but the default of 5 is a
reasonable starting point. This target has no browser fallback, so a burst of
concurrent requests that trips anti-bot defenses costs you more (blocked, unpaid
requests) than a slower, steady crawl.

# Actor input Schema

## `items` (type: `array`):

One item per line — see the item shape and examples below. Only the items we actually find are charged — never per run, and never for a miss.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Defaults to Residential — this target returns HTTP 403 through the shared datacenter proxy pool even though a plain request from a residential IP succeeds.

## Actor input object example

```json
{
  "items": [
    "https://www.willhaben.at/iad/gebrauchtwagen/d/auto/vw-touran-comfortline-1-6-tdi-comfortline-dsg-1731057880"
  ],
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 = {
    "items": [
        "https://www.willhaben.at/iad/gebrauchtwagen/d/auto/vw-touran-comfortline-1-6-tdi-comfortline-dsg-1731057880"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/willhaben-listing-lookup").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 = { "items": ["https://www.willhaben.at/iad/gebrauchtwagen/d/auto/vw-touran-comfortline-1-6-tdi-comfortline-dsg-1731057880"] }

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/willhaben-listing-lookup").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 '{
  "items": [
    "https://www.willhaben.at/iad/gebrauchtwagen/d/auto/vw-touran-comfortline-1-6-tdi-comfortline-dsg-1731057880"
  ]
}' |
apify call accountable_eel/willhaben-listing-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/willhaben-listing-lookup"
        }
    }
}
```

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/7zAG7b3jXdKoVyIhY/builds/jawjxNNjq6UYJ7fpR/openapi.json