# AutoScout24 Listings Scraper - Used Cars, Prices & Sellers (`xtracto/autoscout24-listings-scraper`) Actor

Scrape AutoScout24 used-car listings from any search URL: make, model, version, price, mileage and specs, location, seller and images. Reads the page's embedded data island and paginates automatically. HTTP-only, no account, no browser.

- **URL**: https://apify.com/xtracto/autoscout24-listings-scraper.md
- **Developed by:** [Farhan Febrian Nauval](https://apify.com/xtracto) (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 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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

## AutoScout24 Listings Scraper — Used Cars, Prices & Sellers

Scrape AutoScout24 used-car listings from any search URL: make, model, trim, price, mileage,
fuel, gearbox, location, seller and images. HTTP-only, no account, no browser.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `searchUrls` | array | *required* | Result-page URLs with your filters already applied |
| `maxItemsPerUrl` | integer | `200` | Stop a search after this many unique listings |
| `maxPages` | integer | `20` | Pages per search (site ceiling is 200 — see below) |
| `maxConcurrency` | integer | `2` | Searches in parallel; pages within a search stay sequential |
| `proxyConfiguration` | object | RESIDENTIAL | Recommended for sustained volume |

Build the search in the browser with the filters you want, then paste the URL. Any AutoScout24
domain works. `page` is managed by the actor — it is rewritten rather than appended, so a URL
that already carries one is handled correctly.

### Output

```jsonc
{
  "_input": "https://www.autoscout24.com/lst/bmw/118?atype=C",
  "_source": "S1-next-data",
  "_scrapedAt": "2026-09-07T03:12:42Z",
  "_page": 1,
  "_tlsProfile": "chrome110",

  "listingId": "9b0a3d2a-…",
  "listingUrl": "https://www.autoscout24.com/offers/…",
  "make": "BMW",
  "model": "118",
  "modelVersion": "Navi WLAN PDC Lordos LED",
  "priceRaw": 11999,                 // numeric, straight from upstream
  "priceFormatted": "€ 11,999",
  "mileageInKm": "98,904 km",        // as rendered
  "mileageKm": 98904,                // parsed
  "fuel": "Gasoline",
  "transmission": "Manual",
  "offerType": "Used",
  "city": "Celle", "zip": "29223", "countryCode": "D",
  "sellerType": "Dealer", "sellerName": "…",

  // raw sub-objects, upstream field names verbatim
  "vehicle": {…}, "price": {…}, "location": {…}, "seller": {…},
  "images": […], "ratings": {…}, "statistics": {…}, "wltpValues": {…}
}
```

All twelve convenience fields were filled on 120 of 120 listings in testing.

### How it works

Data comes from the page's `__NEXT_DATA__` island (`props.pageProps.listings`), which carries
far more than the cards show — including the seller's phone links and WLTP emission values.

#### The 200-page ceiling is real, and the actor says so

`numberOfPages` comes back as **200 whatever the search is**: 200 for a query reporting 8,849
results, and 200 again for one reporting 827,638. At ~19 rows per page that is roughly **4,000
listings per search URL**, full stop.

Silently returning 4,000 of 827,638 rows would look like a bug in the actor, so it warns once
per URL when it detects the cap and tells you what to do instead — split the search into
narrower filters (price band, registration year, region) and pass several URLs.

#### Two field names that lie

Worth knowing if you extend this actor, because both produce a wrong answer rather than an
error:

- **`modelVersion` does not exist.** The trim level is `modelVersionCustom` (or
  `modelVersionInput`, or only `subtitle`). Reading the obvious name gave a column that was
  empty on all 120 test rows — which reads as "this site has no trim data" rather than "wrong
  key".
- **`mileageInKm` is a string**, e.g. `"98,904 km"`. The raw value is passed through and a
  parsed `mileageKm` integer is offered beside it.

#### Duplicate rows across pages

Consecutive pages overlap — sponsored and rotated slots reappear. Listings are deduplicated by
id, and a page that contributes nothing new ends the crawl for that URL.

### Known limits

| Limit | Detail |
|---|---|
| ~4,000 rows per search URL | The site's own paging ceiling; narrow the filters to go deeper |
| List pages only | Full spec sheets and descriptions live on the detail page, not fetched here |
| Seller phone | Present in the raw `seller` object as links, not resolved to a number |

# Actor input Schema

## `searchUrls` (type: `array`):

Result-page URLs from any AutoScout24 domain, with your filters already applied — build the search in the browser, then paste the URL. Example: https://www.autoscout24.com/lst/bmw/118?atype=C

## `maxItemsPerUrl` (type: `integer`):

Stop a search once this many unique listings have been emitted.

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

AutoScout24 itself refuses to page past 200 (~4,000 listings) no matter how many results a search reports, so this cannot exceed that. For a bigger harvest, split the search into narrower filters rather than raising this.

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

Search URLs processed in parallel. Pages within one search are always sequential.

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

Residential recommended for sustained volume.

## Actor input object example

```json
{
  "searchUrls": [
    "https://www.autoscout24.com/lst/audi/a4?atype=C&fregfrom=2019"
  ],
  "maxItemsPerUrl": 200,
  "maxPages": 20,
  "maxConcurrency": 2,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

One row per scraped record, stored in the run's default dataset.

# 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 = {
    "searchUrls": [
        "https://www.autoscout24.com/lst/bmw/118?atype=C"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("xtracto/autoscout24-listings-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 = { "searchUrls": ["https://www.autoscout24.com/lst/bmw/118?atype=C"] }

# Run the Actor and wait for it to finish
run = client.actor("xtracto/autoscout24-listings-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 '{
  "searchUrls": [
    "https://www.autoscout24.com/lst/bmw/118?atype=C"
  ]
}' |
apify call xtracto/autoscout24-listings-scraper --silent --output-dataset

```

## MCP server setup

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