REAL ESTATE · GERMANY
Immowelt Germany Property
Collect property listings from immowelt.de search results for market research and listing monitoring.
About this data
Collect property listings from immowelt.de search results for market research and listing monitoring. Search by city or postcode, rent or buy, and apartment, house or plot; alternatively supply an Immowelt search URL.
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/immowelt/listings
Fetch one public Immowelt search URL with up to 20 property listings; the default is Berlin rental apartments.
Apply local price, room and area bounds to that page.
Records include IDs, titles, EUR prices, cold/warm rents, room counts, living areas, floor and energy labels, location/postcode, availability, agency names, images and source URLs.
No expose or profile pages are fetched.
Input
Send a JSON body to POST https://api.ssh.autos/v1/de/immowelt/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
searchUrl | string | optional | up to 1000 characters; default "https://www.immowelt.de/suche/mieten/wohnung/berlin/berlin-10115/ad08de8634" |
priceFrom | number | optional | at least 0 |
priceTo | number | optional | at least 0 |
roomsFrom | number | optional | at least 0 |
roomsTo | number | optional | at least 0 |
areaFrom | number | optional | at least 0 |
areaTo | 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 26 fields; a field the source does not publish comes back null.
26 fields per record
| Field | Type | Notes |
|---|---|---|
listingId | string | — |
url | string | — |
transactionType | string | — |
propertyType | string | — |
price | number | price; null when the source shows no amount |
currency | string | currency; null when the price is on request |
priceOnRequest | boolean | priceOnRequest; true when the source marks the price as on request |
coldRent | number | — |
warmRent | number | — |
purchasePrice | number | — |
rooms | number | — |
livingArea | number | — |
plotArea | number | — |
floor | string | — |
yearBuilt | number | — |
energyClass | string | — |
city | string | — |
district | string | — |
postcode | string | — |
availableFrom | string | — |
agencyName | string | Published publisher title, including private publishers, sole traders, partnerships and brands. |
phoneNumbers | array | Published provider phone numbers in source format, or null when unavailable. |
contactCard | object | Published provider contact card, including contact names and emails when available, or null. |
images | array of strings | — |
postedAt | string | — |
updatedAt | string | — |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/de/immowelt/listings -m POST -b '{"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: Immowelt Germany Property Scraper. 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