AutoScout24 Car Search Across 9 European Markets: MCP config, n8n workflow and API

{
  "mode": "searchCars",
  "make": "BMW",
  "country": "de",
  "powerUnit": "kw",
  "vatDeductibleOnly": false,
  "includeDetails": false,
  "includeSellerProfile": false,
  "maxItems": 3
}

---
name: autoscout24-car-search-across-9-european-markets
description: "Car listings from AutoScout24 with identity, vehicle, price, consumption, location, dealer profile (email, VAT/UID, reviews, address, opening hours), EV/charging, engagement counters, media, equipment/history, and enrichment metadata. Fields that the source does not publish are omitted; CHF prices use priceAmount + priceCurrency=CHF and all other markets use EUR. Runs the Apify Actor nimbryxo-studio/autoscout24-car-search-across-9-european-markets. Use when the user needs AutoScout24 data with fields such as id, idType, crossReferenceId, title, status, make and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/autoscout24-car-search-across-9-european-markets"
  store-url: "https://apify.com/nimbryxo-studio/autoscout24-car-search-across-9-european-markets"
---

# AutoScout24 Car Search Across 9 European Markets

Use this skill to fetch AutoScout24 data with the Apify Actor `nimbryxo-studio/autoscout24-car-search-across-9-european-markets` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `searchCars`, `getCarDetails`, `searchByUrl`, `dealerInventory`, `listingIds`, required | What to do: search by filters, fetch listing URLs, replay search URLs, read dealer inventory, or resolve listing IDs. |
| `make` | string | Car brand/manufacturer to filter by (e.g. BMW, Mercedes-Benz, Volkswagen, Audi, Toyota). |
| `country` | string | Market to search. 'all' loops the 8 HTML markets plus Switzerland. '.com' is URL-only and is not part of 'all'. |
| `powerUnit` | one of `kw`, `hp` | Unit for Power From / Power To. Bounds are always sent to AutoScout24 in kW. |
| `vatDeductibleOnly` | boolean | Only VAT-deductible listings (HTML `vatded=true`). CH has no equivalent filter. |
| `includeDetails` | boolean | Fetch each listing's detail page (or CH detail + equipment) to fill body, colour, doors, seats, equipment, history, VAT, seller, GPS, price evaluation, view/favourite counters, mileage-history URL, Carfax (with partner-integration fallback) and created date. |
| `includeSellerProfile` | boolean | Fetch the dealer/seller profile once per seller from `dealerInfoPage` for website, email, VAT/UID, phones, address, contact name, opening hours, imprint, ratings and up to 10 reviews. |
| `maxItems` | integer | Maximum listings to return. Values above the 4,000/query ceiling use year/price slicing; the hard maximum is 10,000. Prefill uses 3 so scheduled checks stay fast. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "searchCars",
  "make": "BMW",
  "country": "de",
  "powerUnit": "kw",
  "vatDeductibleOnly": false,
  "includeDetails": false,
  "includeSellerProfile": false,
  "maxItems": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~autoscout24-car-search-across-9-european-markets/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~autoscout24-car-search-across-9-european-markets/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `id`, `idType`, `crossReferenceId`, `title`, `status`, `make`, `model`, `modelGroup`, `variant`, `condition`, `offerType`, `fuelType`, `fuelCode`, `transmission`, `mileageKm`, `displacement`, `priceEur`, `priceAmount`, `priceCurrency`, `priceRaw`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.