Zonaprop Scraper: Argentina Property Listing Alerts avatar

Zonaprop Scraper: Argentina Property Listing Alerts

Pricing

from $1.52 / 1,000 listing returneds

Go to Apify Store
Zonaprop Scraper: Argentina Property Listing Alerts

Zonaprop Scraper: Argentina Property Listing Alerts

Zonaprop scraper for Argentina property listings: price, area, rooms, location, agency and link per listing. Monitoring mode returns only new listings and price drops since your last run. No login. Pay per listing; quiet runs are free.

Pricing

from $1.52 / 1,000 listing returneds

Rating

0.0

(0)

Developer

Adrian Voss

Adrian Voss

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Watch a property search, get only what's new. This actor runs your search against Zonaprop.com.ar — Argentina's flagship real-estate portal (part of the QuintoAndar-owned Navent family alongside Inmuebles24 in Mexico and ImovelWeb in Brazil) — 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 Zonaprop's member of the Navent real-estate lane alongside inmuebles24-listing-lookup (Mexico) and imovelweb-listing-lookup (Brazil) in this catalogue — all three share one underlying platform (window.__PRELOADED_STATE__.listStore.listPostings), confirmed live on all three domains.

Who it's for

An investor or renter watching one neighbourhood for newly-posted or repriced listings wants a live feed of what's actually on Zonaprop right now, without refreshing the search page by hand. A market research team tracking asking prices per m² for a neighbourhood, 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 Zonaprop's own structured listing data. Every field comes from the window.__PRELOADED_STATE__ object Zonaprop'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.
  • Honest about what's confirmed and what isn't. Zonaprop's own "newest first" sort option exists in the page's data but has no discoverable URL form — two candidate URL patterns were tried live and both were silently ignored. This actor does not expose a non-functional sort control; see "Monitoring / only new results" below for what that means in practice.
  • Paste a neighbourhood or your own saved search URL. Type a location (e.g. "Palermo"), or paste a Zonaprop 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).

FieldTypeDescription
querytextThe search you submitted, echoed back
foundbooleantrue if Zonaprop returned a real search-results page for this search
statustextOK on a match; NOT_FOUND, BLOCKED, or BAD_FORMAT on a miss
messagetextPlain-English reason for a miss — only present when found is false
searchQuerytextThe search line actually run
listingCountnumberListings returned and billed for this search
totalAvailablenumberTotal listings Zonaprop reports matching this search
truncatedbooleantrue if more results existed than were returned
newCountnumberNew listings this run (monitoring only)
priceDropCountnumberPrice drops this run (monitoring only)
monitorStatustextNO_NEW_ROWS on a quiet monitoring run, SEEDED on a silent first run, otherwise empty
listingIdtextZonaprop's own numeric posting ID
urltext (link)Permanent listing link
titletextListing title
operationtextAlquiler (rent) or Venta (sale), as Zonaprop labels it
pricenumberListed price
currencytextARS or USD — Zonaprop mixes both (rentals mostly in pesos, sales often in dollars)
expensesnumberMonthly condo fee ("expensas"), when listed
expensesCurrencytextCurrency of expenses
propertyTypetexte.g. "Departamentos"
postingTypetextPROPERTY or DEVELOPMENT (a new-build project)
totalAreaM2 / coveredAreaM2numberTotal and covered area in m²
roomsnumber"Ambientes" (Argentina's own combined room count)
bedrooms / bathrooms / toilettesnumberAs Zonaprop's own feature fields report them
ageYearsnumberBuilding age in years, when listed
parkingnumberParking spaces, when listed
neighbourhood / city / countrytextWalked from Zonaprop's own location hierarchy (Argentina's own taxonomy has no separate state/province level — see the FAQ)
lat / lngnumberGeolocation
agencyName / agencyIdtextThe listing's business publisher (agency, developer, or brokerage) — never a private individual's name
sellerTypetextbusiness for every sampled listing on this build (see the FAQ)
sellerHashtextAnonymous seller ID (stable hash), always present
isPremierbooleanFeatured/paid-placement listing
updatedAttextZonaprop's own modified_date (see the FAQ — this is not a posting date)
photoCountnumberNumber of photos
imageUrltext (link)First listing image
descriptiontextFull listing description, with emails and phone-like strings redacted
changeTypetextnew, price-drop, or seen (monitoring only)
isNewbooleantrue on this listing's first appearance (monitoring only)
previousPricenumberThe price last recorded for this listing, when it dropped (monitoring only)
priceDropPctnumberPercentage drop from the previous recorded price (monitoring only)
firstSeenAtdateWhen this watchlist first saw this listing (monitoring only)
scrapedAtdateWhen 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 Zonaprop 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. Zonaprop'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 — two different URL patterns were tried live against the real site and both were silently ignored (the site served its default order instead). So every search runs in Zonaprop'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 — a practical "nothing new here" signal without a guaranteed ordering. 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 neighbourhood, not a whole 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. If it falls out of your maxListingsPerSearch window between runs, this actor has no way to notice it dropped.

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~zonaprop-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"searches":["Palermo"]}'
  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.
  1. 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": [
"Palermo"
]
}

One search per line: a location slug such as "Palermo" or "ciudad-de-mexico"-style text (combined with the Operation/Property type settings below), or a full search-results link copied from zonaprop.com.ar (its own filters carry straight through). No login required. Accepted formats: Palermo, Recoleta, https://www.zonaprop.com.ar/departamentos-alquiler-belgrano.html.

A bare location line (e.g. "Palermo") combines with the Operation (rent/sale) and Property type settings under Advanced to build the search URL. A pasted Zonaprop URL is used exactly as given and ignores those two settings, since the URL already encodes its own operation and type.

Sample output

queryfoundstatussearchQuerylistingCounttotalAvailabletruncatednewCountpriceDropCountmonitorStatuslistingslistingIdurltitleoperationpricecurrencyexpensesexpensesCurrencypropertyTypepostingTypetotalAreaM2coveredAreaM2roomsbedroomsbathroomstoilettesageYearsparkingneighbourhoodcitycountrylatlngagencyNameagencyIdsellerTypesellerHashisPremierupdatedAtphotoCountimageUrldescriptionisNewchangeTypepreviousPricepriceDropPctfirstSeenAtscrapedAt
PalermotrueOKPalermo303334true30060123715https://www.zonaprop.com.ar/propiedades/clasificado/alclapin-departamento-en-palermo-60123715.htmlDepartamento en PalermoAlquiler1100000ARS220000ARSDepartamentosPROPERTY463821115PalermoCapital FederalArgentina-34.5834108-58.4236871GUIMAT PROPIEDADES17016191businessfb5b294b1640eb77true2026-09-18T11:48:30-04008https://imgar.zonapropcdn.com/avisos/1/00/60/12/37/15/720x532/2079084672.jpgExcelente departamento en alquiler...truenew2026-09-18T18:21:19.956Z2026-09-18T18:21:19.956Z

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~zonaprop-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
-X POST \
-H "Content-Type: application/json" \
-d '{"searches":["Palermo"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~zonaprop-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"searches":["Palermo"]} (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~zonaprop-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 "Zonaprop Scraper: Argentina 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 neighbourhood) — see "No confirmed newest-first sort" above for why a broad, whole-city search is a weaker monitoring signal here than on other actors in this catalogue.
  • Set the currency filter to match the listing type you're browsing: ARS for most rentals, USD for most sales — a price bound never filters out a listing priced in the other currency.
  • A BLOCKED status means Zonaprop returned a 403, 429, 502 or 503 — lowering "Max concurrency" or trying again shortly usually clears it.

vs. Zonaprop's own alerts, and vs. the current Store leader

Zonaprop has no native saved-search alert feature comparable to QuintoAndar's. A public GitHub project, zonaprop-bot, exists specifically to fill this gap by polling a saved search and posting new listings to Telegram — independent evidence of real demand for exactly this job. The current Apify Store leader for Zonaprop, memo23, has 28 users in the last 30 days (128 lifetime) at 5 stars, but no monitoring mode.

What it costsWhat you getTrade-off
This actorPay per listing returned; nothing for a miss or a quiet monitoring runNew-listing and price-drop monitoring, area/room/agency detail, works across the whole Navent family (same shape on Inmuebles24 and ImovelWeb)No confirmed newest-first sort (see above); no posting date, only a "last updated" timestamp
Zonaprop's own siteFreeBrowsing onlyNo alerts, no export, no automation
zonaprop-bot (GitHub)Free, but you host and maintain itNew-listing Telegram alertsNo price-drop tracking, no structured export, self-hosted

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 Zonaprop / 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 Zonaprop's terms and your local law.

FAQ

Why is there no state/province field? Argentina's own location hierarchy on Zonaprop has no province level between city and country — confirmed live across every sampled listing (Buenos Aires' federal-capital status means there's no separate "province" the way Mexico and Brazil have one). inmuebles24-listing-lookup and imovelweb-listing-lookup do carry a state column, since Mexico and Brazil's listings do have one.

Why is a row empty, or why does found say false? Either the input line was blank (status: BAD_FORMAT), Zonaprop 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 actor, across Zonaprop, Inmuebles24 and ImovelWeb, came from a business publisher (a real-estate agency, developer or brokerage) — no private-individual posting was ever observed live. sellerType is derived from whether Zonaprop attaches a publisher record at all, so it would say "private" the moment a listing without one is fetched, but this build never saw one to confirm the shape of.

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

Can I filter by price in the currency I care about? Yes. Set the "Currency for the price filter" to ARS or USD. A listing priced in the other currency is always returned unfiltered rather than silently dropped by a bound that doesn't apply to it.

Do I need to configure proxies? No, but this actor requires Apify's UNBLOCKER proxy group by default — Zonaprop 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 ("Zonaprop Scraper: Argentina Property Alerts").

  • Inmuebles24 Scraper — the same search and monitoring shape for Inmuebles24.com, Mexico's member of the same Navent family.
  • ImovelWeb Scraper — the Brazilian member of the same family.