AutoScout24 Cars Scraper — EU Prices & Specs | from $1.39/1K
Pricing
from $1.35 / 1,000 car-items
AutoScout24 Cars Scraper — EU Prices & Specs | from $1.39/1K
Scrape AutoScout24 car listings across DE/FR/IT/NL/BE by make, model, price, year, mileage and fuel type. Returns 30+ fields: title, price, year, mileage, power, transmission, fuel, body type, seller info, location, images. Pay per result.
Pricing
from $1.35 / 1,000 car-items
Rating
0.0
(0)
Developer
Vitalii Bondarev
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
10 days ago
Last modified
Categories
Share
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):
- Direct HTTP — sufficient for most runs
- 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
sellerIdsearch - 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.
Use it from your existing tools
Use with Claude Desktop / Cursor / Cline (MCP)
Load this actor as a tool in your AI assistant. Call it directly from your AI assistant via the Apify MCP server — no Store browsing needed. Paste this into your MCP client config (e.g. claude_desktop_config.json) and restart the client:
{"mcpServers": {"apify-autoscout24-cars-scraper": {"command": "npx","args": ["-y","@apify/actors-mcp-server","--tools","bovi/autoscout24-cars-scraper"],"env": {"APIFY_TOKEN": "YOUR_APIFY_TOKEN"}}}}
Replace YOUR_APIFY_TOKEN with your own Apify API token (free at apify.com → Settings → Integrations). Curated to a handful of tools so the agent selects reliably.
Works with Clay
Run this actor as an HTTP enrichment step inside a Clay table:
- Method:
POST - URL:
https://api.apify.com/v2/acts/bovi~autoscout24-cars-scraper/run-sync-get-dataset-items?token={{apify_token}} - Body (JSON): map your Clay columns to the actor input (see the Input section above), e.g.
{"make": "{{clay_column}}"}
The run finishes synchronously and returns the dataset rows straight into your Clay table. It runs on Apify's cloud under your own token and usage. Synchronous runs must complete within 300 seconds.