AutoScout24 Listing Lookup — Car Data & Specs API

Look up any AutoScout24 car listing by URL and get back full structured vehicle data — make, model, price, mileage, engine, fuel type, transmission, previous owners, and more — pulled directly from the listing's own schema.org JSON-LD. No API key, no anti-bot workaround needed: a real AutoScout24 listing page serves this data in clean structured form on a plain fetch.

Features

• Full listing snapshot. Make, model, name, color, body type, production date, price, currency, and condition.
• Technical specs. Mileage (km), fuel type, engine power (hp), transmission, doors, seats, and number of previous owners.
• Full URLs or bare slugs. Pass a complete autoscout24.de/angebote/... listing URL, or a bare slug appended to that path.
• Pay only for resolved listings. Removed listings and invalid URLs are never charged — see Pricing.
• Built for bulk. Feed in many listing URLs at once; concurrency is configurable.

How to use AutoScout24 Listing Lookup — Car Data & Specs API

1. In the Apify Console. Open the actor page and click Start — the items field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~autoscout24-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"items":["https://www.autoscout24.de/angebote/bmw-1er-d-klimaautomatik-navi-sport-pdc-2hd-ahk-diesel-blau-cat_ma13gr100037ge192va4086mt520tr5338-6abcd6fd-da11-489c-9969-aa6226df929a"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "items": ["https://www.autoscout24.de/angebote/bmw-1er-118i-advantage-benzin-blau-abc123"],
  "maxConcurrency": 5,
  "proxyConfiguration": { "useApifyProxy": true }
}

items is the list of AutoScout24 listing URLs (or bare slugs appended to /angebote/) to look up. maxConcurrency controls parallel requests (default 5); this target has no browser fallback, so keeping it conservative avoids getting blocked. proxyConfiguration routes requests through Apify Proxy — not required for this target, but available if you see rate limiting at volume.

Output

One row per listing, for example:

{
  "query": "https://www.autoscout24.de/angebote/bmw-1er-118i-advantage-benzin-blau-abc123",
  "found": true,
  "data": {
    "listingId": "abc123",
    "make": "BMW",
    "model": "1er",
    "name": "BMW 118i Advantage",
    "color": "Blau",
    "bodyType": "Kleinwagen",
    "productionDate": "2021-03",
    "mileageKm": 34500,
    "transmission": "Manual",
    "doors": 5,
    "seats": 5,
    "previousOwners": 1,
    "fuelType": "Benzin",
    "enginePowerHp": 136,
    "price": 21990,
    "currency": "EUR",
    "condition": "https://schema.org/UsedCondition",
    "image": ["https://prod.pictures.autoscout24.net/..."],
    "url": "https://www.autoscout24.de/angebote/bmw-1er-118i-advantage-benzin-blau-abc123"
  },
  "scrapedAt": "2026-08-20T12:00:00.000Z"
}

A removed listing, an invalid URL, or a 404 page returns found: false with no data — and is never charged.

Use cases

• Track price and mileage changes across a watchlist of car listings.
• Enrich a dealership or aggregator feed with structured specs from AutoScout24.
• Verify a listing is still live before referencing it elsewhere.
• Compare technical specs (fuel type, transmission, power) across multiple listings.
• Feed listing URLs from another source into a clean, structured extraction step.

Pricing

$4 per 1,000 results, plus a $0.005 start fee. Misses (found:false) are never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~autoscout24-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"items":["https://www.autoscout24.de/angebote/bmw-1er-d-klimaautomatik-navi-sport-pdc-2hd-ahk-diesel-blau-cat_ma13gr100037ge192va4086mt520tr5338-6abcd6fd-da11-489c-9969-aa6226df929a"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~autoscout24-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"items":["https://www.autoscout24.de/angebote/bmw-1er-d-klimaautomatik-navi-sport-pdc-2hd-ahk-diesel-blau-cat_ma13gr100037ge192va4086mt520tr5338-6abcd6fd-da11-489c-9969-aa6226df929a"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~autoscout24-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"items":["{{value}}"]}, mapping the row's value into the items array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "AutoScout24 Listing Lookup | Apify" — the agent will find and run this actor.

FAQ

What counts as "found"? The listing page must contain a schema.org Product JSON-LD block with an offers.itemOffered vehicle object. A 404, a removed listing, or an unexpected page shape returns found: false and is never charged.

Does this need a proxy or browser to get past bot protection? No — AutoScout24 listing pages serve their structured data on a plain fetch with no bot protection encountered. Apify Proxy is available in the input but not required for this target.

Can I use search-result pages instead of listing URLs? No — this actor expects full listing URLs (autoscout24.de/angebote/...), not search or category pages. Search-result bulk export is a different shape this actor doesn't attempt.

What language/region does the data come back in? Requests use German (de-DE) headers, matching the .de domain the actor targets — fields like bodyType and color come back in German as published on the listing.

How heavy are these requests? A real listing page is roughly 584KB — notably heavier than a JSON-API-only lookup, since it's a full rendered HTML page, but that's the cost of getting the same structured data straight from the source.

What happens to previous-owner or engine-power fields if AutoScout24 doesn't publish them for a listing? Any field not present in the listing's own JSON-LD comes back as null rather than being omitted — the row shape stays consistent across listings.