Kleinanzeigen Search: New Listing & Price Alerts

Your Kleinanzeigen Suchauftrag, as an API: only new listings and price drops, every hour. This actor runs your search against Kleinanzeigen.de's own search-results pages — Germany's dominant classifieds marketplace, covering everything from phones and furniture to cars and apartments — and returns one clean row per listing: title, price, location, image, and a permanent link. Turn on monitoring and it becomes a watchlist: new listings and price drops since your last run, charged per new row, free on quiet days. Add the sold signal and it is also a Kleinanzeigen sold items tracker: which listings disappeared since the last run, which of those were presumably sold, and the search's sell-through rate. Schedule it hourly and send the results to Discord, Slack, Google Sheets, or n8n.

Who it's for

A reseller or arbitrage buyer watching one category (phones, bikes, cars) for underpriced or newly-posted listings wants a live feed of what's actually on Kleinanzeigen right now, without refreshing the search page by hand or relying on Kleinanzeigen's own "Suchauftrag" email alert inside its app. An apartment hunter watching "Wohnung Berlin" wants to know the moment something new appears, not whenever Kleinanzeigen's own email digest gets around to it. A market-research team tracking asking prices for a product category, or a Sheets/n8n workflow that reacts the moment something new is posted, gets the same shape here: paste a list of search terms, get back a flat row per listing, and pay only for listings actually returned — a search that finds nothing costs nothing.

This actor is the search-and-monitor member of the Kleinanzeigen pair in this catalogue — kleinanzeigen-listing-lookup (public, paid) covers a single known listing URL; this one covers a keyword or a pasted search URL, with monitoring on top, on the same ../.. this catalogue's other classifieds actors (Blocket, Marktplaats, OLX) already ship.

Why this one

• Monitoring first, not a one-off dump. Turn on "Only return results that are new, or dropped in price" and this actor becomes a watchlist: it remembers every ad ID it has already shown you, and only bills you for what's actually new or has dropped in price since the last run. A quiet run — nothing new, nothing cheaper — still finishes and costs only the base run fee. Neither Store leader for "kleinanzeigen scraper" sells this as the core product — both return a plain search dump.
• Sold signal and sell-through rate. Turn on "Alert on gone listings" and the watchlist also tells you which listings disappeared since the last run (changeType: gone), flags the cheap, long-listed ones as gonePresumedSold, and keeps a lifetime sellThroughRate and this run's medianPrice for the search. Gone rows are ordinary listing rows, with no separate event. See "Sold signal and sell-through" below for how it decides and where it stops.
• Reads Kleinanzeigen's own structured listing data. Every base field is read from the same embedded data Kleinanzeigen's own search page ships to render the results — not brittle text scraped from styled HTML — so price, posting time, seller type, and a stable seller hash come through as exact, typed values, not guesses.
• Never charged for a miss, or a quiet monitoring run. A search that finds nothing, or a scheduled watchlist run where nothing changed, still gets a row explaining what happened — and costs nothing. See "Pricing" below for the found-row rate.
• Paste a keyword or your own saved search URL. Type plain keywords, or paste a Kleinanzeigen search-results URL you've already filtered on the site (price range, private-seller-only, offer/wanted) — its filters carry straight through.
• Optional item-page hop for the full picture. Turn on "Fetch extra details per listing" to add the full (redacted) description and category-specific attributes (mileage, condition, room count — whatever that category shows), billed as a separate event only for rows you actually keep.

What you get

One row per listing by default (turn off "Expand rows" in Advanced to get one row per search instead, with the listings nested under listings).

Deselect any field in the Input tab's column picker to drop it from every row — query, found, status, message, and scrapedAt always stay.

Pricing

• Listing returned: $2 per 1,000 listings
• Listing details fetched: $1 per 1,000 listings

Plus a $0.01 start fee per run. Each event above is billed independently, only when it actually returns data — misses (found:false) are never charged.

listing-details only fires when "Fetch extra details per listing" is on, and only for listings actually delivered that run — a listing dropped by monitoring never triggers a details fetch, so you never pay for a detail hop on a row you didn't get.

Gone rows (with "Alert on gone listings" on) are ordinary listing rows at the same price. There is no separate event, and a gone row never triggers a details fetch or any other request: it is rebuilt from what the watchlist remembered.

Monitoring / only new results

Turn on "Only return results that are new, or dropped in price" and a search line becomes a watchlist instead of a one-off dump:

• A listing counts as new the first time its Kleinanzeigen ad ID is returned by this watchlist.
• A listing counts as a price drop when its price falls by at least "Minimum price drop" (5% by default) since it was last seen — measured against the most recently seen price, so a listing that drops twice is compared against its latest price each time, not its original one.
• Already-seen, unchanged listings are dropped before you're billed. A quiet run — nothing new, nothing cheaper — still finishes and returns one free row with monitorStatus: NO_NEW_ROWS, so a scheduled task shows it actually ran.
• The first run has nothing to compare against. By default it returns everything it finds as "new" (so you see your whole current search result once). Turn on "Seed silently" to instead have the first run bank everything quietly with zero rows and zero charge, and start alerting from the second run on — this is what stops a fresh watchlist from firing a hundred "new listing" messages into your Discord channel on day one.
• With "Alert on gone listings" on, a remembered listing that has disappeared from the part of the search this run provably covered comes back as changeType: gone (see the next section). Gone listings are counted for sellThroughRate even with that checkbox off.
• Sort is forced to Kleinanzeigen's own newest-first order whenever monitoring is on (it's already the site's own default with no filters at all), so two runs of the same watchlist are always comparing the same ordering.

Schedule recipe. Save this actor as an Apify Task with deltaMode: true and a deltaName you choose, add an hourly (or daily) Schedule (Console → your Task → Schedule), and point the task's webhook (Console → your Task → Webhooks) at Discord, Slack, Google Sheets, or an n8n/Make webhook URL to get pinged only when something actually changes.

Price-drop window limitation. A price drop is only ever seen while the listing is still inside what a run actually fetches — if a listing falls out of your maxListingsPerSearch window or your price filters between runs, this actor has no way to notice it dropped. Keep searches reasonably narrow (a specific model, a tight category, a city) rather than one huge catch-all if price-drop coverage matters to you.

Sold signal and sell-through

Resellers pricing a flip want to know what actually sells, how fast, and at what price. With monitoring on, this actor works as a Kleinanzeigen sold items tracker for any search you give it.

What "gone" means, honestly. Kleinanzeigen never publishes that an ad was sold. A gone row means the listing was delisted: most often sold, sometimes withdrawn, deleted, expired, or edited so that it no longer matches your search (a new price outside your price filter, a new category). An ad marked "Reserviert" that is still in the results is simply seen, not gone. If a gone listing shows up again later (a reservation that fell through, a paused ad), it is taken back off the lifetime gone count and is not alerted twice.

gonePresumedSold narrows that down: true only when the listing was seen on 2 or more consecutive runs and its last price was at or under the median price of this run's search. A cheap, established listing that vanishes is the one most likely to have sold. Anything else is false (gone only).

How it decides a listing is gone. A run only reads the newest maxListingsPerSearch results, so "not in this run" usually just means "slid further down the search". This actor tells the two apart by feed position, not by ad ID (Kleinanzeigen's ad IDs are not in date order):

• Kleinanzeigen sorts a search newest first, with 2 paid "TOP" ads pinned on each page. Every listing's place among the organic results is remembered; TOP ads hold no place.
• A listing seen on the previous run and missing now is gone only if, after counting every listing that appeared above it (new ads, ads bumped back to the top with "hochschieben", and ads from outside the last window), it would still sit inside this run's window, with a safety margin at the bottom edge. Every estimate errs toward "still for sale".
• When the run read the whole search (small searches: it paged to the end of Kleinanzeigen's own result count, nothing was cut by your limit), any remembered listing missing from it is gone.
• There is no gone check on a first run, on a run where a page was blocked or failed, on a page that had to be read by the fallback parser, on an empty result, or on the first run after you change the filters of a watchlist you named yourself.

Limits. A listing that disappears near the bottom edge of your window, or after it already slid out of view, is never reported gone (a missed sale, never a false one). Size maxListingsPerSearch comfortably above the number of new listings your search gets between two runs. For a busy search like "iphone" across all of Germany that can be hundreds per hour, so a narrow search (a model, a city, a price band) run hourly gives far better sell-through coverage than a broad one. sellThroughRate is gone / tracked over the watchlist's lifetime (listings unseen for 30 days are forgotten, and at most 5,000 are remembered per search), so treat it as a signal for comparing searches, not an exact market statistic.

Billing. Gone rows are ordinary listing rows, at the same per-listing price, with no separate event. They are only returned (and billed) with "Alert on gone listings" on. goneCount, sellThroughRate and medianPrice are filled either way, on every row and on the free quiet-run row.

Example input (run it daily as a Task; a first run seeds the watchlist, sold signals start on the second run):

{
  "searches": ["iphone 13 128gb"],
  "location": "Berlin",
  "radiusKm": 30,
  "maxListingsPerSearch": 100,
  "deltaMode": true,
  "deltaName": "iphone13-berlin-sell-through",
  "alertOnNew": false,
  "alertOnPriceDrop": false,
  "alertOnGone": true
}

That returns only the listings that went gone since the last run, each with gonePresumedSold, daysListed and lastPrice, plus the search's sellThroughRate and medianPrice.

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:

   curl "https://api.apify.com/v2/acts/accountable_eel~kleinanzeigen-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["iphone"]}'
   

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.

4. Turn on "Only return results that are new, or dropped in price" under Monitoring once you want a watchlist instead of a one-off dump — see "Monitoring / only new results" above.

How to filter

Every filter below is optional and off by default — leave it out and you get the exact same listings as before. minPrice/maxPrice, location+radiusKm and the offer/wanted/seller-type filters already existed; this section adds includeKeywords/excludeKeywords. There is no conditions, availability or brands filter on this actor: Kleinanzeigen exposes no condition grade, and its only sold-shaped signal (gonePresumedSold, from monitoring) is a delta inference, never real source data — see "Monitoring / only new results" above.

1. Exclude a word, private sellers only:

{
  "searches": ["iphone"],
  "excludeKeywords": ["defekt", "ersatzteile"],
  "sellerType": "private"
}

excludeKeywords matches the title before billing, so a broken or parts-only listing never costs you a row.

2. Only titles mentioning a model:

{
  "searches": ["iphone"],
  "includeKeywords": ["pro max", "pro"]
}

includeKeywords keeps a listing only if its title contains at least one of these — combine it with excludeKeywords to both require and forbid terms in the same run.

3. A price range, near a city:

{
  "searches": ["fahrrad"],
  "location": "Berlin",
  "radiusKm": 20,
  "minPrice": 50,
  "maxPrice": 300
}

Input

{
  "searches": [
    "iphone"
  ]
}

One per line — plain keywords (e.g. "iphone", "wohnung berlin") or a full search-results URL copied from kleinanzeigen.de, including any filters it already has. No login required. Accepted formats: iphone, wohnung berlin, https://www.kleinanzeigen.de/s-anbieter:privat/preis:100:500/iphone/k0.

Sample output

A search that finds nothing comes back as a row with "found": false and is never charged. A quiet monitoring run comes back as a row with "found": true, "monitorStatus": "NO_NEW_ROWS" and is also 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~kleinanzeigen-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["iphone"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~kleinanzeigen-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"searches":["iphone"]} (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~kleinanzeigen-search-lookup/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 "Kleinanzeigen Scraper: New Listings & Price Alerts" — the agent will find and run this actor.

For monitoring, point the Task's webhook (Console → your Task → Webhooks) at a Discord or Slack incoming-webhook URL, a Google Sheets automation (via Zapier/Make/n8n listening for the webhook), or an n8n/Make workflow's own webhook trigger, so new listings and price drops land wherever you actually work instead of a dataset you have to remember to check.

Tips

• Start monitoring with "Seed silently" on for any watchlist you're setting up on a schedule — it avoids a wall of "new" alerts for your entire current search result on day one.
• Keep a monitored search reasonably narrow (a model, a tight category, a city) — see "Price-drop window limitation" above for why a huge catch-all search misses price drops on listings that fall outside what gets fetched.
• Turn on "Fetch extra details per listing" only when you actually need the full description or category attributes — it adds one request (and one listing-details charge) per delivered listing.
• A BLOCKED status means Kleinanzeigen returned a 403, 429, or 503 — lowering "Max concurrency" or trying again shortly usually clears it; this actor doesn't need a proxy by default, and falls back to RESIDENTIAL automatically on a follow-up request that gets blocked.
• Paste your own already-filtered Kleinanzeigen search URL instead of rebuilding filters in this actor's Input tab — price range, private-seller-only, and offer/wanted carry straight through.
• Already have a list of known listing URLs instead of a search? Use Kleinanzeigen Listing Lookup — this actor's sibling for a single known link.

vs. Kleinanzeigen's own Suchauftrag, and vs. the Store leaders

Kleinanzeigen's own "Suchauftrag" (saved-search alert) lives inside a Kleinanzeigen account, sends alerts by email only, and isn't callable from a script, a Sheet, or an automation platform. This actor gives you the same "only tell me what's new" behavior as a plain HTTP call or a scheduled Apify Task with a webhook into whatever tool you actually use.

The two current Apify Store leaders for "kleinanzeigen scraper" (a growing incumbent with about 95 30-day users, and a smaller one around 43) both sell a plain search dump — neither offers new-listing or price-drop monitoring as a first-class mode. This actor works across any Kleinanzeigen category, adds monitoring as a first-class mode, and bills only for listings actually delivered.

Data & privacy

This actor reads public search results that anyone can see without logging in. It doesn't log in, solve CAPTCHAs, or reveal hidden contact details. Seller identity is off by default: you get a private/business flag and an anonymous seller hash so you can group listings by seller without names. Turning on seller info makes you responsible for having a lawful reason to process it. Contact-info-like strings (emails, phone numbers) inside a listing's description are always redacted to [redacted], regardless of that setting. Not affiliated with Kleinanzeigen / eBay Kleinanzeigen / Adevinta.

Is this allowed? It collects the same public listing data your browser shows, for the searches you choose. It's built for monitoring a search, not for copying the marketplace. Check that your use fits Kleinanzeigen's terms and your local law.

FAQ

Why is a row empty, or why does found say false? Either the input line was blank (status: BAD_FORMAT), Kleinanzeigen returned a 403/429/503 (status: BLOCKED), or the search matched nothing on Kleinanzeigen right now (status: NOT_FOUND). Check the message column for the specific reason. None of these are billed.

Am I charged for a quiet monitoring run? No. When monitoring finds nothing new and no price drops, you get one row with monitorStatus: NO_NEW_ROWS and listingCount: 0 — Actor.charge() only fires when listingCount is greater than zero.

What does "Fetch extra details per listing" actually fetch? One extra request per delivered listing to that listing's own Kleinanzeigen item page, for its full (redacted) description and category-specific attributes (mileage, condition, room count — whatever that category shows). It's billed as a separate listing-details event and is automatically skipped, at no charge, whenever the proxy configuration is set to RESIDENTIAL (

detailsStatus: DETAILS_SKIPPED_PROXY

Does it find sold listings? What is the sell-through rate? Kleinanzeigen doesn't publish sales, so no scraper can show a confirmed sale or the price it sold at. With monitoring and "Alert on gone listings" on, this actor reports listings that disappeared from your search since the last run (changeType: gone, delisted: most often sold, sometimes withdrawn), flags the likely sales (gonePresumedSold), and keeps sellThroughRate: the share of the listings the watchlist has tracked that went gone. See "Sold signal and sell-through" above for how it decides and its limits. Gone rows cost the same as any listing row.

Can I paste my own filtered Kleinanzeigen search instead of using this actor's filters? Yes. Paste the full search-results URL from your browser's address bar as a search line — price range, private-seller-only, and offer/wanted filters already in it carry through. Location/radius and the free-listings category are read too, best-effort, from the URL's own encoding.

Do I need to configure proxies? No. This actor uses Apify's default proxy configuration (no proxy group) out of the box — Kleinanzeigen didn't block any plain request from Apify's datacenter IPs during this actor's build and probe. A per-request RESIDENTIAL fallback (country DE) is wired in automatically for any follow-up request that does get blocked (page 2+, the details hop).

Does the offer/wanted filter call Kleinanzeigen's own server-side filter? No, on purpose. Kleinanzeigen's sidebar links for this filter use a URL shape (/s-anzeige:angebote/, /s-anzeige:gesuche/) that wasn't live-tested as a query parameter this build. Rather than guess a parameter value, this actor filters using Kleinanzeigen's own "Gesuch" (wanted) tag on the data it already fetched — the result is the same, just applied after the request instead of inside it.

Can an AI agent call this directly? Yes. It's registered on the Apify MCP server — an agent in Claude, Cursor, or another MCP client can find and run it by name ("Kleinanzeigen Scraper: New Listings & Price Alerts"), or you can call the REST endpoint shown above from any script or workflow tool.

Related actors

• Kleinanzeigen Listing Lookup — the sibling actor for a single known Kleinanzeigen listing URL, without search or monitoring.