Immobiliare.it Scraper - Properties, Prices & Agents avatar

Immobiliare.it Scraper - Properties, Prices & Agents

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Immobiliare.it Scraper - Properties, Prices & Agents

Immobiliare.it Scraper - Properties, Prices & Agents

From $1/1K. Extract property listings from Immobiliare.it with clean structured data including prices, descriptions, GPS coordinates, agency details, photos, and property attributes such as condition, heating, garage, floor, and features. Search by city, filters, or URL. Blazing fast, reliable.

Pricing

from $1.00 / 1,000 results

Rating

0.0

(0)

Developer

Abot API

Abot API

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

2

Monthly active users

16 days ago

Last modified

Features

Limited permissions

Share

Immobiliare.it Scraper: Property Listings, Prices and Agency Contacts for Italy

Immobiliare.it Scraper turns Italy's largest property portal into clean structured data. Get prices, full Italian descriptions, GPS coordinates, agency names and phone numbers, every photo, and a deep set of attributes such as condition, heating, garage and floor, for both sale and rental listings. Search by city with filters, or paste any Immobiliare.it search-page link and let the run walk it forward, then export to JSON, CSV or Excel, or pull the results straight into your app through the API.

Why This Scraper?

  • Two ways to search. Build searches from city names and filters (price, surface, rooms, property type, sort order), or paste one or more Immobiliare.it search-page links and let the run walk them forward.
  • Fully populated on the first pass. Every listing already carries price, the full Italian description, GPS coordinates, agency name and phone numbers, and every photo, straight from the same response that lists it, with no separate lookup per listing.
  • 35+ named fields. Condition, heating, garage, floor, features, and multi-unit ranges for new-construction listings that span several units.
  • Buy or rent, any city. Sale and rental listings across the Italian cities the site covers, filtered by property type, price, surface and room count.
  • Built for schedules. Incremental mode returns only new and changed listings on recurring runs, classifying each one NEW, UPDATED, UNCHANGED, REAPPEARED or EXPIRED, and a fully blocked run fails loudly instead of returning an empty dataset.
  • Resume without re-paying. Paste a previous run or dataset id and the actor skips every listing it already collected. This works cleanly when the search result order hasn't shifted since the interrupted run; if new listings pushed older ones down in the meantime, the resumed walk can stop once it hits a page made entirely of already-collected listings, before reaching genuinely new ones further down (see "Resume and recurring updates" below).

Use Cases

  • Real estate agencies and PropTech platforms: track competitor listings and pricing across Italian cities.
  • Market and investment research: build price-per-square-metre datasets by city, zone or property type for sale and rental segments.
  • Lead generation: collect agency names, phone numbers and listing links tied to active properties.
  • Price-tracking apps and alert bots: schedule Incremental mode to catch new listings and price changes as they happen.

Data You Get

Sample shape: values are illustrative placeholders, not from a live listing.

FieldExample
id10000001
url"https://www.immobiliare.it/annunci/10000001/"
title"Trilocale in Via Esempio, zona Zona Esempio"
contract"sale" (also "rent")
propertyType"Appartamento"
category"Residenziale"
price / priceFormatted245000 / "€ 245.000"
priceRange"200.001 - 300.000 €"
surface / rooms85 / 3
bathrooms / bedrooms2 / 2
floor"2° piano con ascensore"
elevatortrue
condition"Ottimo / Ristrutturato"
heating"Centralizzato"
garage"1 posto auto"
features["balcone", "porta blindata"]
latitude / longitude41.9000 / 12.5000
address"Via Esempio 12"
city / macrozone"Roma" / "Zona Esempio"
description"Full listing description text appears here."
photos["https://pwm.im-cdn.it/image/000000000/xxl.jpg"]
agencyName"Agenzia Demo Srl"
agencyPhones["+39 06 0000000"]
agencyUrl"https://www.immobiliare.it/agenzie-immobiliari/900001/agenzia-demo/"

Multi-unit new-construction listings also carry isProject, unitCount, and surfaceMin/surfaceMax plus roomsMin/roomsMax ranges for the cases where a single scalar surface or room count would be misleading; on those records the plain surface/rooms fields are left empty. Every record also carries a uuid, propertyTypeId, the original site wording in surfaceLabel/floorAbbreviation, region/province/microzone/nation, view tags, isNew/luxury/visibility flags, priceVisible and currency, agency extras (agencyType, agencyLogo, agencyIsPaid, hasCallNumbers), a verbatim agencyRaw/locationRaw passthrough of the source objects, and a photoCount. When Incremental mode is on, four extra fields are added to each record: changeType (NEW, UPDATED, UNCHANGED, REAPPEARED or EXPIRED), changedFields, firstSeenAt and lastSeenAt.

How to Use

  1. Pick a mode: search (build searches from city names and filters) or url (paste one or more Immobiliare.it search-page links).
  2. For search mode, add city names and any filters; for url mode, paste the search URLs (the place - city, province or whole country - buy or rent, property type from the path when it names one (apartments or villas; for a /vendita-case/ or /affitto-case/ link the Property type input still applies), price, surface, room count, auction and sort filters are read straight from the URL; a neighbourhood segment under a city narrows the run to that neighbourhood; a single-listing link returns that one listing).
  3. Set Max listings (and optionally Max pages per search) to control run size and cost, then click Start.
  4. Download the dataset as JSON, CSV or Excel, or read it through the API.

Search a single city:

{
"mode": "search",
"locations": ["Roma"],
"contract": "sale",
"maxPages": 5,
"proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "IT" }
}

Search with filters:

{
"mode": "search",
"locations": ["Milano"],
"contract": "rent",
"category": "apartments",
"minPrice": 800,
"maxPrice": 1500,
"minRooms": 2,
"sortBy": "price-asc",
"maxPages": 10
}

Multiple cities at once:

{
"mode": "search",
"locations": ["Torino", "Bologna", "Firenze"],
"contract": "sale",
"minSurface": 80,
"maxListings": 300
}

Paste search-page URLs:

{
"mode": "url",
"urls": [
"https://www.immobiliare.it/vendita-case/torino/",
"https://www.immobiliare.it/vendita-case/bologna/"
],
"maxPages": 1
}

Supported URL shapes

Paste any of these into Search URLs (url mode) or Start URL. Pagination starts at the page in the URL.

ShapeExample pathWhat you get
City search, sale or rent/vendita-case/milano/, /affitto-case/roma/Every listing of the city, newest page forward
Property type/vendita-appartamenti/milano/, /vendita-ville/roma/Apartments or villas only. For a /vendita-case/ or /affitto-case/ link the Property type input applies
Province/vendita-case/milano-provincia/The whole province
Region/vendita-case/lombardia/Not supported: the site has no region search this actor can read, so a region link is skipped with a warning and never scraped as another place. Use city or province links
Whole country/vendita-case/?idContratto=1Italy-wide search (idContratto=2 for rent)
Paginated/vendita-case/milano/?pag=2Starts at that result page
Filtered and sorted/vendita-case/milano/?prezzoMinimo=200000&criterio=prezzo&ordine=ascPrice, surface, rooms, auction and sort filters read from the URL
Neighbourhood/vendita-case/milano/affori-bovisa/Only that neighbourhood. The site may also place its own paid-promoted listings from just outside the area in a neighbourhood page, and those are returned as the site returns them. A neighbourhood that is not found under the city is skipped with a warning; it never turns into a whole-city run
Single listing/annunci/131543928/That one listing as one row, same fields as a search row. This read uses the backup connection described under Plan Requirement. A removed or expired ad logs "Listing not found" and returns no row
Agency directory/agenzie-immobiliari/, /agenzie-immobiliari/milano/Not a listing page (it lists agencies, not properties): skipped with a warning
Market statistics/mercato-immobiliare/milano/Not a listing page (price statistics for an area): skipped with a warning

Run it from your code

Python:

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("abotapi/immobiliare-it-scraper").call(run_input={"mode": "search", "locations": ["Roma"]})
for listing in client.dataset(run["defaultDatasetId"]).iterate_items():
print(listing["title"], listing["priceFormatted"])

JavaScript:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('abotapi/immobiliare-it-scraper').call({ mode: 'search', locations: ['Roma'] });
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Or connect it to Make, Zapier, n8n, Google Sheets or webhooks from the Integrations tab.

How Max pages and Max listings shape a run

Start URL (startUrl) is a single-URL shortcut: paste one search URL and the run switches to URL mode, replacing the Search URLs list. Max items (maxItems) is an alias of Max listings and takes precedence when set.

Max pages per search caps how many result pages are walked per city or URL (roughly 25 listings per page); leave it empty, or set it to 0, to walk every page the site reports. Max listings caps the total across the whole run; when a run searches several cities or URLs at once, that cap is divided evenly across them, so a single city cannot use up the entire budget while the others go unwalked.

Resume and recurring updates

  • Resume (resumeFromRunId) continues one interrupted run: paste its run or dataset id and the actor skips every listing already collected there. The walk still starts over from page 1 of each search and stops the first time it hits a page made entirely of ids already in that already-collected set; if the search's result order was stable since the interrupted run, that page is genuinely the end and Resume works cleanly, but if new listings shifted the order in the meantime, that stop can happen before the walk reaches genuinely new listings further down, so a resumed run isn't guaranteed to reach every remaining listing. Combining Resume with Incremental mode is only safe as the very first (bootstrap) run of a new tracked search; once a real Incremental-mode baseline exists for that search, the run refuses to combine them and fails immediately with a clear message.
  • Incremental mode (incrementalMode) is for scheduling this actor on the SAME search repeatedly (e.g. daily). Each listing is classified NEW, UPDATED (with changedFields), UNCHANGED (suppressed and not billed unless emitUnchanged is on), REAPPEARED or EXPIRED. EXPIRED and REAPPEARED are meant to be rare: a listing is only supposed to flip to "not present" (and, with emitExpired on, be reported as EXPIRED) after a run that scans its entire tracked search end to end, uncapped and without Resume or a mid-run checkpoint restart in the way; a maxListings/maxPages cap, an unresolved location, or a resumed run are all meant to block that. In practice, the same early-stop condition described under Resume above can also end a search early inside a single run that tracks more than one city or URL: if one search's walk collects at least one new listing and then hits a page made entirely of listings a different search in that same run already collected, it stops there and is still counted as a complete scan, which can wrongly mark still-live listings further down as EXPIRED. Keep each tracked scope (city or URL) to its own run, or verify results carefully, if you rely on emitExpired across overlapping searches. REAPPEARED only fires on a later run that reads a listing id back after an earlier run had already flipped it to "not present"; with emitExpired left off, no listing is ever flipped, so REAPPEARED cannot occur either. stateKey names or shares the stored baseline; leave it empty to let the actor derive the tracked scope automatically from your search filters. By default every field counts as a change, including the agency fields (agencyName, agencyPhones, agencyLogo, agencyIsPaid, agencyType, agencyUrl, agencyRaw), which an agency shares across all its listings; if you only care about the property itself, list them in ignoreFieldsForChanges. Pasted URLs that are now scoped more narrowly than before start a fresh baseline: a neighbourhood URL such as /vendita-case/milano/affori-bovisa/ (earlier versions read the whole city) and a URL whose property type (/vendita-appartamenti/, /vendita-ville/) differs from the Category input (earlier versions used the input). The first Incremental run on such a URL list reports every listing as NEW and never reports the listings of the old, wider scan as EXPIRED, because they were not removed, they only fell outside the new scope. URL lists without these shapes, and all search-by-location runs, keep their existing baseline. With Incremental mode off, output is exactly as before.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape: the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record, not the full JSON. Each item becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.

  1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
  2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
  3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

Input Parameters

ParameterTypeDefaultDescription
modestringsearchsearch by city and filters, or url to read pasted search-page URLs.
locationsarrayprefill: ["Roma"]City names to search. Only applies when mode = search.
contractstringsalesale (vendita) or rent (affitto). Only applies when mode = search.
categorystringallProperty type: all, apartments, or villas. Applies in search mode and, in url mode, to /vendita-case/ and /affitto-case/ links (a /vendita-appartamenti/ or /vendita-ville/ link carries its own type).
minPriceinteger(none)Minimum price in euro. Only applies when mode = search.
maxPriceinteger(none)Maximum price in euro. Only applies when mode = search.
minSurfaceinteger(none)Minimum surface in square metres. Only applies when mode = search.
maxSurfaceinteger(none)Maximum surface in square metres. Only applies when mode = search.
minRoomsinteger(none)Minimum number of rooms (locali). Only applies when mode = search.
maxRoomsinteger(none)Maximum number of rooms (locali). Only applies when mode = search.
excludeAuctionsbooleanfalseHide auction listings (aste). Only applies when mode = search.
sortBystringrelevancerelevance, price-asc, price-desc, newest, or surface-desc. Only applies when mode = search.
urlsarrayone example per supported shapeImmobiliare.it search-page URLs to read. The city, buy/rent, price, surface, room, auction and sort filters are read straight from the URL itself, not from the fields above; the property type comes from the path when it names apartments or villas, otherwise the Property type input applies; a region link is skipped with a warning; a neighbourhood segment under a city narrows the run to that neighbourhood, and a neighbourhood that cannot be matched exactly is skipped with a warning instead of scraping the whole city. A single-listing link returns that one listing. Agency directory and market-statistics pages are not listing pages and are skipped with a warning. With this field left untouched, url mode scrapes one example of each supported shape (see the URL shapes table), capped by Max listings. Pagination starts at the page in the URL. Only applies when mode = url.
startUrlstring(none)Single search URL shortcut: switches the run to url mode and replaces the Search URLs list.
maxPagesintegerprefill: 0 (unlimited)Optional bound on result pages walked per city/URL. Leave empty to walk every page.
maxListingsinteger20Hard cap on total listings across every city/URL in the run (0 = unlimited).
maxItemsinteger(none)Alias of maxListings; takes precedence when set.
resumeFromRunIdstring(none)Paste a previous run/dataset id from this actor to skip listings it already collected.
incrementalModebooleanfalseTrack this same search across scheduled runs and classify each listing NEW/UPDATED/UNCHANGED/REAPPEARED/EXPIRED.
stateKeystring(none)Only used when Incremental mode is on. Names or shares the stored baseline; leave empty to derive it automatically.
emitUnchangedbooleanfalseOnly used when Incremental mode is on. Also return (and bill) a row for every unchanged listing.
emitExpiredbooleanfalseOnly used when Incremental mode is on. Also return (and bill) a tombstone row for listings that dropped out of a fully scanned search.
ignoreFieldsForChangesarray[]Only used when Incremental mode is on. Field names (dotted for nested ones) left out of UPDATED detection and changedFields; they stay in the output. Changing the list never triggers a one-time wave of UPDATED rows.
proxyobjectprefill: Residential (IT)Connection settings. Residential proxy is recommended; the run defaults the exit country to Italy and rotates across other EU pools when needed.
mcpConnectorsarray(none)Optional: send a summary of each record to apps you authorized under Integrations.
notionParentPageUrlstring(none)Notion connector only: page under which records are created.
maxNotifyListingsinteger50Cap on items written to each connector per run. Does not affect the dataset.

Output Example

Sample shape: values are illustrative placeholders, not from a live listing.

{
"id": 10000001,
"uuid": "00000000-0000-0000-0000-000000000000",
"url": "https://www.immobiliare.it/annunci/10000001/",
"title": "Trilocale in Via Esempio, zona Zona Esempio",
"contract": "sale",
"propertyType": "Appartamento",
"category": "Residenziale",
"price": 245000,
"priceFormatted": "€ 245.000",
"priceRange": "200.001 - 300.000 €",
"currency": "EUR",
"surface": 85,
"surfaceMin": 85,
"surfaceMax": 85,
"rooms": 3,
"roomsMin": 3,
"roomsMax": 3,
"isProject": false,
"unitCount": 1,
"bathrooms": 2,
"bedrooms": 2,
"floor": "2° piano con ascensore",
"elevator": true,
"condition": "Ottimo / Ristrutturato",
"heating": "Centralizzato",
"garage": "1 posto auto",
"features": ["balcone", "porta blindata"],
"latitude": 41.9,
"longitude": 12.5,
"address": "Via Esempio 12",
"region": "Lazio",
"province": "Roma",
"city": "Roma",
"macrozone": "Zona Esempio",
"description": "Full listing description text appears here.",
"photos": ["https://pwm.im-cdn.it/image/000000000/xxl.jpg"],
"photoCount": 1,
"agencyName": "Agenzia Demo Srl",
"agencyType": "agency",
"agencyPhones": ["+39 06 0000000"],
"agencyUrl": "https://www.immobiliare.it/agenzie-immobiliari/900001/agenzia-demo/",
"agencyRaw": {},
"locationRaw": {}
}

Plan Requirement

Immobiliare.it sits behind a strict bot-protection layer. In our tests a plain datacenter or default connection was refused on first contact, so this actor does not promise results on every connection. Residential proxy is recommended and is prefilled, with the exit country set to Italy; the run rotates across other EU residential pools and retries with a different connection whenever one is refused. Apify free plans do not include residential proxies. On a free plan, or when the selected connection is unavailable, the run continues on a backup connection, logs that it is doing so, and some pages may still be unavailable; a single-listing link is read over the backup connection when the run uses the platform's proxy, and a run with your own proxy URLs makes a plain attempt that can be refused; the backup connection is slower (often 10 to 60 seconds per page) and its traffic counts toward your proxy usage. For reliable residential access, upgrade your Apify plan or supply your own proxy URLs.

If no page can be read the run fails with a message instead of returning an empty dataset: a refused proxy account, residential proxies unavailable on a free plan, or a plain connection failure each get their own message.

FAQ

How much does it cost?

You pay per listing record written to the dataset, once per row. Rows that are not returned (for example unchanged listings in Incremental mode while Emit unchanged is off) are not billed, and a failed or empty run bills no rows. Every listing record already includes price, the full description, agency contacts and photos, there is no separate toggle that changes what a record contains. The Pricing tab shows the current rates. Use Max listings and Max pages per search to cap the cost of any run.

This actor collects only publicly available real estate listing data. You are responsible for how you use it: follow Immobiliare.it's terms and the laws that apply to you, and get legal advice if you plan commercial redistribution. Property details are generally facts, but photos, descriptions and agency-provided contact details may be subject to third-party rights and data-protection rules in your jurisdiction.

Can I get only new or changed listings on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated listings, and unchanged ones are not billed unless you switch on Emit unchanged listings.

What's the difference between Resume and Incremental mode?

Resume (resumeFromRunId) continues one specific interrupted run, once, from a pasted run or dataset id. Incremental mode is for scheduling the actor on the same search repeatedly; it remembers the previous run itself, so you never paste an id. They solve different problems and, once a real Incremental-mode baseline exists, the actor refuses to run them together.

Why did my run fail instead of returning an empty dataset?

If every request to the source is refused, the run stops with a clear failure message (proxy account refused, residential proxies unavailable on a free plan, or the requests failing) so "this search has zero listings" is never confused with "nothing could be read". Run it again in a few minutes. If only part of a run's cities or pages were blocked, you still get what was found from the rest.

Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.

🔗 Want more real estate data?

Pair this actor with these related scrapers from the same team:

🏷️ Subito.it Scraper
Scrape Subito.it listings across cars, real estate, marketplace, jobs, and more. Search...
🏠 ImmobilienScout24.de Scraper
Extract property listings from immobilienscout24.de, Germany's #1 real estate platform...
🏠 Idealista Scraper
Scrape Idealista properties across Spain, Italy, and Portugal. Extract 35+ fields...
🏠 Domclick RU Property Scraper
Extract property listings from domclick.ru, one of Russia’s largest real estate portals...
🏠 DDproperty Thailand Scraper
Scrape DDproperty.com Thailand listings at scale. Extract prices, property features...
🏠 Property24 Scraper
Extract structured property listings from Property24, South Africa’s largest property...

👉 Browse all abotapi scrapers

💬 Support

  • 🐞 Found a bug or a missing field? Open a ticket on the Issues tab. We usually reply within hours.
  • 🛠️ Need another site, extra fields or a private build? Email contact@abotapi.com.
  • ⭐ Enjoying it? A quick review on the actor page helps other users find it.