Idealista Scraper — Spain Real Estate, Prices, m² | from $2/1K

Scrape property listings from idealista.com (Spain's #1 real estate portal), including idealista.it (Italy) and idealista.pt (Portugal).

Returns structured property data for sale and rental listings: title, price, price per m², rooms, floor, description, agency, images, and more.

What it does

• Searches listings by location (province, city, region) and operation (sale or rent)
• Supports all property types: homes, offices, commercial space, garages, land, buildings
• Client-side price and rooms filters available
• Paginates automatically across all result pages (30 listings per page)
• Pay per result — only charged for listings actually returned

Input

Field	Description
Search URL	Paste a full idealista.com URL from your browser (recommended — filters are encoded in the URL)
Location slug	Location as in idealista URL, e.g. madrid-provincia, barcelona-provincia, sevilla-provincia
Operation	sale (venta) or rent (alquiler)
Property type	viviendas (homes), oficinas, locales, garajes, trasteros, terrenos, edificios
priceMin / priceMax	Client-side price filter (EUR)
minRooms	Client-side minimum rooms filter
maxItems	Maximum listings to return (default 100)
Proxy	Apify Residential proxy (country ES required — datacenter IPs are blocked)

Finding your location slug

Open a search on idealista.com, pick a location, and copy the slug from the URL:

https://www.idealista.com/venta-viviendas/madrid-provincia/
                                            ↑ this part is the slug

Common Spain slugs: madrid-provincia, barcelona-provincia, valencia-provincia, sevilla-provincia, malaga-provincia, alicante-provincia

Output fields

Field	Type	Description
property_id	string	Unique listing ID
title	string	Listing title (address + type)
url	string	Full listing URL
operation	string	sale or rent
property_type	string	Property type (viviendas, etc.)
price	number	Price in EUR (or EUR/month for rent)
price_unit	string	€ or €/mes
price_per_m2	number	Derived price per m²
old_price	number	Original price before reduction (if reduced)
price_dropped	boolean	True if price was reduced
price_drop_pct	integer	Reduction percentage
rooms	integer	Number of rooms/bedrooms
size_m2	number	Property size in m²
floor	string	Floor description (e.g. "2ª planta exterior con ascensor")
location	string	Human-readable location
location_slug	string	Raw location slug
domain	string	idealista.com, idealista.it, or idealista.pt
description	string	Property description excerpt
tags	array	Feature tags (e.g. "Lujo", "Obra nueva", "Villa")
features	array	Other detail items (e.g. "Garaje incluido")
agency_name	string	Agency or owner name
agency_kind	string	Agency role (e.g. "Comercializa")
agency_url	string	Agency profile URL
images	array	Full image URLs
image_count	integer	Number of images
thumbnail	string	First image URL
search_url	string	Search URL used for this run
page_number	integer	Page number this listing came from
scraped_at	string	ISO 8601 timestamp

Pricing

This actor uses Pay-Per-Event (PPE) pricing: you are charged only for listings actually returned, after a successful push. Rate: approximately $2 per 1,000 listings.

Access notes

Idealista requires an Apify Residential proxy with country ES — datacenter IPs receive a 403 block. The proxy cost is billed to your Apify run and is included in the per-listing charge calculation.

Supported sites

• Spain: idealista.com (default)
• Italy: idealista.it (pass URL with idealista.it domain)
• Portugal: idealista.pt (pass URL with idealista.pt domain)

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.