AutoScout24 Scraper (PPR)

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.

Ready-to-run examples

Choose a small preconfigured search; review its input before starting.

• Track BMW listings in Germany — Collect BMW inventory using the make and country filters.
• Export an Audi Germany market search — Collect listings from a configured public search URL without detail enrichment.

What does AutoScout24 Scraper (PPR) do?

AutoScout24 Scraper (PPR) turns public AutoScout24 search pages into a clean dataset.

It can scrape:

• Vehicle listing URLs, prices and currencies
• Mileage, make, model, version, fuel type and transmission
• Seller location and public seller or dealer name
• Listing images and 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 from public search URLs
• Make/model helpers for simple searches
• Pagination and deduplication
• Optional detail-page enrichment

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

Pricing

This Actor uses Apify pay-per-event pricing. The start event is charged once per run, and the item event is charged only when a vehicle listing is saved successfully. Subscription-tier discounts may apply.

See the live Apify Pricing tab for current rates.

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.

Fields	Purpose
query, make, model	Make fallback and vehicle filters when startUrls is empty
country	Country filter; defaults to D (Germany)
minPrice, maxPrice	Minimum and maximum listing price
yearFrom, yearTo	First-registration year range
fuelType, transmission	AutoScout24 filter codes
sort	standard, price_asc, price_desc, mileage_asc, mileage_desc, or age_desc
maxItems	Maximum saved listings: 1–10,000; default 20
locale	Preferred page language via the request header
includeDetails	Optional listing-page enrichment; default false

startUrls takes precedence over the search-building filters. Input validation runs before the start charge or network requests.

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

Illustrative shape only, not an observed vehicle listing. Fields can be missing or null when the public page does not expose them.

{
  "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
• Run-completion webhooks; compare saved datasets separately to detect 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-scraper-ppr-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-scraper-ppr-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-scraper-ppr-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. Authenticate with your Apify account and review the input and spending limits before starting a run. Ask the agent for maxItems: 5 and includeDetails: false first; retrieve the returned dataset before comparing vehicles. These client examples require compatible installed clients; never paste credentials into prompts.

MCP URL:

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

Claude Code setup:

$claude mcp add --transport http apify-autoscout24 'https://mcp.apify.com/?tools=fetch_cat/autoscout24-scraper-ppr-scraper'

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-autoscout24": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.apify.com/?tools=fetch_cat/autoscout24-scraper-ppr-scraper", "--header", "Authorization: Bearer ${APIFY_TOKEN}"],
      "env": {"APIFY_TOKEN": "YOUR_APIFY_TOKEN"}
    }
  }
}

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.

FAQ

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.

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.

Input recipes

Track BMW listings in Germany

{"make":"BMW","country":"D","maxItems":20}

Export a filtered market search

{"startUrls":[{"url":"https://www.autoscout24.com/lst/audi?atype=C&cy=D&ustate=N%2CU"}],"maxItems":50,"includeDetails":false}

Related scrapers

Explore other FetchCat actors for marketplace and vehicle-adjacent workflows:

• Google Maps Lead Finder
• Google Maps Reviews Scraper
• Airbnb Listings Scraper
• Booking.com Hotel Scraper
• Amazon Products Search Scraper

Support

If a run fails, output looks wrong, or you need an additional field, open an issue or report a bug from this Actor's page.

Include the run ID or run URL, a non-sensitive input JSON example, one reproducible public AutoScout24 URL, and the expected versus actual output. Do not share tokens, cookies, or private account data.

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.