Kleinanzeigen.de Germany Listings Scraper

Kleinanzeigen Scraper is a direct marketplace-scraping rival for buyers seeking German classifieds data, while this actor makes the collection controls and output semantics explicit: keyword or reusable search URL, category, location, radius, price, seller type, pagination, and normalized price labels. The practical gap is not an unsupported claim of superiority; it is clearer operational guidance for bounded, repeatable search-result collection and validation in an Apify dataset.

The same rival category often emphasizes fast listing retrieval without explaining whether results come from search cards or complete detail pages. This actor fairly narrows that promise: it focuses primarily on listings visible in search results and exposes fields such as price_type, location_zip, seller_type, image_count, and parse_confidence when available. That transparency helps resale researchers and price-monitoring teams decide what still needs manual review instead of assuming complete detail-page coverage.

What this actor does

The actor searches Kleinanzeigen.de and writes normalized listing records to the default Apify dataset. It supports:

• Keyword searches with query.
• Reusable Kleinanzeigen search URLs with searchUrl.
• Category, city or ZIP code, radius, and price filters.
• all, privat, or gewerblich seller-type selection.
• Bounded or unrestricted result collection through maxItems.
• Pagination through available search-result pages.
• Normalization of fixed, negotiable, free, and price-on-request price labels.
• JSON or CSV export from Apify.

Inputs

You can provide either query or searchUrl. When both are supplied, searchUrl takes precedence.

Input	Type	Description
query	string	Search keyword or keywords, such as iphone 14, fahrrad, or sofa.
searchUrl	string	Complete Kleinanzeigen search URL.
categoryId	string	Optional numeric category ID.
locationName	string	Optional German city name or ZIP code, such as Berlin or 10115.
radiusKm	integer	Search radius around the location; default is 30 when applicable.
priceMin	integer	Optional minimum price in EUR.
priceMax	integer	Optional maximum price in EUR.
sellerType	string	all, privat, or gewerblich; default is all.
maxItems	integer	Maximum number of listings; the documented default is 100, and 0 means all available results.
proxyConfiguration	object	Apify proxy settings. German residential access may be useful when source behavior differs for datacenter traffic.

Example input

{
  "query": "iphone 14",
  "locationName": "Berlin",
  "radiusKm": 30,
  "priceMin": 200,
  "priceMax": 600,
  "sellerType": "all",
  "maxItems": 50
}

A direct search URL can be used instead:

{
  "searchUrl": "https://www.kleinanzeigen.de/s-iphone/k0",
  "maxItems": 25
}

Output

Typical dataset records may include:

• title
• price
• price_type
• condition
• location_zip
• location_city
• seller_name
• seller_type
• posted_date
• url
• image_count
• parse_confidence

Example record shape:

{
  "title": "iPhone 14 128GB",
  "price": 420,
  "price_type": "fixed",
  "condition": "used",
  "location_zip": "10115",
  "location_city": "Berlin",
  "seller_name": "Example seller",
  "seller_type": "privat",
  "posted_date": "2026-01-15",
  "url": "https://www.kleinanzeigen.de/s-anzeige/example/1234567890",
  "image_count": 5,
  "parse_confidence": 0.96
}

The actual fields and values depend on the source response and current implementation. Inspect representative records before creating a downstream schema.

Buyer workflows

Price monitoring

Repeat the same query, search URL, location, radius, and price limits to compare listings over time. Store run dates and input settings with exported data.

Resale sourcing

Search a product and geographic area, use price and seller filters to narrow candidates, then open the source URL and manually verify condition, availability, and seller claims before acting.

Local market research

Build a bounded dataset for a product category, city, ZIP code, or price band. Use normalized price_type and location fields to compare results consistently.

Review queues

Collect a conservative number of records, sort or filter by parse_confidence, and send selected URLs to a human review process rather than treating parsed cards as verified offers.

Limitations

The actor primarily processes listing cards available in search results. It does not promise complete detail-page crawling, complete marketplace coverage, or every field for every listing. Results may be incomplete or unavailable because of source-page changes, pagination behavior, filters, access conditions, anti-bot responses, proxy behavior, or listing-specific markup.

A successful run is not proof that the returned set is exhaustive, current, accurate, or legally reusable. Review source URLs and confidence values, especially before pricing, purchasing, contacting sellers, or making business decisions. Respect Kleinanzeigen terms, applicable laws, privacy requirements, rate limits, and restrictions on storing or redistributing personal information.

Recommended workflow

1. Start with a focused query or a known searchUrl.
2. Use a small maxItems value to validate parsing and fields.
3. Add location, radius, price, category, or seller filters only as needed.
4. Inspect titles, prices, locations, URLs, and parse_confidence.
5. Confirm the source pages manually for high-value or sensitive decisions.
6. Scale the run and export the verified dataset as JSON or CSV.
7. For monitoring, preserve the input parameters and run timestamp for meaningful comparisons.