# Kleinanzeigen Search: New Listing & Price Alerts (`accountable_eel/kleinanzeigen-search-lookup`) Actor

Kleinanzeigen.de scraper by keyword: one row per listing (title, price, location, image, link). Turn on monitoring for only new listings and price drops since your last run, replacing Kleinanzeigen's Suchauftrag alerts. No login required; empty searches and quiet runs are free.

- **URL**: https://apify.com/accountable\_eel/kleinanzeigen-search-lookup.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 $1.00 / 1,000 listing 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

## 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. 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
[marketplace contract](../..) 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.
- **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`).

| Field | Type | Description |
|---|---|---|
| `query` | text | The search you submitted, echoed back |
| `found` | boolean | `true` if Kleinanzeigen returned a real search-results page for this search |
| `status` | text | `OK` on a match; `NOT_FOUND`, `BLOCKED`, or `BAD_FORMAT` on a miss |
| `message` | text | Plain-English reason for a miss — only present when `found` is `false` |
| `searchQuery` | text | The keyword actually searched (parsed out of a pasted URL, if you gave one) |
| `listingCount` | number | Listings returned and billed for this search |
| `totalAvailable` | number | Total listings Kleinanzeigen reports matching this search, including ones not returned |
| `truncated` | boolean | `true` if more results existed than were returned |
| `newCount` | number | New listings this run (monitoring only) |
| `priceDropCount` | number | Price drops this run (monitoring only) |
| `detailsCount` | number | Listings this run fetched the item-page details for |
| `monitorStatus` | text | `NO_NEW_ROWS` on a quiet monitoring run, `WATCHLIST_SEEDED` on a silent first run, otherwise empty |
| `listingId` | text | Kleinanzeigen's own numeric ad ID |
| `url` | text (link) | Permanent listing link |
| `title` | text | Listing title |
| `price` | number | Price in EUR, or empty if the listing has no price |
| `priceType` | text | `fixed`, `negotiable` (VB / Verhandlungsbasis), `free`, or `on_request`, as the listing actually shows it |
| `currency` | text | Always `EUR` |
| `postalCode` | text | Seller's postal code |
| `city` | text | Seller's city |
| `postedAt` | date | Parsed posting time (from "Heute, HH:MM" / "Gestern, HH:MM" / an absolute date) |
| `postedText` | text | The raw posting-time text as Kleinanzeigen shows it |
| `description` | text | Short listing blurb (contact info redacted) |
| `imageUrl` | text (link) | First listing image |
| `isShippingOffered` | boolean | `true` if the seller offers shipping |
| `isPromoted` | boolean | `true` for a Kleinanzeigen "Top-Anzeige" (paid extra placement) |
| `sellerType` | text | `private` or `commercial`, from Kleinanzeigen's own Privat/Gewerblich flag |
| `sellerHash` | text | Anonymous, stable per-seller hash — always present, groups listings by seller with no name |
| `sellerId` | text | **Privacy-gated.** Kleinanzeigen's raw numeric user ID — only with "Include raw seller info" |
| `fullDescription` | text | **Details only.** Full (redacted) description text |
| `attributes` | object | **Details only.** Category-specific label/value pairs (mileage, condition, room count, etc.) |
| `detailsFetched` | boolean | `true` if the item-page hop ran for this row |
| `detailsStatus` | text | `DETAILS_SKIPPED_PROXY` when details were skipped because the proxy is RESIDENTIAL, `BLOCKED` on a failed hop, otherwise empty |
| `changeType` | text | `new`, `price-drop`, or `seen` (monitoring only) |
| `isNew` | boolean | `true` on this listing's first appearance (monitoring only) |
| `previousPrice` | number | The price last recorded for this listing, when it dropped (monitoring only) |
| `priceDropPct` | number | Percentage drop from the previous recorded price (monitoring only) |
| `firstSeenAt` | date | When this watchlist first saw this listing (monitoring only) |
| `scrapedAt` | date | When this row was fetched |

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

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed
per item only when data is actually found and returned — see
`.actor/pay_per_event.json` for exact prices. A miss is 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.

### 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.
- 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.

### 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~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.

### Input

```json
{
  "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

| query | found | status | searchQuery | listingCount | totalAvailable | truncated | newCount | priceDropCount | detailsCount | monitorStatus | listings | listingId | url | title | price | priceType | currency | postalCode | city | postedAt | postedText | description | imageUrl | isShippingOffered | isPromoted | sellerType | sellerHash | sellerId | fullDescription | attributes | detailsFetched | detailsStatus | changeType | isNew | previousPrice | priceDropPct | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| iphone | true | OK | <search> | <listings returned> | <total matching on kleinanzeigen> | <more results were available> | <new listings this run> | <price drops this run> | <listings with details fetched> | \<monitoring status (quiet / seeded runs)> | \<all listings found (full list)> | <kleinanzeigen ad id> | <listing link> | <title> | \<price (eur)> | \<fixed / negotiable / free / on\_request> | <currency> | <postal code> | <city> | \<posted (parsed)> | \<posted (raw, as shown on kleinanzeigen)> | \<description (short snippet)> | <image> | <shipping offered> | \<top ad / promoted> | \<private / commercial> | <anonymous seller hash> | \<seller id (privacy: only with "include raw seller info")> | \<full description (details only)> | \<category attributes (details only)> | <details were fetched for this row> | \<details\_skipped\_proxy / blocked, when details weren't fetched> | \<new / price-drop / seen> | \<is this listing new?> | \<previous price (eur)> | \<price drop %> | <first seen on a run> | 1970-01-01T00:00:00.000Z |

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.

```bash
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](https://apify.com/accountable_eel/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.

| | What it costs | What you get | Trade-off |
|---|---|---|---|
| **This actor** | Pay per listing returned; nothing for a miss or a quiet monitoring run | Any Kleinanzeigen category, monitoring mode (new + price drop), optional full description/attributes | Offer/wanted filtering happens after fetching (client-side), not as a server-side param |
| **Kleinanzeigen's own Suchauftrag** | Free, inside a Kleinanzeigen account | Email alerts for a saved search | Not callable from a script or automation platform; no price-drop alerting |
| Doing it yourself | Your time to build and maintain a scraper, a seen-listing store, and a price-tracking layer | The same data | This actor's parsing, monitoring state, and redaction are the maintenance burden it absorbs |

### 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`).

**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](https://apify.com/accountable_eel/kleinanzeigen-listing-lookup) —
  the sibling actor for a single known Kleinanzeigen listing URL, without search or monitoring.

# Actor input Schema

## `searches` (type: `array`):

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. 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. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip 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.

## `sort` (type: `string`):

Kleinanzeigen's search already sorts by newest first by default (confirmed live) — this is kept for consistency with the rest of this catalogue's marketplace actors and is always forced to newest whenever monitoring is on.

## `maxListingsPerSearch` (type: `integer`):

Kleinanzeigen shows about 25 listings per page; this actor pages up to 40 times to reach your limit. You pay per listing returned, so this is also your budget control.

## `minPrice` (type: `integer`):

Optional. Applied as Kleinanzeigen's own price filter. Leave empty for no minimum.

## `maxPrice` (type: `integer`):

Optional. Applied as Kleinanzeigen's own price filter. Leave empty for no maximum.

## `sellerType` (type: `string`):

Kleinanzeigen's own "Privat" / "Gewerblich" filter.

## `adType` (type: `string`):

Applied after fetching, using Kleinanzeigen's own "Gesuch" tag on a listing — this actor's query-param form of Kleinanzeigen's offer/wanted filter wasn't live-tested this build, so filtering happens on the data actually returned rather than risk a silently wrong server-side filter.

## `freeOnly` (type: `boolean`):

Restricts the search to Kleinanzeigen's own "Zu verschenken & Tauschen" (free / to give away) category.

## `location` (type: `string`):

Optional. A German city name or postcode, e.g. "Berlin" — Kleinanzeigen resolves it server-side. Leave empty to search all of Germany.

## `radiusKm` (type: `integer`):

Only used together with "Location" above.

## `deltaMode` (type: `boolean`):

Turns this actor into a monitor — the buyer-facing replacement for Kleinanzeigen's own "Suchauftrag" saved-search email alert. A listing counts as new when its Kleinanzeigen ad ID has not been returned by a previous run of the same watchlist, and as a price drop when its price falls since it was last seen (see "Minimum price drop" below). Already-seen, unchanged listings are dropped before you are billed, so a quiet run costs only the run fee. The first run has nothing to compare against, so (unless "Seed silently" is on) it returns everything and remembers it.

## `deltaName` (type: `string`):

Leave empty and we derive one from this run's search settings, so two schedules with different settings keep separate memories. Type your own name to keep one memory across a settings change, or to have two schedules share one.

## `alertOnNew` (type: `boolean`):

On by default. Turn off to have this watchlist report price drops only, not brand-new listings.

## `alertOnPriceDrop` (type: `boolean`):

On by default. Turn off to have this watchlist report new listings only, ignoring price changes on ones you've already seen.

## `minPriceDropPct` (type: `integer`):

A listing must drop by at least this percentage since it was last seen to be reported as a price-drop.

## `skipFirstRun` (type: `boolean`):

Instead of returning every current listing as "new" the first time a watchlist runs, this banks them silently and starts alerting from the second run on. Stops a fresh watchlist from spamming a hundred messages to your webhook on day one.

## `includeDetails` (type: `boolean`):

Off by default. When on, this actor makes one extra request per returned listing to that listing's own Kleinanzeigen item page, for its full (redacted) description and category-specific attributes (e.g. vehicle mileage, item condition) — billed as a separate "listing-details" event. Automatically skipped, at no charge (status DETAILS\_SKIPPED\_PROXY), whenever the proxy below is set to RESIDENTIAL.

## `includeSellerInfo` (type: `boolean`):

Off by default. When on, adds the seller's raw numeric Kleinanzeigen user ID (sellerId) to every row, in addition to the always-on anonymous sellerHash. Kleinanzeigen doesn't expose a seller display name on this route. Turning this on makes you responsible for having a lawful reason to process it.

## `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": [
    "iphone"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "sort": "newest",
  "maxListingsPerSearch": 50,
  "sellerType": "any",
  "adType": "any",
  "freeOnly": false,
  "location": "",
  "deltaMode": false,
  "deltaName": "",
  "alertOnNew": true,
  "alertOnPriceDrop": true,
  "minPriceDropPct": 5,
  "skipFirstRun": false,
  "includeDetails": false,
  "includeSellerInfo": false,
  "columns": [
    "searchQuery",
    "listingCount",
    "totalAvailable",
    "truncated",
    "newCount",
    "priceDropCount",
    "detailsCount",
    "monitorStatus",
    "listings",
    "listingId",
    "url",
    "title",
    "price",
    "priceType",
    "currency",
    "postalCode",
    "city",
    "postedAt",
    "postedText",
    "description",
    "imageUrl",
    "isShippingOffered",
    "isPromoted",
    "sellerType",
    "sellerHash",
    "sellerId",
    "fullDescription",
    "attributes",
    "detailsFetched",
    "detailsStatus",
    "changeType",
    "isNew",
    "previousPrice",
    "priceDropPct",
    "firstSeenAt"
  ],
  "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": [
        "iphone"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/kleinanzeigen-search-lookup").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": ["iphone"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/kleinanzeigen-search-lookup").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": [
    "iphone"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/kleinanzeigen-search-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/kleinanzeigen-search-lookup"
        }
    }
}
```

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/RXBmNAWEen8QM2c16/builds/woSF3nhUtEmWxkUO0/openapi.json