Idealista Scraper

Scrape Idealista public sale and rental property listings, prices, and sizes from public pages and export Idealista data to CSV, JSON, or Excel. This Idealista API alternative turns repeatable inputs into structured properties for European property listing research.

Each dataset row represents a public propertie or a documented alternate record type. The output includes source identifiers and links where available, so you can verify a row, compare later runs, and distinguish missing source data from an omitted column.

What data can you extract from Idealista?

The dataset schema defines every field below. Examples come from one successful published run; null means that field was not exposed for that particular record. Availability may differ by input mode, page, and record type.

Field	Description	Example
propertyCode	Stable listing identifier.	596679
url	Direct listing URL.	https://www.idealista.fr/immeuble/596679/
title	Listing headline.	Appartement dans le quartier Ternes-Maillot, Paris
price	Asking price in euros.	970
currency	Price currency code.	EUR
operation	Sale or rent.	sale
propertyType	Listing property type when supplied by page data.	null
size	Advertised area in square meters.	100
rooms	Number of bedrooms or rooms shown in the result.	2
bathrooms	Number of bathrooms when shown.	null
floor	Floor label as displayed.	RDC avec ascenseur
address	Public address or area label.	null
description	Public listing description.	Dans le quartier de l'avenue de la Grande Armée, à proximité immédiate du mét…
thumbnail	Main listing image URL.	https://img4.idealista.fr/blur/480_360_mq/0/id.pro.fr.image.master/1f/cb/3e/6…
agency	Public agency label when displayed.	null
country	Country code.	fr
priceByArea	Asking price divided by advertised area.	10
sourceSearchUrl	Search result page that supplied the listing.	https://www.idealista.fr/achat-logement/paris-paris-75/
imageUrls	Additional image URLs from a detail page, when available.	null

Use the identifier and URL fields as your join keys before comparing snapshots. Fields that describe a page, search, category, author, or tournament establish where the record came from; keep them when you export a subset. Numeric values and boolean flags reflect the public page at collection time, not a permanent claim about the underlying item.

How to scrape Idealista

1. Open the actor input form and choose a narrow public source: a search phrase, page URL, item URL, or ID supported by the input fields below.
2. Set the relevant per-source page or result limit and the total item limit. Start with a small sample to check which optional fields the public source exposes.
3. Run the actor. Its dataset contains one structured row per saved result; inspect the first rows and their source links for the chosen input.
4. Download the dataset as JSON, CSV, or Excel. Preserve identifiers when combining runs so repeated results can be deduplicated.

For this actor, generated routes support homes; exact searchUrls handle custom filters and other property types. For France, only the Paris generated route was verified. The public search API requires credentials and some search pages present a challenge.

Input

Use only the parameters relevant to your collection mode. An omitted optional filter uses the schema default shown here; an empty array, zero, and an omitted value can have different meanings, so keep intentional settings in your saved input.

| Parameter | Type | Default | Description | | --- | --- | --- | | operation | string | sale | Search properties for sale or rent. | | propertyType | string | homes | Homes are supported for generated search routes. For other property types, supply exact search URLs. | | country | string | fr | Country for generated routes and listing links. | | location | string | Paris | City name for a generated homes search route. In France, only Paris has a verified generated route; use an exact URL elsewhere. | | locations | array | [] | Optional city names or search URLs to search in order. Overrides location. | | searchUrls | array | [] | Exact public search result URLs. Overrides location and locations; use for detailed site filters or non-home property types. | | propertyCodes | array | [] | Optional listing codes to fetch directly instead of search pages. | | maxItems | integer | 50 | Maximum number of unique listings to save. Zero means no item limit. | | maxPages | integer | 50 | Maximum result pages to visit for each search URL or location. | | minPrice | integer | 0 | Keep only listings at or above this price in euros. Applied after reading the page. | | maxPrice | integer | 0 | Keep only listings at or below this price in euros. Zero means any price. Applied after reading the page. | | minSize | integer | 0 | Keep only listings at or above this size in square meters. Applied after reading the page. | | maxSize | integer | 0 | Keep only listings at or below this size in square meters. Zero means any size. Applied after reading the page. | | bedrooms | array | [] | Keep only listings with one of these exact bedroom counts. Empty means any. | | fetchDetails | boolean | false | Visit each listing page to add a fuller description and image URLs when available. This adds one request per listing. | | proxyConfiguration | object | {"useApifyProxy":true} | Proxy configuration for site requests. |

Example input based on the published golden run (long URL lists are shortened):

{
  "operation": "sale",
  "propertyType": "homes",
  "country": "fr",
  "searchUrls": [
    "https://www.idealista.fr/achat-logement/paris-paris-75/"
  ],
  "maxItems": 30,
  "maxPages": 1,
  "fetchDetails": false
}

The example is a starting shape, not a guarantee of a particular result count. Source inventory and page accessibility change. When you need repeatable comparisons, save the exact input JSON with the run date and inspect the returned source or record-type field.

Output example

The following is one real item from a successful published dataset. Long text and media arrays are shortened for readability; the actual dataset keeps the original values and all schema fields.

{
  "propertyCode": "596679",
  "url": "https://www.idealista.fr/immeuble/596679/",
  "title": "Appartement dans le quartier Ternes-Maillot, Paris",
  "price": 970,
  "currency": "EUR",
  "operation": "sale",
  "size": 100,
  "rooms": 2,
  "floor": "RDC avec ascenseur",
  "description": "Dans le quartier de l'avenue de la Grande Armée, à proximité immédiate du métro Argentine, dans le 17ème arrondissement de Paris, cet appartement 3 pièces de 95,91 m² avec balcon occupe le rez-de-j…",
  "thumbnail": "https://img4.idealista.fr/blur/480_360_mq/0/id.pro.fr.image.master/1f/cb/3e/6327975.webp",
  "country": "fr",
  "priceByArea": 10,
  "sourceSearchUrl": "https://www.idealista.fr/achat-logement/paris-paris-75/"
}

This row illustrates the observed output structure, including its identifiers and public links. Empty values elsewhere in the dataset should be interpreted field by field; a field shown in this example is not promised for every propertie.

Use cases

• Property analysts can compare asking prices per square meter within a chosen search area.
• Agents can monitor new public listings using propertyCode as a stable key.
• Relocation teams can shortlist homes by size, rooms, and advertised area.
• Researchers can compare public sale and rent listings by country and source URL.

The strongest analyses keep source context. A field such as price, rating, engagement, or rank has meaning only with its associated item, query, date, and public URL. Keep the raw export and create a separate cleaned view for charts or alerts.

How much does it cost to scrape Idealista?

The price is $1.00 per 1,000 saved results. Platform usage is included. The charge scales with output rows, so a restrictive filter or inaccessible page can produce fewer billable results than the requested maximum.

• 100 properties: $0.10. This is useful for checking a small cohort and confirming which optional fields are present.
• 1,000 properties: $1.00. This is the reference price for a larger export.
• 5,000 properties: $5.00. Reaching this size may require multiple focused sources or scheduled runs, depending on public inventory and source caps.

Compute any other estimate as saved result count × $1.00 / 1,000. A maximum input is a ceiling, not a purchase of that many rows. For planning, use the actual saved-item count from an initial representative run.

Tips for best results

Use an exact public search URL for a chosen neighborhood and site filters. Keep country and operation aligned with that URL. Price, size, and bedrooms are post-collection filters, so request enough pages to leave sufficient matching rows.

Collect a small baseline first, record the exact input and date, and inspect both a typical row and a sparse row. Expand by adding focused sources instead of assuming one broad input can reveal the full public inventory. When comparing two runs, match stable IDs or canonical URLs and use the same filters so changes reflect the source rather than a changed query.

Export the full JSON when nested arrays or objects matter. CSV and Excel are convenient for sorting and joins, but nested structures may need flattening before spreadsheet analysis. Keep numeric fields numeric and preserve source URLs as text; do not infer a zero from a null.

Limits

Some markets or exact URLs may be challenged. Price, size, floor, agency, and images depend on page data; detail enrichment adds one request per listing and may still leave optional fields empty.

Public pages can change, disappear, or expose different fields for different records. The schema is a list of possible output columns, not a promise that each column is filled in each row. The maxItems-style input limits cap saved results; they do not bypass source pagination, public visibility, or a site-specific result ceiling.

Treat a saved result as a snapshot. If a later run returns fewer rows, first compare the input, source access, and public inventory before concluding that the underlying market changed. If you need an audit trail, retain the source URL, stable identifier, and run timestamp with the export.

Use with AI agents (MCP)

An agent can supply the documented input JSON, run this actor, and work from its dataset. Ask it to keep source links and identify null values explicitly when summarizing results. Example prompts:

Run Idealista Scraper for the sample input above. Return the first 20 properties with their source URLs and the fields needed for European property listing research. Mark unavailable fields as null.

Schedule a repeat Idealista collection with the same filters. Compare records by stable ID or canonical URL and report only new, removed, or changed public values.

FAQ

Is it legal to scrape Idealista?

This actor collects public data. Check the site’s terms, applicable law, and the rights of people whose data appears in your export. Follow GDPR and other privacy rules where relevant; do not use personal data for misuse, intrusive profiling, or unauthorized contact.

Do I need to configure proxies?

The input includes proxyConfiguration and defaults to Apify Proxy. Usually the default is enough to start. Availability can vary by page and region; changing network settings cannot make private or login-only information public.

How fast will a run finish?

Duration depends on the number of inputs, pages, detail requests, and source responses. A small sample is the best way to measure your workload. Increase the limits gradually, then use the observed run duration for scheduling and monitoring.

Can I schedule and monitor recurring runs?

Yes. Save the input and schedule recurring runs in Apify. Monitor run status, item count, and any missing-field changes; store the run date alongside exports when comparing snapshots.

Can I export to Google Sheets or Excel?

Yes. Download CSV or Excel from the dataset, or pass JSON to a spreadsheet integration. For nested fields, flatten the specific child values you need rather than losing the original JSON.

What if a field is empty?

An empty or null field means it was not available from that public source record in that run. Check the source URL, input mode, and record type. Do not replace missing prices, counts, dates, or flags with zero unless your own analysis has a documented rule for doing so.

Can I search any property type by city name?

Generated routes support homes. For other property types or detailed filters, supply an exact public Idealista search URL.

Integrations

Use the Apify API to start runs and retrieve the dataset, webhooks to react when a run finishes, or Zapier, Make, and n8n to route records into other systems. Google Sheets supports lightweight review, while scheduled runs provide repeat snapshots. Keep the raw JSON when downstream workflows need nested fields or exact null values.

Support

Open an issue on the Issues tab; we reply within 24h and add fields on request.