AutoScout24 Car Listings Scraper

Scrape public AutoScout24 vehicle listings with prices, mileage, seller details, locations, images, and normalized car fields.

Data fields

FieldTypeDescription
urlstringValue exported as url.
listingIdstring | nullValue exported as listingId.
titlestring | nullValue exported as title.
makestring | nullValue exported as make.
modelstring | nullValue exported as model.
versionstring | nullValue exported as version.
pricenumber | nullValue exported as price.
currencystring | nullValue exported as currency.

Input preview

startUrlsAutoScout24 search URLs
querySearch query / make fallback
makeMake
modelModel
countryCountry code
localeAccept-Language header

API and agents

This actor can be run through Apify API, datasets, webhooks, schedules, and the official Apify MCP server.

How this actor works

See example inputs, outputs, API usage, and practical limits before running this actor on Apify.

Open Apify page

Extract public car listings from AutoScout24 search result pages.

Use this actor to collect prices, mileage, seller names, locations, images, and normalized vehicle attributes from public AutoScout24 marketplace inventory.

What does AutoScout24 Car Listings Scraper do?

AutoScout24 Car Listings Scraper turns public AutoScout24 search pages into a clean dataset.

It can scrape:

  • ๐Ÿš— Vehicle listing URLs
  • ๐Ÿ’ถ Prices and currencies
  • ๐Ÿ›ฃ๏ธ Mileage values
  • ๐Ÿท๏ธ Make, model, and version
  • โ›ฝ Fuel type
  • โš™๏ธ Transmission
  • ๐Ÿ“ Seller location
  • ๐Ÿข Seller or dealer name
  • ๐Ÿ–ผ๏ธ Listing images
  • ๐Ÿ•’ Scrape timestamp

The actor is designed for search-result inventory monitoring and market research.

Who is it for?

Used-car dealers

Track comparable vehicles, dealer pricing, and nearby inventory.

Automotive marketplaces

Monitor public supply, price ranges, and seller coverage across regions.

Lead generation teams

Build lists of public dealer inventory pages and seller names for compliant research workflows.

Pricing analysts

Compare vehicle price bands by make, model, mileage, fuel type, and country.

Resale researchers

Collect repeatable snapshots of public car listings for valuation and trend analysis.

Why use this actor?

  • โœ… Normalized dataset rows
  • โœ… Public search URLs supported
  • โœ… Make/model filter helper for simple searches
  • โœ… Pagination and deduplication included
  • โœ… Optional detail-page enrichment
  • โœ… Works well for small QA runs and larger monitoring runs

What data can you extract?

Field Description
url Public AutoScout24 listing URL
listingId Unique listing UUID when available
title Listing title
make Vehicle make
model Vehicle model
version Trim/version text
price Numeric price
currency Currency code such as EUR
mileage Numeric odometer value
mileageUnit Mileage unit code
firstRegistration Registration date/year text when present
year Parsed year when present
fuelType Fuel type
transmission Transmission type
power Power value when available
location Seller city/region
country Seller country
sellerName Dealer or seller name
sellerType Seller schema type
sellerUrl Dealer profile URL when available
images Listing image URLs
descriptionSnippet Short description when available
features Additional feature strings
sourcePageUrl Search page where the row was found
position Result position on the source page
scrapedAt ISO timestamp

Input options

You can start from AutoScout24 search URLs or from basic filters.

Recommended input:

{
  "startUrls": [
    { "url": "https://www.autoscout24.com/lst/bmw?atype=C&cy=D&desc=0&sort=standard&ustate=N%2CU&pricefrom=10000&priceto=30000" }
  ],
  "maxItems": 20,
  "includeDetails": false
}

Start URLs

Use startUrls when you already configured a search on AutoScout24.

This is the most accurate way to preserve site filters.

Examples:

  • A BMW search in Germany
  • A specific price range
  • A country-specific inventory page
  • A make/model result page

Filter inputs

If you do not provide startUrls, the actor can build a basic search URL.

Supported helper fields include:

  • query
  • make
  • model
  • country
  • minPrice
  • maxPrice
  • yearFrom
  • yearTo
  • sort

For complex AutoScout24 filters, use startUrls.

Detail page enrichment

Set includeDetails to true to open each vehicle listing page.

This can add description snippets or extra feature values when available.

Use it when you need richer data.

Leave it disabled for faster and cheaper inventory scans.

Output example

{
  "url": "https://www.autoscout24.com/offers/example-car-00000000-0000-0000-0000-000000000000",
  "listingId": "00000000-0000-0000-0000-000000000000",
  "title": "BMW i4 eDrive40 Gran Coupe M Sport",
  "make": "BMW",
  "model": "i4",
  "version": "i4 eDrive40 Gran Coupe M Sport",
  "price": 25000,
  "currency": "EUR",
  "mileage": 69000,
  "fuelType": "Electric",
  "transmission": "Automatic",
  "location": "Krauchenwies",
  "sellerName": "Example Dealer",
  "images": ["https://prod.pictures.autoscout24.net/example.jpg"],
  "scrapedAt": "2026-07-06T08:00:00.000Z"
}

How to scrape AutoScout24 listings

  1. Open AutoScout24.
  2. Configure your public search filters.
  3. Copy the search result URL.
  4. Paste it into startUrls.
  5. Set maxItems.
  6. Run the actor.
  7. Export the dataset as JSON, CSV, Excel, XML, or via API.

Tips for best results

  • Use public search result URLs.
  • Start with maxItems: 20 for a quick smoke test.
  • Use includeDetails: false for faster monitoring.
  • Use one country per run for cleaner analysis.
  • Use separate runs for very different makes/models.
  • Keep exact AutoScout24 filters in the URL when possible.

Common use cases

Price monitoring

Run the same search every day and compare prices over time.

Dealer inventory research

Collect seller names and listing details in a target market.

Market supply snapshots

Track how many public listings match make, model, price, and year filters.

Competitive analysis

Compare similar vehicles by mileage, fuel, transmission, and listed price.

Integrations

You can connect the actor output to:

  • Google Sheets dashboards
  • Airtable vehicle research tables
  • BI tools through dataset API exports
  • CRM enrichment workflows
  • Scheduled monitoring jobs
  • Webhooks for inventory changes

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/autoscout24-car-listings-scraper').call({
  startUrls: [{ url: 'https://www.autoscout24.com/lst/bmw?atype=C&cy=D&desc=0&sort=standard&ustate=N%2CU' }],
  maxItems: 20
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient

client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('fetch_cat/autoscout24-car-listings-scraper').call(run_input={
    'startUrls': [{'url': 'https://www.autoscout24.com/lst/bmw?atype=C&cy=D&desc=0&sort=standard&ustate=N%2CU'}],
    'maxItems': 20,
})
print(run['defaultDatasetId'])

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~autoscout24-car-listings-scraper/runs?token=MY-APIFY-TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"startUrls":[{"url":"https://www.autoscout24.com/lst/bmw?atype=C&cy=D&desc=0&sort=standard&ustate=N%2CU"}],"maxItems":20}'

MCP usage

Use Apify MCP to run this actor from AI tools.

MCP URL:

https://mcp.apify.com/?tools=fetch_cat/autoscout24-car-listings-scraper

Claude Code setup:

claude mcp add apify-autoscout24 https://mcp.apify.com/?tools=fetch_cat/autoscout24-car-listings-scraper

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-autoscout24": {
      "url": "https://mcp.apify.com/?tools=fetch_cat/autoscout24-car-listings-scraper"
    }
  }
}

Example prompts:

  • "Scrape 50 BMW listings from this AutoScout24 URL."
  • "Compare prices and mileage in the dataset."
  • "Export the results to CSV and summarize the cheapest cars."

Scheduling

The actor can be scheduled on Apify.

Typical schedules:

  • Daily market snapshots
  • Weekly dealer inventory scans
  • Monthly valuation research exports

Use stable search URLs for comparable time-series data.

Data quality notes

AutoScout24 pages may vary by locale and country.

Some fields may be missing from individual listings.

For example, power or first registration may not be present on every search result page.

Optional detail enrichment may improve coverage for some fields.

Limits

  • Only public AutoScout24 pages are supported.
  • Account-only data is not scraped.
  • Contact forms and saved-search data are out of scope.
  • Very large runs may take longer due to pagination.
  • Site layout changes can affect extraction and should be reported.

Legality

This actor is intended for public web data.

Before scraping, make sure your use case complies with applicable laws, AutoScout24 terms, and privacy requirements.

Do not use scraped data for spam, harassment, or unlawful profiling.

Troubleshooting

The run returned fewer listings than requested

The search may have fewer public results than maxItems, or the URL may include narrow filters.

Try a broader AutoScout24 search URL.

Some fields are empty

AutoScout24 does not expose every field for every listing.

Try enabling includeDetails for richer detail-page data.

My filters are not applied

Use a copied AutoScout24 search result URL in startUrls.

This preserves the site's own filter parameters better than manually entering helper fields.

Support

If AutoScout24 changes page structure or you need an additional output field, open an issue on the actor page.

Include:

  • The input you used
  • A sample AutoScout24 URL
  • Expected field(s)
  • Run ID if available

Privacy and data handling

This Actor only requests the permissions needed to run the input you provide. It uses your input (such as URLs, search terms, identifiers, filters, and limits) only to fetch the requested public data from the relevant source site or API for this Actor, then writes results to your Apify dataset/key-value store.

Data may pass through Apify platform services and Apify Proxy during the run, and requests are sent only to the target site or public data provider required for this Actor's results. FetchCat does not send your inputs or outputs to advertising networks, data brokers, or model-training services, and does not retain run data outside Apify storage after the run except when you explicitly share run details for transient support debugging.

You are responsible for using this Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs. Review the output before storing, sharing, or combining it with other data.

Common questions

Questions and answers reused from the canonical actor README.

Is AutoScout24 login required?

No. The actor is designed for public search result and listing data only.

Can I scrape contact forms or saved searches?

No. Account-only workflows, saved searches, and private contact actions are out of scope.