# Kleinanzeigen Listing Lookup: Germany Classifieds API (`accountable_eel/kleinanzeigen-listing-lookup`) Actor

Look up any Kleinanzeigen.de listing: title, price, location, description, and the full category-specific details list (mileage, brand, condition, and more). Pay only for listings that resolve. No charge on removed or invalid listing URLs.

- **URL**: https://apify.com/accountable\_eel/kleinanzeigen-listing-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.52 / 1,000 successful lookups

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Kleinanzeigen Listing Lookup

Look up any [Kleinanzeigen.de](https://www.kleinanzeigen.de) listing — title, price,
location, description, and the full category-specific details list (mileage, brand,
condition, and more) — from Germany's dominant classifieds marketplace, covering
everything from cars and real estate to electronics and jobs.

### Features

- **Core listing fields.** Title, price (both raw text and a parsed numeric value),
  location, full description text, and the ad ID.
- **Category-specific details.** A generic label/value `details` object that covers
  whatever attribute list the listing shows — vehicle mileage, real-estate room count,
  item condition, and more — without needing a separate schema per category.
- **Listing image.** The preview image URL pulled from the page's Open Graph tags.
- **Pay only for hits.** Removed or invalid listing URLs cost nothing — see
  [Pricing](#pricing).

### How to use Kleinanzeigen Listing Lookup — Germany Classifieds API

1. **In the Apify Console.** Open the actor page and click **Start** — the `items` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~kleinanzeigen-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"items":["https://www.kleinanzeigen.de/s-anzeige/hyundai-getz-cross-1-4-klima-8x-1-hand-s-heft-tuev-10-27/3495798211-216-989"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "items": ["https://www.kleinanzeigen.de/s-anzeige/audi-q3.../3489456174-216-2284"],
  "maxConcurrency": 5,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

`items` is the only required field — a list of full Kleinanzeigen.de listing URLs (the
`/s-anzeige/...` permalink). A bare path is also accepted and expanded onto the domain
automatically. One dataset row is returned per item; rows with `"found": false` are
never charged. `maxConcurrency` (default 5, up to 20) controls how many requests run
in parallel. `proxyConfiguration` defaults to the **Residential** proxy group — plain
datacenter IPs can get a 403 from this target even though a residential IP succeeds.

### Output

```json
{
  "query": "https://www.kleinanzeigen.de/s-anzeige/audi-q3.../3489456174-216-2284",
  "found": true,
  "data": {
    "adId": "3489456174",
    "title": "Audi Q3 2.0 TDI quattro S line",
    "priceText": "24.500 € VB",
    "priceValue": 24500,
    "locality": "10115 Berlin",
    "description": "Gepflegter Audi Q3 aus erster Hand, scheckheftgepflegt...",
    "details": {
      "Kilometerstand": "68.000 km",
      "Erstzulassung": "03/2019",
      "Kraftstoffart": "Diesel",
      "Fahrzeugzustand": "Gebraucht"
    },
    "image": "https://img.kleinanzeigen.de/api/v1/prod-ads/images/...",
    "url": "https://www.kleinanzeigen.de/s-anzeige/audi-q3.../3489456174-216-2284"
  },
  "scrapedAt": "2026-08-20T12:00:00.000Z"
}
```

A removed, expired, or invalid listing URL redirects to the category browse page,
which has none of the listing elements above — that's used as the not-found signal, so
you get a dataset row with `"found": false`, but you're never charged for it.

### Use cases

- **Vehicle/marketplace price comparison** — pull structured price and detail fields
  across a shortlist of listings instead of reading each page manually.
- **Listing monitoring** — re-check a saved set of listing URLs over time; a removed or
  sold listing flips to `found: false`.
- **Category-specific data extraction** — the generic `details` object surfaces
  whatever attributes a category shows (mileage and fuel type for cars, room count for
  real estate, condition for electronics) without a custom parser per category.
- **Lead sourcing** — collect structured listing data from a set of URLs gathered
  elsewhere (search exports, saved searches) into one clean table.

### Pricing

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

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

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

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~kleinanzeigen-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"items":["https://www.kleinanzeigen.de/s-anzeige/hyundai-getz-cross-1-4-klima-8x-1-hand-s-heft-tuev-10-27/3495798211-216-989"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~kleinanzeigen-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"items":["https://www.kleinanzeigen.de/s-anzeige/hyundai-getz-cross-1-4-klima-8x-1-hand-s-heft-tuev-10-27/3495798211-216-989"]}` (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-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"items":["{{value}}"]}`, mapping the row's value into the `items` array.

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

### FAQ

**What counts as "not found"?**
A removed, expired, or fabricated listing URL redirects to Kleinanzeigen's category
browse page, which has none of the listing-specific elements this actor extracts.
That's used directly as the not-found signal.

**Why does this default to a Residential proxy?**
Plain datacenter IPs have been observed getting blocked with an HTTP 403 on this
target even when a request from a residential IP succeeds — the Residential proxy
group is the default for a reliable found rate. You can override
`proxyConfiguration` if you have your own proxy setup.

**Can I submit a listing path instead of the full URL?**
Yes — a bare path (e.g. `/s-anzeige/...`) is expanded onto `www.kleinanzeigen.de`
automatically. Submitting the full URL is recommended for clarity.

**What's in the `details` field?**
Whatever category-specific attribute list the listing page shows, as label/value
pairs — vehicle mileage and fuel type, real-estate room count, item condition, and so
on. The fields present vary by listing category.

**Does this cover every Kleinanzeigen category?**
Yes — the extraction targets generic id-tagged elements present on every listing page
regardless of category (vehicles, real estate, electronics, jobs, services), plus the
category-specific `details` list.

**Can I run this against a large batch of listing URLs?**
Yes — `maxConcurrency` controls how many requests run in parallel (default 5, up to
20\).

# Actor input Schema

## `items` (type: `array`):

One item per line — see the item shape and examples below. Only the items we actually find are charged — never per run, and never for a miss.

## `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. Defaults to Residential — this target returns HTTP 403 through the shared datacenter proxy pool even though a plain request from a residential IP succeeds.

## Actor input object example

```json
{
  "items": [
    "https://www.kleinanzeigen.de/s-anzeige/ford-ecosport-titanium-erst-19-200-km-/3489647313-216-1712"
  ],
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 = {
    "items": [
        "https://www.kleinanzeigen.de/s-anzeige/ford-ecosport-titanium-erst-19-200-km-/3489647313-216-1712"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/kleinanzeigen-listing-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 = { "items": ["https://www.kleinanzeigen.de/s-anzeige/ford-ecosport-titanium-erst-19-200-km-/3489647313-216-1712"] }

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/kleinanzeigen-listing-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 '{
  "items": [
    "https://www.kleinanzeigen.de/s-anzeige/ford-ecosport-titanium-erst-19-200-km-/3489647313-216-1712"
  ]
}' |
apify call accountable_eel/kleinanzeigen-listing-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/kleinanzeigen-listing-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/U1N9aoBEggxnLdTGy/builds/ivrKGR6Pie2UXbdeD/openapi.json