# AutoScout24 Scraper - car listings, prices, dealers (`marekhartmann/autoscout24-scraper`) Actor

Scrape AutoScout24 car listings: price, mileage, first registration, power, fuel, transmission, dealer and location. Refuses to return the whole marketplace when your make or model filter is not recognised.

- **URL**: https://apify.com/marekhartmann/autoscout24-scraper.md
- **Developed by:** [Marek Hartmann](https://apify.com/marekhartmann) (community)
- **Categories:** E-commerce, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.30 / 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.

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

## AutoScout24 Scraper

Scrape **car listings from AutoScout24**: price, mileage, first registration, power, fuel,
transmission, damage flag, dealer and location — from any search you can build on the site.

Built around one rule the alternatives break:

> **A result that does not match your filter is worse than no result at all.**

### The problem this Actor solves

Ask AutoScout24 for a make it does not know — a typo, a renamed brand, a model that moved —
and it answers `HTTP 200` with a full page of cars. Not an error. Not an empty list.
**The entire marketplace, 800 000+ listings**, sorted as if you had asked for them.

A scraper that trusts the page will hand you thousands of rows that look perfectly fine and have
nothing to do with your request, and bill you for every one.

This Actor checks that AutoScout24 actually applied your filter before it writes a single row.
If it didn't, the run stops and tells you which part of your input was not recognised.

| Situation | What happens | You pay |
|---|---|---|
| Make or model not recognised | Run **succeeds**, dataset empty, the unrecognised value is named | Nothing |
| Search matches zero cars | Run **succeeds**, reason explained | Nothing |
| AutoScout24 blocked us or changed its page structure | Run **fails** loudly | Nothing |
| Listings found | Run succeeds with data | Per result |

### Input

Either paste search URLs:

```json
{ "startUrls": ["https://www.autoscout24.com/lst/bmw/x1?cy=D&priceto=15000"], "maxItems": 200 }
```

or describe the search:

```json
{
  "make": "bmw",
  "model": "x1",
  "country": "D",
  "priceTo": 15000,
  "yearFrom": 2015,
  "mileageTo": 150000,
  "sort": "price",
  "maxItems": 200
}
```

### Output

One row per listing:

```json
{
  "listingId": "e8854adb-97eb-466a-bfcb-f34fb6e7a1a2",
  "url": "https://www.autoscout24.com/offers/bmw-x1-18-d-sdrive-diesel-...",
  "make": "BMW",
  "model": "X1",
  "variant": "18 d sDrive",
  "priceEur": 2900,
  "mileageKm": 242000,
  "firstRegistrationYear": 2010,
  "firstRegistrationMonth": 11,
  "powerKw": 105,
  "powerHp": 143,
  "fuel": "Diesel",
  "transmission": "Manual",
  "engineCcm": 1995,
  "isDamaged": true,
  "sellerType": "Dealer",
  "sellerName": "Autohandel Younes K.",
  "country": "DE",
  "zip": "54311",
  "city": "Trierweiler",
  "imageCount": 13,
  "scrapedAt": "2026-08-19T17:00:00.000Z"
}
```

Numbers come out as numbers. `242,000 km` becomes `242000`, `105 kW (143 hp)` becomes two fields.

A **`RUN_REPORT`** record in the key-value store records every search, what came back, and — if
anything went wrong — which side it was on.

### Known limit, stated up front

AutoScout24 serves at most **200 pages per search**, roughly 4000 listings, no matter how many
results it claims. When you ask for more, this Actor says so in the log and in `RUN_REPORT`
instead of quietly stopping. Split the search by price band or registration year to go past it.

### Use cases

- Price benchmarking for a specific make, model and year
- Dealer inventory monitoring
- Residual value and depreciation analysis
- Sourcing damaged or high-mileage cars
- Feeding a used-car pricing model

### Tests

```bash
npm install
npm test
```

22 tests, no network needed — including the one that matters: an unrecognised make must never
turn into a full marketplace dump.

### Need a scraper for something else?

I build custom Apify Actors and browser automation the same way this one is built:
a verified result or an explicit failure, never an empty dataset sold as a success.

- My other Actors: https://apify.com/marekhartmann
- Code and test suites: https://github.com/marekhartmann-creator

Tell me the site and what you need out of it.

# Actor input Schema

## `startUrls` (type: `array`):

Paste ready-made search URLs from AutoScout24. Leave empty and use the fields below instead.

## `make` (type: `string`):

e.g. bmw, audi, skoda

## `model` (type: `string`):

e.g. x1, a4, octavia

## `country` (type: `string`):

Which national AutoScout24 market to search. Germany has by far the most listings.

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

Lowest asking price to include, in euros. Leave empty for no lower bound.

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

Highest asking price to include, in euros. Leave empty for no upper bound.

## `yearFrom` (type: `integer`):

Earliest year of first registration, e.g. 2015.

## `yearTo` (type: `integer`):

Latest year of first registration.

## `mileageTo` (type: `integer`):

Maximum odometer reading in kilometres.

## `fuel` (type: `string`):

AutoScout24 fuel code, e.g. D for diesel, B for petrol

## `transmission` (type: `string`):

AutoScout24 gear code, e.g. M manual, A automatic

## `powerFromKw` (type: `integer`):

Minimum engine power in kilowatts. 100 kW is roughly 136 hp.

## `sort` (type: `string`):

Order AutoScout24 returns the listings in. Affects which listings you get when you cap the result count.

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

AutoScout24 stops at 200 pages (~4000 listings) per search. Split the search to get more.

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

AutoScout24 has no captcha, so the standard Apify proxy is usually enough. Switch to RESIDENTIAL only if runs start coming back blocked.

## Actor input object example

```json
{
  "startUrls": [],
  "make": "bmw",
  "country": "D",
  "sort": "standard",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `listings` (type: `string`):

One row per listing: price, mileage, first registration, power, fuel, transmission, dealer and location - as numbers, not localised strings.

## `runReport` (type: `string`):

Per-search outcome, whether AutoScout24 actually applied your filter, and whether the 200-page cap was hit.

# 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 = {
    "make": "bmw"
};

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

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

```

## MCP server setup

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