ImmobilienScout24 Property Listings Scraper

Export public ImmobilienScout24 property search listings from German regions into an Apify dataset. Collect listing IDs, prices, area, rooms, locations, coordinates and image URLs for rental or purchase market research, then download CSV, Excel or JSON.

This Actor returns search-listing data, not full property details. It reads the region and apartment/house rent/buy type from supported German regional search URLs. Price, rooms, radius and sorting filters in a URL are not applied.

Quick start

1. Open the Actor's Input tab and paste a German regional search URL, or clear Search URLs and enter a geocode.
2. Set Maximum listings to a small explicit limit and start the run.
3. Open the Dataset tab to inspect and export results.

{
  "startUrls": [{ "url": "https://www.immobilienscout24.de/Suche/de/berlin/berlin/wohnung-mieten" }],
  "maxItems": 10
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Collect Munich Apartment Rentals from ImmobilienScout24
• Export Berlin Apartment Rentals from ImmobilienScout24

What you get

One row per unique public German search listing, with its ID, source and listing links, plus available parsed and original price, area and room values. Public location fields, image links, flags and page context can accompany it. This does not fetch full descriptions, contacts or other property-detail enrichment.

Who is it for?

• Property-market analysts assembling regional rental or purchase listing samples.
• PropTech data teams retaining listing identifiers, available coordinates and price fields.
• Regional researchers comparing selected apartment and house search scopes.
• Automation developers joining their own repeated exports for downstream reports.

How you can use the data

• Review Berlin apartment rentals. Use the existing Berlin rental-search URL with a ten-listing cap. Keep listing ID, URL, raw price, parsed price and available area and rooms together, rather than assuming URL price or room filters were applied.
• Collect a known regional purchase scope. Use the existing Potsdam geocode and housebuy recipe with search URLs cleared for a geocode-only request. Supplying both URLs and geocodes processes both sets under the shared unique-listing cap.
• Build an honest regional map or sheet. Keep address, city, postal code and available coordinates alongside source links. Exact coordinates and optional card fields are not guaranteed, while image URLs remain links rather than downloaded media.
• Compare your own retained exports. Join listing IDs and keep priceRaw, area/room raw values and collection time before interpreting changes. Parsing can vary with source formatting. The Actor does not maintain history or send alerts, and a capped sample is not complete regional inventory.

Input settings

Setting	JSON key	Purpose
Search URLs	startUrls	German regional apartment/house rent/buy search URLs. Only region and property/transaction type are used.
Geocodes	geocodes	Region paths such as /de/bayern/muenchen. Clear the Search URLs prefill for geocode-only searches.
Real estate type	realEstateType	apartmentrent, apartmentbuy, houserent or housebuy for geocode searches.
Maximum listings	maxItems	Combined cap on unique saved listings across the input. Set it explicitly in API calls.
Page size	pageSize	Listings requested per page, from 1 to 50.

For house purchases by region:

{
  "geocodes": ["/de/brandenburg/potsdam"],
  "realEstateType": "housebuy",
  "maxItems": 10
}

No login, cookies or proxy configuration is required. There is no connection or sorting selector. Supplying both URLs and geocodes processes both sets of targets. Results are unique by listing ID within a run. With neither target input, the Actor searches Berlin apartment rentals. See field help for defaults and URL interpretation.

Output data

Each dataset row represents one unique listing. Optional source values can be null or empty arrays. The following is a shape-only illustration, not a captured property listing. Other fields are omitted for readability:

{
  "listingId": "<listing ID>",
  "title": null,
  "price": null,
  "priceRaw": null,
  "livingAreaSqm": null,
  "rooms": null,
  "imageUrls": [],
  "searchPageNumber": 1
}

Fields	Meaning
listingId, url, sourceUrl	Listing identity, public listing link and input provenance.
title, realEstateType, listingType	Headline and source property/listing type.
price, priceRaw	Parsed price and original displayed text.
livingAreaSqm, livingAreaRaw, rooms, roomsRaw	Parsed and original area/room values.
address, city, postalCode, latitude, longitude	Available public location information. Precise coordinates are not guaranteed.
published, energyEfficiencyClass	Source publication label and energy class when available.
isProject, isPrivate, isNewObject, liveVideoTourAvailable, listOnlyOnIs24	Optional source listing flags. isPrivate is a listing attribute, not access to private data.
attributes, tags	Search-card attributes and badges.
imageUrls, titlePictureUrl, realtorLogoUrl, reportUrl	Available image, logo and source report links.
searchPageNumber, searchTotalResults, scrapedAt	Page context, reported search size and collection timestamp.

Prices, area and room counts are parsed from the source card attributes. Retain the raw values when comparing listings. Missing or differently formatted attributes can affect numeric interpretation. Image links are returned, not downloaded files.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing charges start once after initial input validation and item for each unique listing saved. A valid run without matches can still incur the start event. No item event is requested without a saved listing.

See the live Pricing tab for current rates.

Tips for best results

• Use supported German regional URLs or known geocodes. Individual property-detail URLs and other country sites are outside scope.
• Clear example search URLs for geocode-only requests. Supplying both target types collects from both.
• Filter and sort exported data yourself. URL price, rooms, radius and sorting settings are not transferred.
• Retain raw values beside parsed numbers. Missing or differently formatted card attributes can affect interpretation.
• Check status and coverage before comparing regions. Saved rows can remain after a later failure or time stop.

Limits and caveats

Only supported German regional apartment/house rental or purchase search targets are interpreted. URL price, room, radius and sorting filters are not applied. Results follow source order without a connection or sorting selector. Austria, Switzerland and individual property-detail URLs are unsupported. No login, cookies or proxy configuration is required.

Search rows do not contain full property descriptions, agent names, phone numbers or detail-page enrichment. Optional values can be null or empty, precise coordinates are not guaranteed, and images are links rather than downloaded files. A private-listing flag is a source attribute rather than access to private data.

Broad or overlapping regions can return fewer unique listings than requested. A row limit does not establish complete regional coverage. An exhausted search without matches may succeed empty, while request or unexpected extraction failures can fail the run. Earlier saved rows remain after later failures, and the working time limit may leave partial output.

Retain raw price, area and room text when reviewing parsed values. Check source region and property type before drawing comparisons, and perform historical joins, changes and notifications in your own workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~immobilienscout24-property-listings-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.immobilienscout24.de/Suche/de/berlin/berlin/wohnung-mieten"
    }
  ],
  "maxItems": 10
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/immobilienscout24-property-listings-scraper').call({
  "startUrls": [
    {
      "url": "https://www.immobilienscout24.de/Suche/de/berlin/berlin/wohnung-mieten"
    }
  ],
  "maxItems": 10
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/immobilienscout24-property-listings-scraper').call(run_input={'startUrls': [{'url': 'https://www.immobilienscout24.de/Suche/de/berlin/berlin/wohnung-mieten'}], 'maxItems': 10})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

Wait for completion before reading the dataset identified by defaultDatasetId in the response. The Apify clients above wait for completion by default. Standard dataset exports are also available in Console.

MCP and AI agents notes

Follow Apify's instructions for authentication in your client. Ask the agent: “Collect up to 10 Berlin apartment rental listings using geocodes /de/berlin/berlin, realEstateType apartmentrent and maxItems 10. Retrieve the dataset and summarize available prices without guessing missing values.” Review current pricing before authorizing a run.

MCP and AI agents

You can ask your AI assistant to collect data with ImmobilienScout24 Property Listings Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's ImmobilienScout24 Property Listings Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/immobilienscout24-property-listings-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use ImmobilienScout24 Property Listings Scraper by Fetch Cat, or give it the identifier fetch_cat/immobilienscout24-property-listings-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s ImmobilienScout24 Property Listings Scraper to collect up to 5 listings from the Berlin apartment-rental search URL in Quick start. Show IDs, source links and raw and parsed prices without assuming extra URL filters apply.”
• “Collect up to 3 house-purchase listings using geocode /de/brandenburg/potsdam and housebuy, with search URLs cleared. Keep available area, rooms and location fields, leaving missing values unknown.”
• “Retrieve up to 5 apartment-rental search listings for geocode /de/bayern/muenchen with search URLs cleared. Keep listing IDs, original price text and collection times for my own comparison without collecting property details or promising exact coordinates.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export ImmobilienScout24 listings to CSV or Excel?

Yes. Download the dataset as CSV, Excel or JSON in Apify Console, or read its rows through the API.

Is this an official ImmobilienScout24 API?

No. This is an independent Actor for public German search listings, not an official ImmobilienScout24 service. No source-site account or private session is required.

Are my search URL filters preserved?

Only supported regional paths and apartment/house rent/buy type are interpreted. Other URL filters and sorting are not applied. Use a geocode when you already know the region path.

Why are some fields empty or fewer listings returned?

Search cards expose different values per listing, and regions can overlap. Missing optional values remain empty. maxItems is a ceiling, not a guaranteed count. Check the source region and property type first. This Actor does not fetch missing detail-page fields.

Related Actors

• Rightmove Property Listings Scraper — UK property searches.
• Redfin Property Listings Scraper — US property searches.
• Zillow Property Details Scraper — US property detail lookups.
• Zillow Property Listings Scraper — US listing searches before detail lookups.
• Google Maps Places Scraper — Place data for location research.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥