Catalog / Retail, marketplaces & classifieds
RETAIL, MARKETPLACES & CLASSIFIEDS · GERMANY
Kleinanzeigen | German Classifieds & Immobilien
Scrape kleinanzeigen.de classifieds by keyword, category, city and radius, or paste a search URL.
About this data
Scrape kleinanzeigen.de classifieds by keyword, category, city and radius, or paste a search URL. Get prices, sellers, photos and dates, with optional full details and rent fields for apartments. Each unique listing is charged once.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/de/kleinanzeigen/listings
Records include listing IDs, titles, category paths, locations, posting times, seller type, description excerpts, image URLs and source URLs.
Fetch one results page with up to 20 Kleinanzeigen listings.
Filter by keyword, category, location/radius and price.
EUR prices and price type appear where stated.
No listing-detail or seller-profile pages are fetched.
Input
Send a JSON body to POST https://api.ssh.autos/v1/de/kleinanzeigen/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
keyword | string | optional | up to 150 characters; default "fahrrad" |
location | string | optional | up to 150 characters |
category | string | optional | one of all, immobilien, apartments-rent, apartments-buy, houses-rent, houses-buy, cars, bicycles, electronics, home-garden, fashion; default "all" |
radiusKm | string | optional | one of 0, 5, 10, 20, 30, 50, 100, 150, 200; default "0" |
priceFrom | number | optional | at least 0 |
priceTo | number | optional | at least 0 |
maxResults | integer | optional | 1–20; default 10 |
Returned fields
The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 19 fields; a field the source does not publish comes back null.
19 fields per record
| Field | Type | Notes |
|---|---|---|
id | string | — |
url | string | — |
currency | string | — |
priceType | string | — |
postedAt | string | — |
sellerType | string | — |
descriptionExcerpt | string | — |
transactionType | string | — |
detailsError | string | — |
price | number | — |
rooms | number | — |
livingAreaM2 | number | — |
warmRent | number | — |
coldRent | number | — |
categoryPath | array of strings | — |
imageUrls | array of strings | — |
location | object | Locality as supplied by the source. |
detailsParsed | boolean | Whether public detail fields were parsed. |
sellerName | string | Public source value, null when absent. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/de/kleinanzeigen/listings -m POST -b '{"keyword": "fahrrad", "maxResults": 5}'
The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Kleinanzeigen Scraper | German Classifieds & Immobilien. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt