ImovelWeb Scraper: Brazil Property Listing Alerts

Watch a property search, get only what's new. This actor runs your search against ImovelWeb.com.br — a Brazilian member of the QuintoAndar-owned Navent family alongside Zonaprop in Argentina and Inmuebles24 in Mexico — and returns one clean row per listing: price, area, rooms, location, agency and a permanent link. Turn on monitoring and it becomes a watchlist: new listings and price drops since your last run, charged per new row, free on quiet days. Schedule it hourly and send the results to Discord, Slack, Google Sheets, or n8n.

This actor is ImovelWeb's member of the Navent real-estate lane alongside zonaprop-listing-lookup (Argentina) and inmuebles24-listing-lookup (Mexico) in this catalogue — all three share one underlying platform (window.__PRELOADED_STATE__.listStore.listPostings), confirmed live on all three domains.

Who it's for

A renter, investor or relocation scout watching one city for newly-posted or repriced listings wants a live feed of what's actually on ImovelWeb right now, without refreshing the search page by hand. A market research team tracking asking prices per m², or a Sheets/n8n workflow that reacts the moment something new is posted, gets the same shape here: paste a location or a saved search link, get back a flat row per listing, and pay only for listings actually returned — a search that finds nothing costs nothing.

Why this one

• Monitoring first, not a one-off dump. Turn on "Only return listings that are new, or dropped in price" and this actor becomes a watchlist: it remembers every listing ID it has already shown you, and only bills you for what's actually new or has dropped in price since the last run.
• Reads ImovelWeb's own structured listing data. Every field comes from the window.__PRELOADED_STATE__ object ImovelWeb's own pages embed to render the search results — not text scraped from rendered HTML — so price, area, rooms and location are exact, typed values.
• Never charged for a miss, or a quiet monitoring run. A search that finds nothing, or a scheduled watchlist run where nothing changed, still gets a row explaining what happened, and costs nothing.
• Paste a city/state slug or your own saved search URL. Type a location in ImovelWeb's own slug form (e.g. "sao-paulo-sp"), or paste an ImovelWeb search-results URL you've already filtered on the site — its filters carry straight through.

What you get

One row per listing by default (turn off "Expand rows" in Advanced to get one row per search instead, with the listings nested under listings).

Field	Type	Description
query	text	The search you submitted, echoed back
found	boolean	true if ImovelWeb returned a real search-results page for this search
status	text	OK on a match; NOT_FOUND, BLOCKED, or BAD_FORMAT on a miss
message	text	Plain-English reason for a miss — only present when found is false
searchQuery	text	The search line actually run
listingCount	number	Listings returned and billed for this search
totalAvailable	number	Total listings ImovelWeb reports matching this search
truncated	boolean	true if more results existed than were returned
newCount	number	New listings this run (monitoring only)
priceDropCount	number	Price drops this run (monitoring only)
monitorStatus	text	NO_NEW_ROWS on a quiet monitoring run, SEEDED on a silent first run, otherwise empty
listingId	text	ImovelWeb's own numeric posting ID
url	text (link)	Permanent listing link
title	text	Listing title
operation	text	Aluguel (rent) or Venda (sale), as ImovelWeb labels it
price	number	Listed price
currency	text	BRL (almost all listings) or USD
expenses	number	Condominium fee, when listed
expensesCurrency	text	Currency of expenses
propertyType	text	e.g. "Apartamentos"
postingType	text	PROPERTY or DEVELOPMENT (a new-build project)
totalAreaM2 / coveredAreaM2	number	Total and covered area in m²
bedrooms / bathrooms / toilettes	number	As ImovelWeb's own feature fields report them
ageYears	number	Building age in years, when listed
parking	number	Parking spaces, when listed
neighbourhood / city / state / country	text	Walked from ImovelWeb's own location hierarchy (Brazil has a state level, unlike Argentina)
lat / lng	number	Geolocation
agencyName / agencyId	text	The listing's business publisher (agency, developer, or brokerage) — never a private individual's name
sellerType	text	business for every sampled listing on this build (see the FAQ)
sellerHash	text	Anonymous seller ID (stable hash), always present
isPremier	boolean	Featured/paid-placement listing
updatedAt	text	ImovelWeb's own modified_date (see the FAQ — this is not a posting date)
photoCount	number	Number of photos
imageUrl	text (link)	First listing image
description	text	Full listing description, with emails and phone-like strings redacted
changeType	text	new, price-drop, or seen (monitoring only)
isNew	boolean	true on this listing's first appearance (monitoring only)
previousPrice	number	The price last recorded for this listing, when it dropped (monitoring only)
priceDropPct	number	Percentage drop from the previous recorded price (monitoring only)
firstSeenAt	date	When this watchlist first saw this listing (monitoring only)
scrapedAt	date	When this row was fetched

Deselect any field in the Input tab's column picker to drop it from every row — query, found, status, message, and scrapedAt always stay.

Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see .actor/pay_per_event.json for exact prices. A miss is never charged.

Monitoring / only new results

Turn on "Only return listings that are new, or dropped in price" and a search line becomes a watchlist instead of a one-off dump:

• A listing counts as new the first time its ImovelWeb listing ID is returned by this watchlist.
• A listing counts as a price drop when its price falls by at least "Minimum price drop" (5% by default) since it was last seen, measured against the most recently seen price.
• Already-seen, unchanged listings are dropped before you're billed. A quiet run still finishes and returns one free row with monitorStatus: NO_NEW_ROWS.
• The first run has nothing to compare against and returns everything as "new" by default. Turn on "Seed silently" to instead bank everything quietly with zero rows and zero charge, and start alerting from the second run.

No confirmed newest-first sort. Same finding as the reference actor zonaprop-listing-lookup: ImovelWeb's page data lists a "Recientes" (most recent) sort option, but its URL form isn't exposed anywhere in the page's links or state. So every search runs in ImovelWeb's own default order, and this actor does not claim a sort control it can't back up. Instead, when monitoring is on, paging stops early once an entire page comes back fully already-seen. Practical effect: a genuinely new listing that doesn't rank into your maxListingsPerSearch window this run may be missed until it does. Keep searches reasonably narrow (a specific city) for the most reliable monitoring.

Schedule recipe. Save this actor as an Apify Task with deltaMode: true and a deltaName you choose, add an hourly (or daily) Schedule, and point the task's webhook at Discord, Slack, Google Sheets, or an n8n/Make webhook URL.

Price-drop window limitation. Same as above: a price drop is only seen while the listing is still inside what a run actually fetches.

How to use

1. In the Apify Console. Open the actor page and click Start — the searches field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~imovelweb-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["sao-paulo-sp"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

4. Turn on "Only return listings that are new, or dropped in price" under Monitoring once you want a watchlist instead of a one-off dump — see "Monitoring / only new results" above.

Input

{
  "searches": [
    "sao-paulo-sp"
  ]
}

One search per line: a location slug in ImovelWeb's own form, city plus state code, such as "sao-paulo-sp" or "rio-de-janeiro-rj" (combined with the Operation/Property type settings below), or a full search-results link copied from imovelweb.com.br (its own filters carry straight through). No login required. Accepted formats: sao-paulo-sp, rio-de-janeiro-rj, https://www.imovelweb.com.br/apartamentos-venda-rio-de-janeiro-rj.html.

A bare location line (e.g. "sao-paulo-sp") combines with the Operation (rent/sale) and Property type settings under Advanced to build the search URL. A pasted ImovelWeb URL is used exactly as given and ignores those two settings. The state-code suffix is part of the slug — ImovelWeb's own city slugs include it (e.g. -sp for São Paulo, -rj for Rio de Janeiro); this actor does not add it for you, since it isn't mechanically derivable from the city name alone (see the FAQ).

Sample output

query	found	status	searchQuery	listingCount	totalAvailable	truncated	newCount	priceDropCount	monitorStatus	listings	listingId	url	title	operation	price	currency	expenses	expensesCurrency	propertyType	postingType	totalAreaM2	coveredAreaM2	bedrooms	bathrooms	toilettes	ageYears	parking	neighbourhood	city	state	country	lat	lng	agencyName	agencyId	sellerType	sellerHash	isPremier	updatedAt	photoCount	imageUrl	description	isNew	changeType	previousPrice	priceDropPct	firstSeenAt	scrapedAt
sao-paulo-sp	true	OK	sao-paulo-sp	30	111234	true	30	0			3040736913	https://www.imovelweb.com.br/propriedades/apartamento-para-locacao-em-vila-andrade-com-2-3040736913.html	Apartamento para locação em Vila Andrade com 2 quartos, 48m²	Aluguel	3000	BRL	421	BRL	Apartamentos	PROPERTY	48	48	2	1		5	1	Vila Andrade	São Paulo	São Paulo	Brasil	-23.6269118	-46.7468929	REMAX LEPEX II	47790151	business	43ec8eb9ec791ae5	true	2026-09-18T11:25:49-0400	8	https://imgbr.imovelwebcdn.com/avisos/2/30/40/73/69/13/720x532/6971593343.jpg	Apartamento na Vila Andrade semimobiliado...	true	new			2026-09-18T20:40:00.000Z	2026-09-18T20:40:00.000Z

A search that finds nothing comes back as a row with "found": false and is never charged. A quiet monitoring run comes back as a row with "found": true, "monitorStatus": "NO_NEW_ROWS" and is also never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~imovelweb-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["sao-paulo-sp"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~imovelweb-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"searches":["sao-paulo-sp"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~imovelweb-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"searches":["{{search}}"]}, mapping the row's search into the searches array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "ImovelWeb Scraper: Brazil Property Alerts" — the agent will find and run this actor.

For monitoring, point the Task's webhook (Console → your Task → Webhooks) at a Discord or Slack incoming-webhook URL, a Google Sheets automation, or an n8n/Make workflow's own webhook trigger.

Tips

• Start monitoring with "Seed silently" on for any watchlist you're setting up on a schedule.
• Keep a monitored search reasonably narrow (one city) — see "No confirmed newest-first sort" above.
• Always include the state-code suffix in a bare location line (-sp, -rj, ...) — ImovelWeb's own URLs require it, and this actor doesn't guess it for you.
• A BLOCKED status means ImovelWeb returned a 403, 429, 502 or 503 — lowering "Max concurrency" or trying again shortly usually clears it.

vs. the current Store leader

The current Apify Store leader for ImovelWeb, fatihtahta, has 17 users in the last 30 days (73 lifetime) with no rating and no monitoring mode.

	What it costs	What you get	Trade-off
This actor	Pay per listing returned; nothing for a miss or a quiet monitoring run	New-listing and price-drop monitoring, works across the whole Navent family (same shape on Zonaprop and Inmuebles24)	No confirmed newest-first sort (see above); no posting date, only a "last updated" timestamp
ImovelWeb's own site	Free	Browsing only	No alerts, no export, no automation

Data & privacy

This actor reads public search results that anyone can see without logging in. It doesn't log in, solve CAPTCHAs or reveal hidden contact details. Seller identity is off by default: you get a business/private flag and an anonymous seller hash so you can group listings by seller without names — a business publisher's agency name is shown (agencies are public businesses, not private individuals), but no private individual's name is ever output. Turning on seller info makes you responsible for having a lawful reason to process it. Agent and owner phone numbers, WhatsApp numbers and emails are never collected. Not affiliated with ImovelWeb / Navent / QuintoAndar.

Is this allowed? It collects the same public listing data your browser shows, for the searches you choose. It's built for monitoring a search, not for copying the marketplace. Check that your use fits ImovelWeb's terms and your local law.

FAQ

Why do I need to add a state code like "-sp" to the location? ImovelWeb's own city-slug convention includes the state abbreviation (confirmed live: apartamentos-aluguel-sao-paulo-sp.html), and it isn't a mechanical function of the city name alone (comparing it to Argentina's or Mexico's URL conventions wouldn't help — each Navent-family site has its own slug template, confirmed independently on all three built this session). Copying the location piece from a real ImovelWeb search URL is the reliable way to get it right.

Why is a row empty, or why does found say false? Either the input line was blank (status: BAD_FORMAT), ImovelWeb returned a 403/429/502/503 (status: BLOCKED), or the search matched nothing (status: NOT_FOUND). None of these are billed.

Am I charged for a quiet monitoring run? No. When monitoring finds nothing new and no price drops, you get one row with monitorStatus: NO_NEW_ROWS and listingCount: 0 — billing only fires when listingCount is greater than zero.

Why doesn't sellerType ever say "private"? Every listing sampled while building this Navent-family trio came from a business publisher (a real-estate agency, developer or brokerage) — no private-individual posting was ever observed live.

Is updatedAt a posting date? No. ImovelWeb's payload carries a modified_date (last-updated timestamp) and nothing resembling a true creation/posting date anywhere in the listing data. This actor never fabricates a postedAt field.

Do I need to configure proxies? No, but this actor requires Apify's UNBLOCKER proxy group by default — ImovelWeb is behind a Cloudflare JS challenge that UNBLOCKER clears server-side (confirmed live), unlike a plain datacenter or residential IP.

Can an AI agent call this directly? Yes. It's registered on the Apify MCP server — an agent in Claude, Cursor, or another MCP client can find and run it by name ("ImovelWeb Scraper: Brazil Property Alerts").

Related actors

• Zonaprop Scraper — the same search and monitoring shape for Zonaprop.com.ar, Argentina's member of the same Navent family (the reference implementation this actor is a config swap of).
• Inmuebles24 Scraper — the Mexican member of the same family.