AutoScout24 Scraper (PPR)

Extract public AutoScout24 vehicle listings, prices, specifications, seller details, and listing URLs.

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
countryCountry code
localeAccept-Language header
maxItemsMaximum listings
sortSort order

API and agents

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

Ready-to-run examples

Open a saved Apify example, adjust the input, and run the actor in your own Apify account.

View all examples

How this actor works

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

Open Apify page

Export public AutoScout24 car listings with prices, mileage, vehicle specifications, seller names, locations and images. AutoScout24 Scraper accepts search-result URLs or basic make/model filters and saves structured rows for inventory research and price comparisons.

Only public www.autoscout24.com/lst searches are supported. Individual offer URLs, other country domains and account-only data are not accepted as starting inputs. Some fields may be unavailable.

Quick start

  1. Configure a search on AutoScout24's .com site and copy its results URL.
  2. Paste it into startUrls, set a small maxItems limit, and run the Actor.
  3. Open the dataset and export JSON, CSV or Excel.
{
  "startUrls": [{"url": "https://www.autoscout24.com/lst/bmw?atype=C&cy=D&ustate=N%2CU"}],
  "maxItems": 20,
  "includeDetails": false
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

https://youtu.be/1OW8gOqlZbY?t=25

What you get

One row per saved public vehicle listing, with its URL, available identity, asking price, mileage and seller fields. Source page and collection time help keep observations traceable. Optional description and feature fields depend on what public pages expose.

Who is it for?

  • Dealer research teams reviewing publicly advertised stock by vehicle type.
  • Used-car analysts comparing asking prices with mileage and registration year.
  • Automotive data teams preparing repeated search exports for analysis in their own tools.

How you can use the data

  • Prepare a make-and-model review sheet. Choose a supported vehicle make and model or paste a public .com/lst search URL. Export listingId, url, price, currency, mileage, mileageUnit and year to review comparable observations.
  • Keep the requested search visible. Save sourcePageUrl with each row, especially when a copied URL contains complex filters. A nonempty URL list takes precedence over helper fields and their ordering settings.
  • Compare separate stock snapshots. Join later exports by listingId, preserving collection time. Check mileage units, currencies and missing fields before interpreting a price difference. The Actor does not calculate valuations, inventory changes or alerts.
  • Choose the detail coverage you need. Enable includeDetails when available descriptions or feature strings matter. A failed extra visit can leave a useful listing-level row, and no complete specification or private-contact coverage is promised.

Input settings

Use a search URL for exact site filters, or omit startUrls to build a basic search. A nonempty startUrls array takes precedence over the search-building filters, including sort.

Setting / API key Purpose
Search URLs — startUrls Public .com/lst searches. Omit or use an empty array for filter-based search
Make fallback — query A vehicle make, used only if make is omitted. Not a full-text search
Make/model — make, model Build a make/model search. Model alone has no effect without a make or make fallback
Country — country Site country code. Default D for Germany
Price range — minPrice, maxPrice Minimum/maximum asking price
Registration years — yearFrom, yearTo First-registration year range
Fuel/transmission — fuelType, transmission AutoScout24 filter codes. Use a copied URL for complex filters
Sort — sort standard, price_asc, price_desc, mileage_asc, mileage_desc, age_desc. Default standard
Listing limit — maxItems Total saved listings across all supplied searches. 1–10,000, default 20
Language — locale Preferred page language. Default en-GB,en;q=0.9
Detail enrichment — includeDetails Visit listing pages for additional descriptions/features where available. Default false

No input is globally required: an omitted make and URL starts a broad search in the default country. Set a make or supply a search URL to keep results relevant. Input-field help explains detailed filter precedence and sorting. The Actor uses direct access. There is no proxy or connection selector.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Each saved row describes one vehicle listing. This abbreviated example shows the output shape only, not an observed listing. Missing values may be null or empty arrays.

{
  "url": "https://www.autoscout24.com/offers/example-car-00000000-0000-0000-0000-000000000000",
  "listingId": "00000000-0000-0000-0000-000000000000",
  "title": "Example vehicle",
  "make": "BMW",
  "price": 25000,
  "currency": "EUR",
  "mileage": 69000,
  "sellerName": null,
  "images": [],
  "scrapedAt": "2026-10-25T00:00:00.000Z"
}
Fields Meaning
url, listingId Public listing URL and UUID when available
title, make, model, version Vehicle identity and trim text
price, currency Numeric listing price and currency
mileage, mileageUnit Odometer reading and source unit
firstRegistration, year Registration text and parsed year
fuelType, transmission, power Available vehicle specifications
location, country Seller city/region and country
sellerName, sellerType, sellerUrl Public seller/dealer identity and profile URL when available
images Available image URLs
descriptionSnippet, features Description text and feature strings when available
sourcePageUrl, position, scrapedAt Source search page, position on that page and collection time

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Tips for best results

  • Set a small listing cap explicitly. Inspect returned price and mileage fields before increasing the workload.
  • Copy a public search URL for complex filters. Use only .com/lst search-result pages, then keep the URL with your export.
  • Use make and model helpers deliberately. The query field is only a make fallback, and a model alone has no effect without a make.
  • Enable details only when extra fields matter. Missing descriptions or features remain unknown rather than becoming full-coverage claims.
  • Review the run summary after interrupted work. Check saved counts and per-search outcomes before using a partial export.

Limits and caveats

Only public .com search-result pages are supported. Individual offer inputs, login pages, saved-search account data and contact forms are outside the scope. Requests use direct access, with no proxy or connection selector.

A narrow search can return fewer listings than requested. Limits are ceilings rather than completeness guarantees. AutoScout24 access challenges or suspected extraction problems can fail a run. A successful empty search does not establish that every target was accessible.

Unavailable optional detail pages leave listing-level rows intact. Long searches may stop before the run deadline. When available, RUN_SUMMARY provides per-search outcomes and saved counts, and interrupted runs may retain a recovery checkpoint.

Optional fields can be missing or null. The Actor does not extract private seller contacts or guarantee every vehicle specification. Site ordering is applied to searches rather than a global re-sort of a combined dataset.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~autoscout24-scraper-ppr-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.autoscout24.com/lst/bmw?atype=C&cy=D&ustate=N%2CU"
    }
  ],
  "maxItems": 20,
  "includeDetails": false
}
JSON

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&ustate=N%2CU"
    }
  ],
  "maxItems": 20,
  "includeDetails": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['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&ustate=N%2CU'}], 'maxItems': 20, 'includeDetails': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

After the asynchronous run finishes, retrieve its defaultDatasetId through the dataset API or Console.

MCP and AI agents

You can ask your AI assistant to collect data with AutoScout24 Scraper (PPR) and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's AutoScout24 Scraper (PPR). You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use AutoScout24 Scraper (PPR) by Fetch Cat, or give it the identifier fetch_cat/autoscout24-scraper-ppr-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

  • “Use Fetch Cat’s AutoScout24 Scraper to collect up to 5 vehicles from this public AutoScout24 .com search URL. Show asking prices, currencies, mileage units, registration years and source links.”
  • “Collect at most 5 BMW i4 listings using the make and model helpers for Germany, with search URLs left empty. Keep listing identifiers and collection time so I can compare the export with my earlier sheet.”
  • “Collect a small sample of 5 cars from my .com search URL with optional detail visits enabled. Show available descriptions and features, marking missing specifications and any incomplete-search outcomes.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

Support and feedback

For custom additions or integrations, email [email protected].

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥

Common questions

Questions and answers reused from the canonical actor README.

Is this an AutoScout24 API alternative?

It provides structured exports of supported public listing searches through Apify's API. It is not AutoScout24's official API and does not provide account-only features.

Can I export AutoScout24 listings to CSV or Excel?

Yes. Export the saved dataset from Apify, or retrieve JSON rows through its dataset API. Exports include only records saved by the run.

Why are my filters ignored?

A nonempty startUrls array uses the supplied URL's filters and sorting. Clear it to use make, model and other search-building fields. query is a make fallback, not a general keyword search.

Why are some fields empty or results missing?

Public pages do not always expose every field. Optional details may improve coverage. Check the run status and available summary for access or extraction failures rather than assuming an empty dataset means no vehicles exist.

Can I monitor inventory or use other scrapers?

Compare separate datasets in your own workflow for inventory changes. For other sources, the related Actors below serve adjacent research needs. They do not extend this Actor's supported inputs.