# AutoScout24 Price Drop Alert: Watch a Car Search or Link (`accountable_eel/autoscout24-price-drop-alert`) Actor AutoScout24 price drop alert: schedule a car search or a listing link and get back only the cars whose asking price fell since the last run, with the old price, the new price and the cut percentage. 8 countries, no login. A run with no price cuts is free. - **URL**: https://apify.com/accountable\_eel/autoscout24-price-drop-alert.md - **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community) - **Categories:** E-commerce, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 price cut returneds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## AutoScout24 Price Drop Alert: Watch a Car Search or Link This is a **price monitor**, not a car-search dump. Give it a make and model, a pasted AutoScout24 search link, or a list of individual listing links; put it on a schedule; and every run returns **only the cars whose asking price has fallen since the last run** — with the old price, the new price and the cut percentage on the row. A run where nothing got cheaper returns one summary row and costs you the start fee alone. The general-purpose [AutoScout24 Car Scraper](https://apify.com/accountable_eel/autoscout24-listing-lookup) can do this too, but it ships as a full-search scraper: you have to turn monitoring on, turn new listings off, pick a threshold, and then find the price change in a 34-column row. Here that is the default and the only thing the actor is shaped for. If you want everything an AutoScout24 search returns — every current car, full specs per listing, sold-signal and sell-through tracking — use the parent actor instead; it is listed under **Related actors** at the bottom. ### Who it's for - **Private buyers** with a shortlist. Paste the listing links of the five cars you are deciding between and hear the moment one of the sellers blinks. - **Dealers and traders** watching a segment ("Volkswagen Golf, 2020+, under 50,000 km, Germany and Austria") for the reductions that mark a car that is not moving. - **Lead-gen and pricing teams** who want price movement as a signal, one row per cut, in a spreadsheet or a warehouse rather than in a browser tab. ### What this does that a plain car search doesn't AutoScout24 shows you today's asking price. It cannot tell you that a car was EUR 24,900 last week and is EUR 22,400 now, because the page has no memory. This actor keeps one. | | Plain search | This actor | |---|---|---| | Rows you get back | every match, every run | only the cars that got cheaper | | Old asking price | not available | `previousPrice` on the row | | Size of the cut | you work it out | `priceDropPct`, and a minimum you set | | Cost of a quiet run | you pay for every row again | start fee only | | "How long has this been listed?" | not available | `daysListed`, `firstSeenAt` | ### How the price memory works Each input line becomes a **watchlist** — whether it is a typed make and model, a pasted search link, or one listing link. The actor remembers every AutoScout24 listing ID and its asking price between runs, in your own account's storage. 1. **First run.** Nothing to compare with, so it returns a single summary row with `monitorStatus: FIRST_RUN` and remembers the prices it found. No cars, no charge. 2. **Every run after.** A car comes back only when its asking price has fallen by at least *Smallest price cut worth an alert* (1% by default) since it was last seen. The row carries `previousPrice`, the current `price`, `priceDropPct` and `changeType: price-drop`. 3. **A quiet run.** Nothing cheaper, so you get one row with `monitorStatus: NO_NEW_ROWS` and `listingCount: 0`. The 1% default is deliberate: car prices move in small steps, and 1% of EUR 20,000 is EUR 200. Raise it on a broad search, lower it on a shortlist. Two schedules with different filters keep **separate** memories, so they never overwrite each other. Give a *Watchlist name* to pin one memory across a filter change. Want cars that are brand new to the search as well? Turn on *Also return cars that are brand new to the search*. They arrive as ordinary rows marked `changeType: new`. ### Countries Eight AutoScout24 country sites, one code per line: `DE`, `AT`, `BE`, `ES`, `FR`, `IT`, `LU`, `NL`. A typed make and model searches all the ones you list at once, newest first. A pasted search link keeps its own countries and filters, so the easiest way to watch something complicated is to build the search on autoscout24.de and paste the link. ### What you get One row per price cut: - **The cut** — `previousPrice`, `price`, `priceDropPct`, `currency`, and AutoScout24's own `priceRating` so you can see whether the new price is actually a good one. - **The car** — `listingId`, `name`, `make`, `model`, `mileageKm`, `productionDate`, `fuelType`, `transmission`, `enginePowerHp`, `condition`, `image`, `url`. - **The seller** — `sellerType` (dealer or private), `sellerName`, `city`, `country`. - **The history** — `changeType`, `firstSeenAt`, `daysListed`. - **The search** — `searchQuery`, `searchUrl`, `listingCount`, `priceDropCount`, `monitorStatus`, `medianPrice`. ### Price $4 per 1,000 listings, plus a $0.00005 start fee. Misses (`found:false`) are never charged. - **Price cuts:** $4 per 1,000 rows returned, plus a $0.00005 start fee per run. - **A quiet run costs the start fee only.** Nothing cheaper means no rows, and no rows means no charge — even though the actor still fetched and compared every page. - A search that returns nothing, or a country that refuses the run, is never billed. Worked example. One watchlist on a 300-car segment, checked daily, where about 8 cars a day get cheaper: 8 × 30 = 240 rows a month, **about $0.96 plus 30 start fees** — roughly **$0.96 a month**. A shortlist of 5 listing links checked daily costs a few cents a month. ### How to use 1. **In the Apify Console.** Open the actor page and click **Start** — the `searches` 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: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~autoscout24-price-drop-alert/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"searches":["bmw 3er"]}' ``` 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. Tips: - **Paste the search link** instead of typing a make and model when you need a filter this actor doesn't list (body type, gearbox, seller type, equipment). Everything in the link is kept. - **A shortlist is the cheapest watchlist there is.** One line per listing link, checked daily: you pay only on the days a seller actually cuts a price. - **Raise the threshold on a broad search.** Dealers nudge prices by EUR 50 to resurface a listing; 2 or 3% keeps that noise out. - **Daily is usually enough.** Unlike consumer marketplaces, car prices are changed by dealers during working hours, not minute by minute. ### Input ```json { "searches": [ "bmw 3er" ] } ``` One per line: a make and model such as "bmw 3er" or "volkswagen golf" (write them the way AutoScout24's own search link does), a search link copied from autoscout24.de or any AutoScout24 country site (all its filters are kept), or a single listing link to watch one car. Each line becomes a watchlist: the first run remembers the asking prices it finds, and every run after it returns only the cars that got cheaper. Searches always run newest first. Accepted formats: bmw 3er, mercedes-benz c-klasse, https://www.autoscout24.de/lst/volkswagen/golf?fregfrom=2020\&kmto=50000\&cy=D, https://www.autoscout24.de/angebote/. ### Sample output | query | found | status | searchQuery | searchUrl | listingCount | priceDropCount | monitorStatus | medianPrice | listings | listingId | url | name | title | make | brand | model | price | previousPrice | priceDropPct | currency | priceRating | mileageKm | productionDate | fuelType | transmission | enginePowerHp | condition | conditionRaw | conditionGrade | sellerType | sellerName | country | city | image | imageUrl | changeType | firstSeenAt | daysListed | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | bmw 3er | true | OK | | | | | | \ | \ | | | | | <make> | <brand> | <model> | <price> | \<asking price when last seen (eur)> | \<price cut %> | <currency> | <autoscout24 price rating> | \<mileage (km)> | <first registration> | <fuel> | <transmission> | \<power (hp)> | <condition> | \<condition (raw autoscout24 offer type / schema.org)> | \<condition (standard: new / good / unknown)> | \<seller type (dealer / private)> | <dealer name> | <country> | <city> | <photo> | <image> | \<change (new / price-drop / gone / seen)> | <first seen on a run> | \<days on the watchlist (first to last seen)> | 1970-01-01T00:00:00.000Z | A real row from the live smoke test (`bmw 3er`, Germany, 5 cars checked out of 11,104 matching, 2026-09-26). This is what run one looks like: the asking prices are now remembered, and the cuts start next run. ```json { "query": "bmw 3er", "found": true, "status": "OK", "searchQuery": "bmw 3er", "searchUrl": "https://www.autoscout24.de/lst/bmw/3er?atype=C&cy=D&sort=age&desc=1&size=100&page=1", "listingCount": 0, "priceDropCount": 0, "monitorStatus": "NO_NEW_ROWS", "medianPrice": 42888, "scrapedAt": "2026-09-26T00:07:56.466Z" } ``` ### How to filter Same optional filters as the AutoScout24 listing actor (`conditions`, `cities`, `brands`, `includeKeywords` / `excludeKeywords`, `sortBy`). They default off, so a watchlist with none of them set still returns exactly the price-cut rows it returned before. Filters run before billing. There is no `availability` input — this actor exists to report price drops on cars it is already tracking. **Used cars in Munich, BMW only.** ```json { "searches": ["bmw 3er"], "cities": ["München"], "brands": ["bmw"], "conditions": ["good"] } ``` **Cheapest first among this run's price cuts.** ```json { "searches": ["volkswagen golf"], "sortBy": "price_asc" } ``` **Drop accident wording from the name.** ```json { "searches": ["bmw 3er"], "excludeKeywords": ["unfall"] } ``` ### 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. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~autoscout24-price-drop-alert/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \ -X POST \ -H "Content-Type: application/json" \ -d '{"searches":["bmw 3er"]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~autoscout24-price-drop-alert/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"searches":["bmw 3er"]}` (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-price-drop-alert/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"searches":["{{search}}"]}`, mapping the row's search into the `searches` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "AutoScout24 Price Drop Alert: Used Car Price Monitor" — the agent will find and run this actor. For a channel or a sheet, add an integration on the Task: trigger on "Apify: run succeeded" in n8n, Make or Zapier and read the run's dataset. A quiet run leaves one summary row with `listingCount: 0` — filter on `listingCount > 0` to skip it. ### vs. alternatives - **AutoScout24's own saved searches.** They notify you about new listings, not about price reductions on cars already in the search, which is the movement that matters when you are negotiating. - **A general AutoScout24 scraper.** Returns every match every run. You pay for the same unchanged cars again and again, and you diff them yourself. - **The parent actor,** [AutoScout24 Car Scraper](https://apify.com/accountable_eel/autoscout24-listing-lookup). Same engine, everything switched on: every current car in a search, full specs per listing (colour, body type, doors, seats, previous owners), the sold signal (`changeType: gone`, `gonePresumedSold`) with a watchlist sell-through rate, and up to 1,000 cars per search. Use it when you want the market; use this one when you want the cuts. ### Data & privacy - **No login, no cookies, no account.** There is no input field that could take an AutoScout24 session, and none is needed: everything here comes from AutoScout24's public search and listing pages. - **Seller data is what the listing already shows publicly** — the dealer or private-seller name and city as printed on the page. No phone numbers, no contact forms, no private-seller contact details are read or returned. - **The price memory holds listing IDs and asking prices only**, in your own account's storage, and only for the watchlists you run. ### FAQ **Nothing came back on the first run. Is it broken?** No. The first run has no earlier price to compare with, so it stores what it finds and returns one summary row (`monitorStatus: FIRST_RUN`). Cuts start from the second run. **How small a cut will it catch?** Whatever you set. The default is 1%, because car prices move in large absolute but small relative steps. **Can I watch specific cars rather than a search?** Yes. Put one AutoScout24 listing link per line. That is the cheapest way to use this actor. **Can I get new listings too?** Yes — turn on *Also return cars that are brand new to the search*. They come back marked `changeType: new` and are billed like any other row. **Does it tell me when a car sold?** No. Disappeared-listing detection and `gonePresumedSold` live in the parent actor; this one is about price movement on live listings. See **Related actors**. **Does it see dealer and private listings both?** Yes, exactly as the search page does. `sellerType` tells you which. ### Related actors - **[AutoScout24 Car Scraper: Listing Price, Specs & Mileage by URL](https://apify.com/accountable_eel/autoscout24-listing-lookup)** — the parent, and the full-capability version: every current car in a search or a single listing's full specs, new-listing alerts, the sold signal with `gonePresumedSold` and days listed, watchlist sell-through rate, and up to 1,000 cars per search across the same 8 countries. - **[Vinted Price Monitor](https://apify.com/accountable_eel/vinted-price-monitor)** — the same price-cut idea on Vinted, with Discord, Slack and Telegram delivery. - **[OLX New Listing Alert](https://apify.com/accountable_eel/olx-new-listing-alert)** — new ads only, on OLX classifieds. # Actor input Schema ## `searches` (type: `array`): One per line: a make and model such as "bmw 3er" or "volkswagen golf" (write them the way AutoScout24's own search link does), a search link copied from autoscout24.de or any AutoScout24 country site (all its filters are kept), or a single listing link to watch one car. Each line becomes a watchlist: the first run remembers the asking prices it finds, and every run after it returns only the cars that got cheaper. Searches always run newest first. Accepted formats: bmw 3er, mercedes-benz c-klasse, https://www.autoscout24.de/lst/volkswagen/golf?fregfrom=2020\&kmto=50000\&cy=D, https://www.autoscout24.de/angebote/<listing>. You're only charged for the ones we actually find — a miss costs nothing. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. One per line. Case-insensitive substring match against the car name (make + model). A listing is kept if the name contains at least one of these. Leave empty to keep every title. ## `excludeKeywords` (type: `array`): Optional. One per line. Case-insensitive substring match against the car name. A listing is dropped if the name contains any of these. Leave empty to drop nothing. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `countries` (type: `array`): One country code per line: DE, AT, BE, ES, FR, IT, LU, NL. A typed make and model searches all of them at once. Leave empty for Germany. Ignored for pasted search links, which keep their own countries. ## `priceFrom` (type: `integer`): Optional. Only cars priced at or above this. Applied by AutoScout24 itself. Ignored for pasted search links. ## `priceTo` (type: `integer`): Optional. Only cars priced at or below this. Ignored for pasted search links. ## `yearFrom` (type: `integer`): Optional, e.g. 2020. Ignored for pasted search links. ## `yearTo` (type: `integer`): Optional. Ignored for pasted search links. ## `mileageTo` (type: `integer`): Optional, e.g. 50000. Ignored for pasted search links. ## `conditions` (type: `array`): Optional. One per line: new\_with\_tags, new, like\_new, good, fair, unknown. AutoScout24's search page only has new vs used (offerType N → new, anything else with an offer type → good, absent → unknown). new\_with\_tags, like\_new and fair are never emitted, so selecting them returns nothing. Leave empty to keep every condition. ## `cities` (type: `array`): Optional. One per line. Case-insensitive contains match against each listing's city. Leave empty to keep every city. ## `brands` (type: `array`): Optional. One per line. Case-insensitive match against the car's make. Leave empty to keep every make this search returned. ## `sortBy` (type: `string`): Optional. Sorts the rows this run actually fetched (after filtering, before the per-search cut) — it does not re-query the rest of AutoScout24. Leave empty to keep AutoScout24's newest-first order. ## `maxListingsPerSearch` (type: `integer`): Newest first. AutoScout24 shows 100 cars per page; this actor pages on its own up to 1,000 per search. This is how deep the watchlist looks, not how many rows you get back: you only pay for the cars whose price actually fell. ## `deltaMode` (type: `boolean`): On by default: this is what the actor is for. The first run remembers every car and asking price it finds and returns a single summary row. From the second run on, a car comes back only when its asking price has fallen by at least the percentage below since it was last seen, with the old price, the new price and the cut percentage on the row. Unchanged cars are removed before you are billed, so a quiet run costs only the start fee. Schedule it daily and send the rows to Slack, Google Sheets, n8n or your dealer system. Turn this off to get every matching car instead, like an ordinary search. ## `deltaName` (type: `string`): Leave empty and one is derived from this run's filters, so two schedules with different filters keep separate price memories. Type your own name to keep one memory across a filter change. ## `minPriceDropPct` (type: `integer`): A car must be at least this much cheaper than when it was last seen to come back as a price cut. Default 1%, because car prices move in small steps: 1% of EUR 20,000 is EUR 200. Raise it to hear only about real reductions. ## `alertOnPriceDrop` (type: `boolean`): On by default. Measured on the asking price AutoScout24 shows. Turning this off with the checkbox above on leaves nothing to return. ## `alertOnNew` (type: `boolean`): Off by default, so your results stay price cuts only. Turn it on to also get cars this watchlist has never seen, each marked new rather than price-drop. They are billed like any other row. ## `skipFirstRun` (type: `boolean`): The first run of a watchlist has no earlier price to compare with, so it returns one summary row and no cars either way. This matters only if you also turned on "Also return cars that are brand new": with it on, the first run remembers everything silently instead of returning a hundred rows at once. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each listing found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. Residential recommended for anti-bot-sensitive targets. ## Actor input object example ```json { "searches": [ "bmw 3er" ], "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "countries": [ "DE" ], "conditions": [], "cities": [], "brands": [], "sortBy": "", "maxListingsPerSearch": 100, "deltaMode": true, "deltaName": "", "minPriceDropPct": 1, "alertOnPriceDrop": true, "alertOnNew": false, "skipFirstRun": false, "columns": [ "searchQuery", "searchUrl", "listingCount", "priceDropCount", "monitorStatus", "medianPrice", "listings", "listingId", "url", "name", "title", "make", "brand", "model", "price", "previousPrice", "priceDropPct", "currency", "priceRating", "mileageKm", "productionDate", "fuelType", "transmission", "enginePowerHp", "condition", "conditionRaw", "conditionGrade", "sellerType", "sellerName", "country", "city", "image", "imageUrl", "changeType", "firstSeenAt", "daysListed" ], "expandRows": true, "maxConcurrency": 5, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '<YOUR_API_TOKEN>' with your token const client = new ApifyClient({ token: '<YOUR_API_TOKEN>', }); // Prepare Actor input const input = { "searches": [ "bmw 3er" ], "includeKeywords": [], "excludeKeywords": [], "countries": [ "DE" ], "conditions": [], "cities": [], "brands": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/autoscout24-price-drop-alert").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '<YOUR_API_TOKEN>' with your token. client = ApifyClient("<YOUR_API_TOKEN>") # Prepare the Actor input run_input = { "searches": ["bmw 3er"], "includeKeywords": [], "excludeKeywords": [], "countries": ["DE"], "conditions": [], "cities": [], "brands": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/autoscout24-price-drop-alert").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "searches": [ "bmw 3er" ], "includeKeywords": [], "excludeKeywords": [], "countries": [ "DE" ], "conditions": [], "cities": [], "brands": [] }' | apify call accountable_eel/autoscout24-price-drop-alert --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/autoscout24-price-drop-alert" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/mu9stWD4ORHWOFcPC/builds/cLxeR7a53Ya9Rp3wG/openapi.json