Immowelt.de Scraper

Immowelt.de Scraper at a glance

Immowelt.de Scraper is a ready-to-run Apify actor from abotapi for collecting real estate data. Its documented output includes id, url, type, property and title, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $1.20 per 1,000 results on the Apify Free plan and from $0.80 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Real Estate, Developer Tools, Automation
Region: Europe
Pricing: $1.20 per 1,000 results (Free plan), from $0.80 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 25 options

Scrape detailed property listings from Immowelt.de into clean structured data. Extract prices, GPS coordinates, rooms, living area, photos, energy class, property features, agent contact details, and more.

What Immowelt.de Scraper can do

40+ fields per listing. Price, price per m², address, GPS coordinates, rooms, living area, floor, energy class, image gallery, agent name, company, phone, website, rating and more.
GPS coordinates on nearly every listing. Latitude and longitude are added automatically from Immowelt's own map data, on by default; very large searches (beyond roughly 2000 results) may have null coordinates on later listings.
Two ways to search. Pick a German state and city from dropdowns, or paste any Immowelt search URL you already refined in your browser.
Rich filter set. Price, rooms, living area, construction year and sort order, passed straight through to Immowelt so results match what the site itself would show.
Both Buy and Rent. Apartments, houses, plots and offices.
Auto pagination. Walks forward through every result page up to the limit you set, 30 listings per page.

Choose what to collect

These inputs let you configure Immowelt.de Scraper - Properties, Prices & Agent Contacts. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string	Filter mode = pick state + city from dropdowns. URL mode = paste any immowelt.de search URL with your filters already applied (great for re-using a search you already refined in a browser). Choices: filter, url
`locations`array	Pick a German federal state, then enter the city name. Any town in the state works (we resolve it automatically). Add multiple entries to scrape several cities in one run. Filter mode only.
`listingType`string	Pick Buy (Kauf) or Rent (Miete). In Filter mode this builds the search. In URL mode it never filters: the listing type is read from each pasted URL when the URL states one, and this field is the fallback label for URLs that do not. Choices: Buy, Rent
`propertyType`string	What kind of property to search for. Filter mode only. Choices: Apartment, House, Plot, Office
`priceMin`integer	Minimum price in euros. Filter mode only. Leave empty for no minimum.
`priceMax`integer	Maximum price in euros. Filter mode only. Leave empty for no maximum.
`roomsMin`integer	Minimum number of rooms. Filter mode only.

Show 18 more inputs

More input fields
Input	What it controls
`roomsMax`integer	Maximum number of rooms. Filter mode only.
`livingSpaceMin`integer	Minimum living area in square meters. Filter mode only.
`livingSpaceMax`integer	Maximum living area in square meters. Filter mode only.
`constructionYearMin`integer	Earliest construction year. Filter mode only.
`constructionYearMax`integer	Latest construction year. Filter mode only.
`sortBy`string	How to order results. Filter mode only, in URL mode the sort is taken from your URL. Choices: Default, MostRecent, PriceAsc, PriceDesc
`urls`array	One or more full Immowelt search URLs: a /suche/... search path (also the older /suche//wohnungen/mieten form, which redirects), or a classified-search URL. Tip: refine a search in your browser, copy the URL, paste it here. If the URL contains page=N, scraping starts at page N and walks forward. Single listing (expose) and m.immowelt.de URLs are skipped with a warning. Leaving this field untouched in URL mode scrapes the three example URLs.
`maxPages`integer	How many result pages to walk per location / URL (30 listings per page). Leave empty to walk every result page.
`maxListings`integer	Hard cap across the whole run. 0 = unlimited (bounded only by Max pages).
`resumeFromRunId`string	Paste a previous run ID or dataset ID to continue a full-catalogue walk across separate runs. Listings already collected there (matched by id) are skipped, so this run only saves the new ones. Leave empty for a normal fresh run. Distinct from Incremental mode below, this continues one specific interrupted run, not recurring monitoring.
`incrementalMode`boolean	When ON, this actor remembers the previous run of the SAME search (see State key) and classifies each listing as NEW / UPDATED / UNCHANGED / REAPPEARED / EXPIRED. Every field of the listing row is compared (price, area, rooms, address, agent details, images, description and the rest) except scrapedAt, isNew and anything you list in Ignore fields when detecting changes; changedFields names what moved. UNCHANGED and EXPIRED rows are not saved to the dataset unless enabled below, this is what keeps a scheduled recurring run cheap. Default OFF (every run returns every listing, as today). Combining with Resume from a previous run above is only safe on the very first incremental run (no baseline yet), once a baseline exists, remove Resume from a previous run or set a different State key.
`stateKey`string	Manually name the incremental baseline for this search, e.g. "berlin-apartments". Leave empty to auto-derive one from mode + locations/urls + the filters + Visit each listing's detail page + Add GPS coordinates, two runs with the exact same search settings then share a baseline automatically. Set this explicitly if you want to run several DIFFERENT search configs against the SAME named baseline, or keep configs that happen to match fully separate.
`emitUnchanged`boolean	When ON, incremental mode also saves listings with no detected change (changeType="UNCHANGED") to the dataset, instead of only NEW/UPDATED/REAPPEARED. This returns, and bills for, every listing every run, defeating the point of incremental mode for most use cases. Default OFF.
`emitExpired`boolean	When ON, incremental mode also saves a row (changeType="EXPIRED") for each previously-tracked listing that no longer appears, once this run reaches the natural end of the search results (skipped on a capped, resumed, or otherwise incomplete run, those cannot tell "gone" apart from "not reached yet"). This returns, and bills for, an extra row per disappeared listing. Default OFF.
`ignoreFieldsForChanges`array	Field names that must NOT make a listing count as UPDATED, e.g. ["agentReviews", "imagesAnnotated"]. Use dots for nested fields ("imagesAnnotated.description"). The fields stay in every output row; they are only left out of the comparison and out of changedFields. scrapedAt and isNew are always ignored. Changing this list never creates a one-time wave of UPDATED rows.
`mcpConnectors`array	Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON, the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).
`notionParentPageUrl`string	URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.
`maxNotifyListings`integer	Cap on items written to each connector per run. Does not affect the dataset.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

idID

urlURL (link)

listingTypeType

propertyTypeProperty

titleTitle

pricePrice (text)

locationLocation

keyFactsKey facts

descriptionDescription

imagesImages (URLs) (array)

priceValuePrice

priceCurrencypriceCurrency

Show 39 more fields

priceDisplayPrice (display)

roomsRooms

livingSpacem²

energyClassEnergy

cityCity

districtDistrict

postcodeZIP

streetStreet

agentNameAgent

agentCompanyCompany

imageCountImages

isNewNew

has3DTour3D

changeTypeChange

changedFieldsChanged fields

firstSeenAtFirst seen

lastSeenAtLast seen

scrapedAtScraped

pricePerSqmpricePerSqm

floorfloor

plotAreaplotArea

constructionYearconstructionYear

energyValueenergyValue

latitudelatitude

longitudelongitude

addressPublishedaddressPublished

agentTypeagentType

agentPhonesagentPhones

agentWebsiteagentWebsite

agentRatingagentRating

agentReviewsagentReviews

agentAddressagentAddress

hasFloorplanhasFloorplan

hasBrokerageFeehasBrokerageFee

originorigin

creationDatecreationDate

updateDateupdateDate

legacyIdlegacyId

imagesAnnotatedimagesAnnotated

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "id": "EXAMPLE0001",
  "legacyId": "00000000-0000-0000-0000-000000000000",
  "url": "https://www.immowelt.de/expose/00000000-0000-0000-0000-000000000000",
  "listingType": "Buy",
  "origin": "strict",
  "propertyType": "APARTMENT",
  "title": "Studio zum Kauf",
  "priceValue": 545000,
  "priceCurrency": "EUR",
  "priceDisplay": "545.000 €",
  "pricePerSqm": "12.520 €/m²",
  "rooms": 1,
  "livingSpace": 43.5,
  "plotArea": null,
  "floor": "EG",
  "constructionYear": null,
  "energyClass": "C",
  "energyValue": null,
  "country": "DEU",
  "city": "München",
  "district": "Altstadt-Lehel",
  "postcode": "80538",
  "street": null,
  "latitude": 48.1344,
  "longitude": 11.5843,
  "addressPublished": false,
  "agentName": "Frau Anna Beispiel",
  "agentCompany": "Beispiel Immobilien GmbH",
  "agentType": "AGENCY",
  "agentPhones": [
    "+4989000000"
  ],
  "agentWebsite": "https://www.example-immobilien.de/",
  "agentProfileUrl": "https://www.immowelt.de/profil/0000000000000000000000000000",
  "agentRating": 4.3,
  "agentReviews": 47,
  "agentAddress": "Beispielstraße 1, 80331 München",
  "imageCount": 2,
  "images": [
    "https://mms.immowelt.de/3/c/e/b/sample1.jpg",
    "https://mms.immowelt.de/e/a/d/d/sample2.jpg"
  ],
  "hasFloorplan": true,
  "has3DTour": true,
  "hasBrokerageFee": false,
  "isExclusive": false,
  "isNew": false,
  "creationDate": "2026-04-13T10:41:40.410Z",
  "updateDate": "2026-04-13T10:41:54.893Z",
  "description": null,
  "scrapedAt": "2026-04-21T08:45:02.602Z"
}

Ways to use this data

Real estate investors: track price per m² across cities and property types to find undervalued listings.
PropTech and market research teams: build a live feed of Buy and Rent listings with coordinates for mapping and comparison tools.
Relocation and rental agencies: monitor a specific city or filter combination for new listings the moment they appear, using a schedule with Incremental mode.
Lead generation: collect agent names, companies, phone numbers and websites from active listings for outreach.
Data teams: build historical datasets of price, size, energy class and location for pricing and valuation models.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does Immowelt.de Scraper return?

The documented output for Immowelt.de Scraper includes id, url, type, property, title, price (text), location and key facts. Availability of each field depends on the source page and the selected mode.

How much does Immowelt.de Scraper cost?

It costs $1.20 per 1,000 results on the Apify Free plan and from $0.80 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

Can I get only new or changed listings on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated listings for that search, and unchanged ones are suppressed from the dataset (and not billed) unless you turn emitUnchanged on.

What's the difference between Resume and Incremental mode?

They solve different problems. Resume (resumeFromRunId) continues ONE interrupted full-catalogue crawl: paste the ID of an earlier run and this run only adds listings it has not already saved there. Incremental mode (incrementalMode) is for a search you run again and again on a schedule: it remembers its own baseline and reports only what is new, updated, or gone since the previous scheduled run. Use one or the other, not usually both; combining them is only supported to bootstrap the very first incremental run from a prior full crawl.

Which dataset views are available?

Three: Listings (overview), Details & agent, and Changes (incremental), which shows changeType and changedFields. A summary of the run is also saved under the OUTPUT key of the run's key-value store.

What does incremental mode ignore?

scrapedAt and isNew never count as a change. Add more field names (dots for nested) to ignoreFieldsForChanges to ignore other noisy fields; the baseline is then compared on the remaining fields.