# Kleinanzeigen Scraper (Germany) (`hexagone-data/kleinanzeigen-scraper`) Actor

Scrape Kleinanzeigen.de ads from a search, a category or an ad URL. Searches above the site's 1,250-row limit are split automatically; what cannot be reached is counted in the summary. One ad is one row and one charge.

- **URL**: https://apify.com/hexagone-data/kleinanzeigen-scraper.md
- **Developed by:** [Hexagone Data](https://apify.com/hexagone-data) (community)
- **Categories:** E-commerce, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.27 / 1,000 ads

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 Scraper (Germany)

Scrape ads from **Kleinanzeigen.de**: type search terms with a location, or paste a search, a category or an ad URL, and get one row per ad: title, price as shown and as a number, postal code and place, date, images, seller type, Top flag. Turn on `includeDetails` to also read each ad's own page: full text, properties, category, status, the seller's display name and profile link.

What you get:

- **Searches above the site's 1,250-row limit are split automatically; what cannot be reached is counted in the summary.** The site shows 50 pages of 25 rows, then silently repeats the last page. This Actor splits the search on its own, by location, attribute, category and price. Real runs on 2026-11-04: `iphone 13`, 20,225 of 20,394 ads, in 387 slices; `klavier` in Berlin, 1,507 of 1,507; `zu verschenken` in Hamburg, 1,255 of 3,754: no filter left to split it.
- **Every summary compares what was read to what was announced.** For each address: ads announced, ads read, how many are missing and why, pages lost, slices, access level. A search that falls short ends as `partial_collection` with the numbers, not as `done`.
- **One ad, one row, one charge.** Paid Top ads come back on several pages (measured: 1,074 rows for 1,037 ads on `waschmaschine` in Köln). They are removed before anything is delivered or charged, and the summary counts the Top rows seen again (`topAdRepeatsRemoved`).
- **One ad, one row: the extra "results in other towns" the site adds below small searches are not delivered or charged, and sellers advertising from further away are flagged (isExtendedRadius).**
- **No browser and no account.** The search pages themselves; a proxy only when the site refuses (see Known limits).

### Try it with 20 ads

1. Keep the prefilled input: search term `Thermomix`, location `Leipzig`, **Maximum number of ads = 20**.
2. Click **Start**. You pay for 20 ads: $0.0126, start fee included.
3. Open **Ads overview** for the table, **Run summary** for what was read against what was announced.

### What to paste

| You paste or type | Example | What you get |
|---|---|---|
| Search terms + location | `Thermomix` + `Leipzig`, with `radiusKm` if you want one | One search per term, solved by the site. If the site does not know the place, the search is refused (`location not found`) rather than run on all of Germany |
| A search URL, filters included | `https://www.kleinanzeigen.de/s-berlin/klavier/k0l3331`, `.../s-anbieter:privat/preis:100:500/fahrrad/k0` | That whole search. A page number in the URL is removed |
| A category or a place | `https://www.kleinanzeigen.de/s-autos/c216`, `https://www.kleinanzeigen.de/s-dresden/l3820` | Very large lists: set **Maximum number of ads** |
| One ad, also the URL after clicking a card | `https://www.kleinanzeigen.de/s-anzeige/<slug>/<id>-<cat>-<place>`, `https://www.kleinanzeigen.de/s-anzeige/<id>` | This ad with its full details |

`kleinanzeigen.de`, `m.kleinanzeigen.de` and `ebay-kleinanzeigen.de` are read as `www.kleinanzeigen.de`. Refused with a message, before any request: other sites, the home page, unknown pages, seller profiles (`/s-bestandsliste.html`), shops (`/pro/`).

| Option | Default | Effect |
|---|---|---|
| `maxItems` | 1000 | Stops at exactly this number across the run. 0 = no limit on the number of ads; the time limit of the run still applies (see Known limits) |
| `includeDetails` | false | Reads each ad's page; adds the paid `ad-details` event per page really read |
| `splitLargeSearches` | true | Off: no splitting, stops at 1,250 rows and the summary says how many are missing |
| `proxyConfiguration` | none | Replaces the automatic ladder, as you set it |

### Output

One row per ad. Unknown values are `null`, never invented. Example with `includeDetails` (a real row of a real run, 2026-11-04, copied as delivered):

```json
{
  "adId": "2656865500",
  "url": "https://www.kleinanzeigen.de/s-anzeige/zaunteam-sprint-beton-fuer-heimwerker-und-profis/2656865500-84-1542",
  "title": "Zaunteam Sprint-Beton für Heimwerker und Profis",
  "description": "Spezial-Zaunteam-Sprint-Beton 25kg für nur 6,00€ (inkl. MWST). Der Spezial-Zaunteam-Sprint Beton eignet sich hervorragend zum schnellen Einbetonieren von Zaun- und Torpfosten, sowie zum Erstellen von Kleinfundamenten für z.B. Bodenhülse für Wäschespinnen, Fahnenmäste, Rosenbögen, Kinderspielgeräte, Gartenbänke, Gartenhäuser usw. Vorteile: -Erhärtung bereits nach 5 Minuten- Betonieren ohne Mischen- spart Zeit und Geld -Einfach, schnell und sicher.",
  "descriptionComplete": true,
  "priceText": "6 €",
  "price": 6,
  "priceType": "fixed",
  "previousPrice": null,
  "currency": "EUR",
  "postalCode": "51674",
  "locality": "Wiehl",
  "distanceKm": null,
  "isExtendedRadius": null,
  "availabilityRadiusKm": null,
  "badges": [],
  "postedAtText": null,
  "postedDate": null,
  "postedTime": null,
  "imageUrls": [
    "https://img.kleinanzeigen.de/api/v1/prod-ads/images/51/512a643a-7b02-4639-8daf-0b3d3483df78"
  ],
  "imageCount": 1,
  "sellerType": "commercial",
  "sellerIsPro": true,
  "storeName": "Zaunteam Südwestfalen",
  "storeUrl": "https://www.kleinanzeigen.de/pro/zaunteam-suedwestfalen",
  "adType": "offer",
  "shippingAvailable": null,
  "buyNowAvailable": null,
  "listingTags": [],
  "isTopAd": null,
  "isHighlight": null,
  "isPriorityAd": null,
  "hasVideo": null,
  "hasVirtualTour": null,
  "sourceUrl": "https://www.kleinanzeigen.de/s-anzeige/zaunteam-sprint-beton-fuer-heimwerker-und-profis/2656865500-84-1542",
  "scrapedAt": "2026-11-05T01:33:32+00:00",
  "detailsStatus": "ok",
  "adStatus": "active",
  "createdDate": "2024-01-19",
  "region": "Nordrhein-Westfalen",
  "categoryId": "84",
  "categoryPath": [
    "Haus & Garten",
    "Heimwerken"
  ],
  "properties": [
    {
      "name": "Zustand",
      "value": "Neu"
    }
  ],
  "features": [],
  "shippingText": "Nur Abholung",
  "streetAddress": null,
  "latitude": 50.9482553,
  "longitude": 7.5158602,
  "sellerName": "Zaunteam Südwestfalen",
  "sellerSince": "2019-02-18",
  "sellerWebsite": "https://www.zaunteam.de/de/partner/46-zaunteam-sudwestfalen",
  "imprint": "Borgard Zaun und Tor GmbH Werner-von-Siemens-Straße 4 51674 Wiehl Deutschland Tel.: 02261 / 5492191 suedwestfalen@zaunteam.de Geschäftsführer: Joachim Borgard, Felix Borgard UST-ID: DE 320 168 445",
  "sellerProfileUrl": "https://www.kleinanzeigen.de/pro/zaunteam-suedwestfalen",
  "sellerId": null,
  "contactInText": false,
  "extractedPhones": [],
  "extractedEmails": []
}
```

This example comes from a pasted ad URL: what exists only on a list card (`isTopAd`, `badges`, `postedAtText`) is empty. Without `includeDetails`, a row stops at `detailsStatus` (`not_requested`) and `description` is the list excerpt: `descriptionComplete` says so. `detailsStatus` can also be `failed` (the page could not be read, or the run reached its time limit before reading it) or `removed` (the ad left the site): the row is then delivered from its list card, with the detail fields empty.

`isExtendedRadius` is `true` when the seller advertises a service radius and comes to you from further away than the search area, as the site's "Kommt zu dir" tag says (`availabilityRadiusKm` gives the radius). These ads count in the site's own total and are delivered, flagged.

### Run summary

The `OUTPUT` record and the `SUMMARY` page give one line per address, plus the total of the run:

| Field | Meaning |
|---|---|
| `url`, `status` | The address; `done`, `partial_collection`, `no_results`, `max_items_reached`, `max_charge_reached`, `not_processed`, `location_not_found`, `ad_not_available`, `not_found`, `access_refused`, `internal_error`, `time_limit` (the run reached its time limit before finishing or reaching this address), `interrupted` (the run was stopped from outside while reading; what was read so far is counted. A run you abort yourself can end without a summary, its rows stay in the dataset) |
| `resolvedLocation` | The place the site understood, as it writes it (`Freiburg (Elbe) - Niedersachsen`); `null` if the page gives none. With search terms and a location, the `message` says so when your name is not that place: `the site read "Freiburg" as "Freiburg (Elbe) - Niedersachsen"` |
| `totalAnnounced`, `totalAtEnd` | The site's total at the start, and read again after the last page |
| `adsDistinct`, `missing`, `missingVsAnnounced` | Distinct ads read for this address, and how many of the announced ones were not, against the larger of `totalAnnounced` and `totalAtEnd` (the last two are the same number; `done` allows 1 ad or 1.5 %, because the site's total moves during a read) |
| `delivered` | New rows from this address. An ad already delivered by an earlier address is read, not written or charged again |
| `pages`, `pagesFailed` | List pages read; pages lost after 8 refusals in a row. A lost page means the address is not `done` |
| `slices`, `slicesOverCap` | Parts the search was read in; parts still above 1,250 rows after every split |
| `topAdRepeatsRemoved` | Top rows that repeat an ad already read for this address, removed. A normal row that repeats an earlier Top row is removed too, but not counted here, so the rows removed can be more than this number |
| `topAdSeenAfterDelivery` | Ads shown as Top only after their row was written |
| `accessLevel`, `refusals` | `direct`, `apify_auto`, `residential_de` or `client_proxy`; refusals met |
| `detailsRead`, `detailsFailed`, `detailsRemoved` | Ad pages read, failed, gone |
| `oldTemplateRereads` | Ad pages read once again because they came on the older page; not charged |
| `reducedDetails` | `true` when ad pages of this address were read in the site's lighter page, through a residential proxy (see Known limits). The run total says the same |
| `message` | What happened, with the numbers |

The run total adds `timeLimitReached` and `maxChargeReached`, `true` when that limit stopped the run.

A run that delivers no ad ends as failed, with the reason: an empty search and a refusal by the site are told apart. The start fee is still charged.

### Pricing

Pay per event. A run costs a start fee of $0.005, also when it delivers no ad, plus:

- **Ad**: $0.38 per 1,000 ads delivered.
- **Full ad details** (`ad-details`): $0.60 per 1,000 ad pages really read, with `includeDetails` or for a pasted ad URL. Not charged when the page could not be read (`failed`) or the ad was removed from the site (`removed`).

| | 20 ads | 1,000 ads |
|---|---|---|
| Without details | $0.0126 | $0.385 |
| With details | $0.0246 | $0.985 |

These totals include the start fee and use the Free plan's prices. Paid Apify plans get a discount on Ad: 10% on the Bronze plan, 20% on Silver, 30% on Gold and above. Full ad details cost the same on every plan: no tier discount on them. A maximum charge per run stops the run before it is passed, and the summary says so.

### Known limits

- **Private sellers: display name and profile link, nothing more.** With details, `sellerName`, `sellerProfileUrl` and `sellerId` are filled when the page shows them. Street, GPS, member-since date, website and legal notice stay `null`, and `extractedPhones` and `extractedEmails` stay empty. Professional sellers keep their name, shop link, address and legal notice.
- **The ad's text is delivered as written.** It can contain a first name or a phone number written by the seller. For a private seller, `contactInText` only says `true` or `false`; the number is not put in a field.
- **Phones and e-mails written in the text are read by rules, with details only.** Values are copied as written, with no digit or country code added. A price, a date, a postal code, a fax number or a site-masked number does not count. A landline number without a country prefix is read only when a phone word stands before it, because part numbers look the same, so a landline with no such word is missed. A part number placed right after such a word, shaped like a German mobile number or starting like a `0041` country code, can still be counted, and so can a fax written `F.` after a phone number. A mobile number of 10 digits with no phone word is missed. A number written in words or glued to a word (`Tel0176...`) is missed, so is an address written `name at site.de` or `name @ site.de`.
- **Personal data.** These fields are personal data under the GDPR. You are responsible for how you use them.
- **The phone number behind the login is not read.** No account is used.
- **No view count.** The site's counter goes up each time it is read, so it is never called.
- **No shops**: `/pro/` pages are refused for now. Paste a search or an ad instead.
- **Ads without an amount and huge categories can stay partial.** Ads without an amount are in no price slice and come last in price sorts; they are looked for in the newest 1,250 rows of each slice. Slices with nothing left to split them are read in up to 4 sort orders. What stays behind is counted in `missing`, with `partial_collection`. Measured sizes reach 10,443,240 ads for one category: set `maxItems` there.
- **The site chooses the place for a name.** `Freiburg` is read as Freiburg (Elbe), not Freiburg im Breisgau: no error, another town. The summary gives the place it read (`resolvedLocation`) and the `message` tells you when it differs from your name. Use a postal code to be sure.
- **A run stops 2 minutes before its time limit (4 hours by default, you can raise it) with a summary.** Addresses not finished end as `time_limit`, with what was read against what was announced; ads already read are delivered, ad pages not read yet stay `failed` and are not charged. So `maxItems: 0` means as many ads as the time limit allows, not the end of a huge category: at the speed measured on 2026-11-04, about 120,000 ads in 4 hours without details, about 46,000 with. Set `maxItems` or a maximum charge to control the cost. To go further, raise the time limit and start a new run: it reads from the first ad again and charges again; resurrecting a finished run reads nothing more.
- **No filter left, no way past 1,250 rows.** Some pages have no price filter and no location facet (`zu verschenken` in Hamburg: 1,255 read of 3,754 announced). No price slice is tried there; the search stays `partial_collection`, and `message` says `no filter left to split this search on the site`.
- **The order changes when a search is split.** Rows come slice by slice, not in the site's order. A search of 1,250 ads or fewer keeps the site's order; set `sortierung:` in your URL to choose it.
- **`isTopAd`** is set when the ad was shown as Top on a page read before its row was written. An ad shown as Top later, in another slice or address, keeps `false`; `topAdSeenAfterDelivery` counts them.
- **The site can refuse a whole range of addresses.** The run then pauses, opens a new session and moves up: Apify datacenter proxy, then German residential proxy after 5 refusals in a row on the datacenter proxy, each on a new session. It does not move back down during the run. The summary gives the level and the refusals (`accessLevel`, `refusals`). Residential traffic is on our side; the price above does not change.
- **Residential reads are lighter.** When the run has to use a residential proxy, ads are read in the site's lighter page: createdDate, sellerWebsite and imprint stay null. `reducedDetails` tells you, and `oldTemplateRereads` stays at 0 for those reads. This also applies to your `proxyConfiguration` when it uses the `RESIDENTIAL` group, another group we do not know, or your own proxy URLs.
- **An older ad page exists.** The first ad page of a session comes on an older page, which shows no creation date, website or legal notice. Without a residential proxy it is read once again in that session; ads that stay on it (some property categories) are delivered with `createdDate`, `sellerWebsite` and `imprint` at `null`. `oldTemplateRereads` counts these reads, which are not charged.

### Support

Open an issue on the Actor's **Issues** tab with the run link. This Actor is not affiliated with Kleinanzeigen or with its owners. It reads public pages without an account. Your use of the data must follow the law, including data protection rules.

# Actor input Schema

## `searchTerms` (type: `array`):

One search per term, as typed in the site's search box (e.g. Thermomix). The location and radius below apply to these searches.

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

A city, a postal code or a German state, as typed on the site (e.g. Leipzig, 04109, Bayern). Empty: all of Germany. If the site does not know this place, the search is refused with the message 'location not found' rather than run on all of Germany. The site picks one place for a name: Freiburg is read as Freiburg (Elbe), not Freiburg im Breisgau. resolvedLocation in the run summary gives the place it read; use a postal code to be sure.

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

0, 5, 10, 20, 30, 50, 100, 150 or 200, as on the site. Needs a location.

## `startUrls` (type: `array`):

Kleinanzeigen URLs exactly as your browser shows them, filters included: a search (https://www.kleinanzeigen.de/s-berlin/klavier/k0l3331), a category (https://www.kleinanzeigen.de/s-autos/c216), or one ad (https://www.kleinanzeigen.de/s-anzeige/<slug>/<id>-<cat>-<place>). A page number in the URL is removed: the whole search is read. Seller profiles (s-bestandsliste) and shops (/pro/) are refused with a message. A remote list of URLs is not supported.

## `maxItems` (type: `integer`):

Stops at exactly this number across all searches. 0 = no limit on the number of ads: the run reads every search until it stops 2 minutes before its time limit, with a summary.

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

Reads each ad's own page: full text, properties, equipment, category, status, the seller's display name and profile link, a yes/no for a phone number or e-mail written in the text, and a professional seller's address, legal notice and written contacts. This adds a paid event per page really read (see Pricing).

## `splitLargeSearches` (type: `boolean`):

The site shows 1,250 rows per search at most. On: the search is split by location, attribute, category and price; what cannot be reached is counted in the summary. Off: it stops at 1,250 rows and the summary says how many are missing.

## `proxyConfiguration` (type: `object`):

Optional. Replaces the automatic ladder (no proxy, then Apify datacenter proxy, then German residential proxy, only when the site refuses). Turning the proxy off is respected. With a residential proxy, a group we do not know or your own proxy URLs, ads are read in the site's lighter page: createdDate, sellerWebsite and imprint stay null.

## Actor input object example

```json
{
  "searchTerms": [
    "Thermomix"
  ],
  "location": "Leipzig",
  "maxItems": 20,
  "includeDetails": false,
  "splitLargeSearches": true
}
```

# Actor output Schema

## `ads` (type: `string`):

All ad records, one per ad, with every field.

## `adsOverview` (type: `string`):

Title, price, location, date, seller type, link.

## `summary` (type: `string`):

Readable per-address summary: status, ads read against the total announced, slices, pages lost, access level, reason for anything missing.

## `summaryJson` (type: `string`):

The same summary as JSON (OUTPUT record).

# 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 = {
    "searchTerms": [
        "Thermomix"
    ],
    "location": "Leipzig",
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("hexagone-data/kleinanzeigen-scraper").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 = {
    "searchTerms": ["Thermomix"],
    "location": "Leipzig",
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("hexagone-data/kleinanzeigen-scraper").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 '{
  "searchTerms": [
    "Thermomix"
  ],
  "location": "Leipzig",
  "maxItems": 20
}' |
apify call hexagone-data/kleinanzeigen-scraper --silent --output-dataset

```

## MCP server setup

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

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/pf3SwZNPg0D4Solhw/builds/9RKBsBDF4uT0ExgND/openapi.json
