Idealista Market Intel Scraper

Export public Idealista property listings from search or individual property URLs in Spain, Portugal, and Italy. This Idealista scraper returns prices, locations, property characteristics, available media and contact fields in a dataset for market analysis. It is not an official Idealista API or a valuation service.

Quick start

1. Paste a public HTTPS search or property URL from idealista.com, idealista.pt, or idealista.it into startUrls.
2. Set a small maxItems, then run the Actor. No buyer login or cookies are required.
3. Open the default dataset to inspect or export the saved listings.

{
  "startUrls": [{ "url": "https://www.idealista.com/venta-viviendas/madrid-madrid/" }],
  "maxItems": 10,
  "fetchDetails": false
}

Use fetchDetails: true for additional available fields. Search access and field availability can change. Neither a URL nor a high limit guarantees complete coverage.

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:

• Export Madrid homes for sale data

What you get

One row per unique public property, with its ID, canonical listing link, country, transaction type and available asking-price and property fields. Successful optional details can add descriptions, media, features and publicly exposed contacts. Missing optional fields are omitted, and unknown operation or property type can remain explicitly unknown.

Who is it for?

• Property-market researchers assembling source-linked asking-price samples.
• Real-estate operations teams reviewing public listing inventories for selected searches.
• PropTech data teams comparing their own retained property exports.
• Location analysts inspecting available property characteristics without expecting valuations or complete regional coverage.

How you can use the data

• Prepare a Madrid sale-listing sheet. Use the existing Madrid homes-for-sale URL with a ten-property cap and optional details off. Keep id, url, price, currency and the input-source context together before comparing available property fields.
• Choose detail depth deliberately. Enable optional details for a small search sample when descriptions, media or exposed contact fields matter. A failed enrichment can leave the useful search row intact. Individual property URLs always fetch details even when optional search details are off.
• Review a known current property. Use its supported country-specific property URL with a one-property cap. Start from a public URL you can open rather than assuming an old identifier still resolves, and leave unavailable dates, contacts and coordinates unknown.
• Compare your own snapshots by property ID. Retain source collection times and original listing links before joining later datasets. Apparent missing rows do not establish removal or a price change, and the Actor does not keep a historical-price database, calculate changes, estimate yields or value properties.

Input settings

Setting	API key	Behavior
Idealista search or property URLs	startUrls	Required nonempty list of public HTTPS URLs for Spain, Portugal or Italy.
Maximum listings	maxItems	Global saved-listing cap across all URLs, from 1 to 10,000. Default 10.
Fetch full property details	fetchDetails	Default true. Enriches search results when detail retrieval succeeds. Individual property URLs always request details.

Overlapping inputs are deduplicated by property ID within a run. A failed optional detail lookup preserves the available search row. The Actor has no customer proxy or connection selector.

For a single-property lookup, provide its current /inmueble/, /imovel/, or /immobile/ URL in startUrls and set maxItems to 1. Use a current URL you can open publicly rather than relying on an old listing ID.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Each dataset row represents a unique property. The following is a synthetic shape-only example, not a live listing or a market observation:

{
  "id": "EXAMPLE_ID",
  "url": "https://www.idealista.com/inmueble/EXAMPLE_ID/",
  "country": "ES",
  "operation": "sale",
  "propertyType": "flat",
  "title": "Example property",
  "price": 100000,
  "currency": "EUR",
  "source": {
    "platform": "idealista",
    "inputUrl": "https://www.idealista.com/venta-viviendas/madrid-madrid/",
    "mode": "search",
    "fetchedAt": "2026-10-25T00:00:00.000Z"
  }
}

Group	Dataset fields
Identity	id, url, country, operation, propertyType, title
Pricing and layout	price, currency, pricePerSquareMeter, size, rooms, bathrooms, floor, condition
Location	address, locationName, municipality, province, latitude, longitude
Features	hasLift, hasParking, hasTerrace, hasSwimmingPool
Content and media	description, images, videoUrl, virtualTourUrl, energyConsumption, energyEmissions
Contact and timing	contactName, agencyName, phone, publishedAt, updatedAt
Provenance	source with platform, inputUrl, fetchedAt and search/detail mode

Optional fields are omitted when unavailable. operation and propertyType can be unknown. Images contain url and an optional tag. Contact details, coordinates, dates and media are not guaranteed. No private seller data, inferred yields or market estimates are added.

Export the default dataset as JSON, CSV, Excel, XML or RSS. Nested fields are easiest to inspect in JSON.

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 target and limit validation, then item for each successfully saved unique property. No separate paid error or status rows are created. A run can incur its start charge even if extraction later fails.

See the live Pricing tab for current rates and plan-specific discounts.

Tips for best results

• Start with one supported public URL and a small global cap. The maximum is shared across all URLs rather than promised per target.
• Use optional search details only when their fields matter. Direct property URLs still request details.
• Keep nested source context with the property ID. Input URL, collection time and search/detail mode help explain your own comparisons.
• Treat missing optional fields as unknown. Contacts, coordinates, dates and media are not guaranteed.
• Inspect status as well as the dataset after incomplete work. A useful search row can survive a failed optional detail lookup.

Limits and caveats

Only public HTTPS search or property URLs on the supported Spanish, Portuguese and Italian Idealista sites are accepted. No buyer login or cookies are required. Private seller information and account data are outside scope, and there is no customer proxy or connection selector. This is not an official Idealista API or a valuation service.

Source access and field availability can change by property and country. The Actor does not guarantee every listing in a broad market, a particular result order or complete detail fields. Overlapping targets are deduplicated within the run. The row cap is global and work may finish with fewer records than requested.

Optional detail failures preserve available search rows. The current implementation fails if no valid property records are saved. An empty dataset or access failure alone does not establish that properties were deleted, made private or otherwise removed.

No market estimates, inferred yields or hidden contacts are added. Optional values are omitted, operation and property type can be unknown, and media is represented by available links. Price-history comparisons, change detection and downstream reporting require 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~idealista-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "startUrls": [
    {
      "url": "https://www.idealista.com/venta-viviendas/madrid-madrid/"
    }
  ],
  "maxItems": 10,
  "fetchDetails": false
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/idealista-scraper').call({
  "startUrls": [
    {
      "url": "https://www.idealista.com/venta-viviendas/madrid-madrid/"
    }
  ],
  "maxItems": 10,
  "fetchDetails": false
});
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/idealista-scraper').call(run_input={'startUrls': [{'url': 'https://www.idealista.com/venta-viviendas/madrid-madrid/'}], 'maxItems': 10, 'fetchDetails': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API and AI-agent use notes

cURL starts a run asynchronously. After completion, use its defaultDatasetId to retrieve the dataset:

MCP and AI agents

You can ask your AI assistant to collect data with Idealista Market Intel 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 Idealista Market Intel 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/idealista-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 Idealista Market Intel Scraper by Fetch Cat, or give it the identifier fetch_cat/idealista-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 Idealista scraper to collect up to 5 listings from https://www.idealista.com/venta-viviendas/madrid-madrid/ with optional details off. Show property IDs, source links and available asking prices without estimating values.”
• “Collect up to 3 listings from the Madrid homes-for-sale URL in Quick start with optional details enabled. Keep available size, room and media fields, and flag missing or failed detail enrichment rather than assuming completeness.”
• “Retrieve up to 5 listings from the Madrid sale-search URL in Quick start with details off. Keep property IDs and nested source input URLs and collection times for my own later comparison, without claiming a price-history or removed-listing report.”

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

Is this an Idealista API alternative?

It provides structured listing exports through Apify, not official Idealista API access. Public-source access can change and may require maintenance.

How can I export Idealista data to CSV or Excel?

Run a bounded lookup, then select CSV or Excel from the default dataset's export options. JSON preserves nested images and source metadata.

Does it require login or return private information?

No buyer login is required. It accepts public URLs and returns only available listing information, not account data or hidden seller information.

Can I monitor prices over time?

Compare separately saved snapshots by id in your own workflow. There is no built-in historical-price or removed-listing detector.

Why are fields missing or no records saved?

Details may be unavailable even when a search row exists. No saved records currently causes a failed run. Inspect the run message and check that the target URL is current. Access failure alone does not prove a property was removed.

Related Actors

• Leboncoin Listings Scraper — adjacent French classifieds inventory.
• Marktplaats Listings Scraper — Dutch classifieds data.
• Apple Maps Places Scraper — nearby place and business research.
• Google Maps Photos Scraper — available place photos for location research.
• Google Images Scraper — separate image discovery by query.

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. ♥