AutoScout24 Cars Scraper — EU Prices & Specs | from $1.39/1K

AutoScout24 Car Scraper — EU Listings, Prices, Specs

Scrape used and new car listings from AutoScout24 — Europe's largest car marketplace — across Germany, France, Italy, Netherlands, Belgium and more. Filter by make, model, price, year, mileage, and fuel type. Returns 30+ structured fields per car.

Pay-per-result. You are charged only for listings actually returned. Starting from $1.39 per 1,000 cars.

---

What you get

Field	Example
listing_id	c50c1fac-1a1c-40f1-…
make	Volkswagen
model	Golf
variant	V 1.9 TDI Comfortline
price_eur	1970
year	2004
first_registration	12/2004
mileage_km	227000
fuel	Diesel
transmission	Manual
power_kw	77
power_hp	105
engine_cc	1896
body_type	Sedan (when available)
seller_type	Dealer / Private
seller_name	Kale Automobile GmbH
location_city	Helmstedt
location_zip	38350
location_country	DE
images	list of image URLs
url	full listing URL

Full schema: 34 fields per record including parse_confidence and warnings.

---

Input

Parameter	Type	Description	Default
make	string	Car make slug (e.g. volkswagen, bmw, mercedes-benz)	—
model	string	Car model slug (e.g. golf, 3er, a4)	—
country	select	Country code: D (Germany), F (France), I (Italy), NL, B, A, E, CH, P, LUX	D
zip	string	Postal code for proximity search	—
radiusKm	number	Search radius in km around the ZIP	—
priceMin	number	Minimum price in EUR	—
priceMax	number	Maximum price in EUR	—
yearMin	number	Minimum year (first registration)	—
yearMax	number	Maximum year	—
mileageMax	number	Maximum mileage in km	—
fuelType	select	B=Petrol, D=Diesel, E=Electric, H=Hybrid, L=LPG, N=CNG	all
maxItems	number	Max listings to return (0 = unlimited)	100
proxyConfiguration	proxy	Apify Residential proxy (recommended for cloud runs)	RESIDENTIAL/DE

---

Access method

AutoScout24 is a Next.js SPA. The actor extracts listings from the embedded __NEXT_DATA__ JSON blob on page 1, then switches to the fast /_next/data/{buildId}/lst[/make[/model]].json JSON route for pagination — the same internal API the browser uses. No HTML parsing after page 1.

Transport (escalates only as needed):

1. Direct HTTP — sufficient for most runs
2. Apify RESIDENTIAL proxy — required when Cloudflare protection activates

---

Proxy

AutoScout24 uses Cloudflare Bot Fight Mode. Direct datacenter IPs (including most CI/cloud runners) are challenged. The included proxyConfiguration with Apify Residential proxy (DE by default) handles this reliably. Without a residential proxy, cloud runs may fail with a 403.

The actor uses sticky sessions (one residential IP per pagination sequence) for consistent access.

---

Use cases

• Price monitoring — track market prices for a specific make/model over time
• Dealer inventory — pull a dealer's full listing set via sellerId search
• Market research — mileage/price distribution for used car valuation models
• Lead generation — find private seller listings before dealers acquire them
• Arbitrage — spot price gaps between countries (DE vs NL vs FR)

---

How much does it cost?

Pricing is pay-per-result — you are charged only for listings actually returned.

Volume	Cost
1,000 listings	~$1.39
10,000 listings	~$13.90
100,000 listings	~$139.00

Each AutoScout24 search page returns 20 listings. A default run of 100 listings (5 pages) consumes roughly $0.15 in actor charges plus Apify Residential proxy costs (typically $0.02–0.05 per page for residential bandwidth). Proxy costs are billed to your Apify account separately.

---

Output example

{
  "listing_id": "651c054e-1021-4938-932f-2ec5ab3b34d3",
  "title": "Volkswagen Golf VI Trendline, Klima, Tüv Neu",
  "make": "Volkswagen",
  "model": "Golf",
  "variant": "VI Trendline, Klima, Tüv Neu",
  "offer_type": "A",
  "price_eur": 3800,
  "price_formatted": "€ 3,800",
  "year": 2011,
  "first_registration": "09/2011",
  "mileage_km": 230000,
  "fuel": "Gasoline",
  "transmission": "Manual",
  "power_kw": 63,
  "power_hp": 86,
  "engine_cc": 1197,
  "body_type": null,
  "seller_type": "Dealer",
  "seller_name": "EYC Global GmbH",
  "location_city": "Köln",
  "location_zip": "51107",
  "location_country": "DE",
  "url": "https://www.autoscout24.com/offers/volkswagen-golf-vi-…",
  "image_count": 35,
  "thumbnail": "https://pic.autoscout24.com/images/651c054e/…",
  "parse_confidence": 1.0,
  "warnings": [],
  "scraped_at": "2026-06-07T12:00:00+00:00"
}

---

FAQ

Q: Does this work without a proxy? A: Direct (no proxy) may work for small test runs locally. For sustained cloud runs, Cloudflare Bot Fight Mode challenges datacenter IPs. Enable Apify Residential proxy (the default) for reliable results on Apify cloud.

Q: How do I scrape a specific dealer? A: AutoScout24's search API does not expose a sellerId filter. The best approach is to set make + model + ZIP + radius to narrow to the area, then filter seller_name / seller_id in your downstream pipeline.

Q: Why is engine_cc sometimes null? A: AutoScout24 omits engine displacement from older listings or listings where the seller did not fill it in. The field is populated when available in the vehicle.engineDisplacementInCCM property of the listing JSON.

Q: What countries are supported? A: All countries served by autoscout24.com: Germany (D), France (F), Italy (I), Netherlands (NL), Belgium (B), Austria (A), Spain (E), Switzerland (CH), Portugal (P), Luxembourg (LUX).

Q: Is the data real-time? A: Each run fetches the live AutoScout24 search results at the time of execution. Listing availability and prices change continuously. For monitoring use cases, schedule repeat runs via Apify's built-in scheduler.

---

Disclaimer

This actor is an independent third-party tool and is not affiliated with, endorsed by, or sponsored by AutoScout24 GmbH or any of its affiliates. AutoScout24 is a trademark of AutoScout24 GmbH. Use of this actor is subject to AutoScout24's Terms of Service and applicable laws. Scrape responsibly — do not overload the site, respect rate limits, and use data for legitimate research or business intelligence purposes only.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Competitor Price Monitor
• Craigslist Scraper
• Doordash Scraper
• Ebay Scraper
• Etsy Listings
• Facebook Marketplace Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.