🏠 Idealista Scraper

Fast, request-only scraper for Idealista — Spain 🇪🇸, Italy 🇮🇹 and Portugal 🇵🇹. Pull prices, full listing details, GPS, photos and advertiser phone numbers 📞 — no browser, no captcha solving.

Point it at a search URL or a listing URL, press Start, and get clean structured data: one row per property. Perfect for real-estate datasets, market analysis, lead generation, competitor tracking and price monitoring.

---

✨ Highlights

📞 Advertiser phones included	Real contact numbers, resolved automatically — no extra toggle, no captcha
🔎 Search & 📄 detail	Scrape result pages or individual listings — or let Auto-detect decide
🌍 3 countries	idealista.com, idealista.it, idealista.pt
💰 Sale / rent / new-build	Build URLs from a location, or paste your own filtered URLs
🪓 Full-coverage mode	Price-range splitting beats Idealista's pagination cap on big cities
🔁 Monitoring	Detect new / unchanged / price_changed / removed between runs
🛡️ Anti-block built in	Safari TLS impersonation + residential proxy + smart retries
⚡ No browser	Pure HTTP requests → cheap, fast, low memory

---

🚀 Quick start

🔎 Scrape a search

{
  "mode": "SEARCH",
  "searchUrls": [
    { "url": "https://www.idealista.com/en/venta-viviendas/madrid-madrid/" }
  ],
  "maxItems": 100,
  "maxPagesPerSearch": 3
}

📄 Scrape specific listings

{
  "mode": "DETAIL",
  "detailUrls": [
    { "url": "https://www.idealista.com/en/inmueble/106387165/" }
  ]
}

🏗️ Let the actor build the URL for you

{
  "country": "ES",
  "operation": "SALE",
  "locationSlug": "madrid-madrid",
  "language": "en",
  "maxItems": 100
}

💡 Just paste URLs and go. With mode on Auto-detect (the default), detail URLs / listing IDs / a dataset trigger DETAIL mode; anything else runs SEARCH.

---

🧭 Modes

Mode	Use it for	You get
🔀 AUTO (default)	Just paste URLs and let the actor choose	DETAIL for detail URLs / IDs / dataset, otherwise SEARCH
🔎 SEARCH	Result pages, region pages, filtered searches, generated URLs	One row per listing, optionally enriched with detail fields
📄 DETAIL	Single property URLs, listing IDs, or a previous dataset	Full detail records for each listing

---

📞 How phone numbers work

Idealista hides the advertiser's real number behind a captcha-gated widget on the website. This actor skips the website entirely for phones and asks Idealista's mobile-app API — the same backend the official Android/iOS app uses — which returns the number as plain JSON.

listing  ──►  HTML page (curl_cffi + Safari TLS)   ──►  price, details, photos, GPS
   │
   └────────►  mobile app API (signed request)      ──►  📞 advertiser phone

✅ No captcha · ✅ no browser · ✅ no paid solver — phones come for free with every run.

Phone fields (populated when Idealista exposes them): phone, phoneFormatted, phoneLocal, phonePrefix, phoneRequiresLogin, secondaryPhone, secondaryPhoneFormatted.

---

⚙️ Input reference

The input form is grouped into sections — you rarely need more than the first one.

🎯 What to scrape

Field	Description
mode	🔀 AUTO (default) / SEARCH / DETAIL
searchUrls	🔎 Idealista search / result URLs (SEARCH)
detailUrls	📄 Individual property URLs (DETAIL)
startUrls	🧩 Mixed URLs, routed by their type
listingIds	🆔 Raw listing IDs (DETAIL)
datasetId	🗂️ Re-scrape a previous run's dataset

🏗️ Build search URLs from a location (optional)

Field	Description
country	🌍 ES / IT / PT
operation	🏷️ SALE / RENT / NEW_DEVELOPMENT
locationSlug, locationSlugs	📍 e.g. madrid-madrid, milano-milano, lisboa
language	🗣️ URL language segment, e.g. en

💶 Filters & limits

Field	Description
minPrice, maxPrice	💶 Price filter (replaces any in the URL)
maxItems	🔢 Output cap · 0 = unlimited
maxPagesPerSearch	📄 Pages per search / price band
maxDetailUrls	🔢 Cap on DETAIL inputs · 0 = no cap

🔬 Coverage & enrichment

Field	Description
enablePriceSplitting	🪓 Split broad searches into price bands for full coverage
maxSplitDepth	🪓 How deep to keep splitting
includeDetails	➕ Enrich each search result with its detail page
rawOutput	🧪 Add raw parsed JS config to detail records

🔁 Monitoring

Field	Description
monitoring	🔁 Label listings new / unchanged / price_changed / removed
monitoringStoreName	💾 Named key-value store for snapshots

🌐 Network & anti-block (advanced — good defaults)

Field	Description
proxy	🌐 Defaults to Apify Residential (recommended)
maxConcurrency	⚡ Parallel detail requests
maxRetries, maxProxyRetries, maxBlockRetries	🔁 Retry budgets (general / proxy / DataDome)
requestTimeoutSecs	⏱️ Per-request timeout
failOnSearchError	🚨 Abort the run if a search URL fails
impersonateProfile, acceptLanguage	🎭 TLS fingerprint & language header

---

📦 Output

One dataset item per listing. Example detail record (trimmed):

{
  "_recordType": "property",
  "source": "idealista",
  "propertyId": "106387165",
  "url": "https://www.idealista.com/en/inmueble/106387165/",
  "title": "Flat in Madrid",
  "price": "450,000 euro",
  "priceValue": 450000,
  "currency": "EUR",
  "sizeM2": 92,
  "bedrooms": 3,
  "bathrooms": 2,
  "floorNumber": 4,
  "hasLift": true,
  "hasTerrace": true,
  "address": "Madrid",
  "city": "Madrid",
  "province": "Madrid",
  "latitude": 40.4168,
  "longitude": -3.7038,
  "advertiserName": "Example Agency",
  "phone": "+34919017396",
  "phoneFormatted": "919 01 73 96",
  "phoneLocal": "919017396",
  "phonePrefix": "34",
  "phoneRequiresLogin": false,
  "photoCount": 24,
  "country": "ES"
}

ℹ️ Empty fields mean Idealista didn't expose that value for the listing or country.

🧾 Special rows

Alongside property rows, the dataset may contain:

• _recordType: "error" — a URL that failed (with sourceUrl and error)
• _recordType: "coverageReport" — per-search summary: totals, pages fetched, whether results were truncated
• _recordType: "change" — a removed listing (monitoring mode)

---

🪓 Full-coverage price splitting

Idealista stops paginating broad searches after a limited number of pages, so a huge city can silently truncate. Turn on splitting to slice the search into price bands and recover the long tail:

{
  "enablePriceSplitting": true,
  "maxSplitDepth": 2,
  "maxPagesPerSearch": 10
}

Each run emits a coverageReport row per band so you can see exactly what was covered and what (if anything) was still truncated.

---

🔁 Monitoring

Run the same search on a schedule and diff it against the previous snapshot:

{
  "mode": "SEARCH",
  "searchUrls": [
    { "url": "https://www.idealista.com/en/venta-viviendas/madrid-madrid/" }
  ],
  "monitoring": true,
  "monitoringStoreName": "idealista-madrid-sale"
}

Every listing is labelled new, unchanged, price_changed (with previousPriceValue) or removed. Use a distinct store name per saved search.

---

🎛️ Recommended settings

---

🩹 Troubleshooting

Symptom	Fix
😕 Fewer results than expected	Raise maxPagesPerSearch, enable enablePriceSplitting, or split a big city into smaller searches
🕳️ Detail fields missing in SEARCH	Enable includeDetails, or run DETAIL mode on the URLs / dataset
🛡️ Hitting blocks	Keep Apify Residential proxy on, lower maxConcurrency, raise retry budgets
📞 Phone empty	The advertiser hides it (phoneRequiresLogin: true) or Idealista didn't expose it for that listing

---

💬 Feature requests & issues

Need a new field, a different format, or a workflow this actor doesn't cover yet? Hit a listing that doesn't parse? Open an issue on the actor's page in Apify Console and include the run ID, your input, what you expected, and a short sample of the data you need. Clear reports get fixed faster. 🙌