Zonaprop Argentina Real Estate & Agency Scraper

Extract property listings, new developments and real estate agencies from Zonaprop, Argentina's largest property portal.

No login. No session cookies. No CAPTCHA solving.

What you get

Every field the listing exposes — not a trimmed-down subset:

Group	Fields
Price	amount, currency (USD or ARS), formatted value, expenses, price-drop percentage, and every operation when a property is listed for both sale and rent
Size & layout	total area, covered area, rooms, bedrooms, bathrooms, toilets, parking spaces, age in years, layout, orientation, brightness, condition
Location	street address, exact latitude and longitude, neighborhood, city, province, full location path, and an address-accuracy flag
Seller	seller type (agency vs. private owner, taken from Zonaprop's own labelling), name, profile URL, logo, member-since date, phone
Media	every photo with dimensions, total photo count, main image, flags for video, floor plans and virtual tour
Meta	listing ID and code, status, reserved flag, featured flag, last-modified date

Turn on detail scraping to also get the publication date, the full photo set, floor plans, videos, virtual tours and the complete description.

One entity type per run

Property listings, new developments and agencies have genuinely different fields, so mixing them would give you one table with half the columns empty. Pick what you want with What to scrape and the dataset you download has a single clean shape:

• Property listings — the default
• New developments — new-build projects, with their own feature set
• Real estate agencies — profiles, including how many listings each one holds

Run it once per type if you need more than one.

Anything that failed goes to the run's key-value store under ERRORS, and failed requests are never charged.

Permissions

This Actor runs with restricted permissions: it only touches its own default dataset and key-value store, never the rest of your account's storages. That is also why everything lands in one dataset instead of several named ones.

How it handles Zonaprop's bot protection

Zonaprop sits behind Cloudflare. This actor gets through by making ordinary requests from residential IPs and keeping the sessions that work, rather than hammering the site. Two things follow:

• A residential proxy is required, and it must not be Argentine — Argentine IPs are challenged. Mexico works best.
• Keep concurrency low. The default of 3 is deliberate.

Coverage, stated honestly

Zonaprop serves at most a few hundred results per search URL, no matter how many listings match — one search can hold 74,000 properties and still only page through about 270. This actor respects robots.txt, which caps it at 5 pages (150 results) per URL, and then automatically splits a large search into smaller ones by location to reach more of the inventory.

So: ask for a specific neighborhood and operation and you get near-complete coverage. Ask for "every apartment in Argentina" and no tool can give you that, this one included.

Privacy

Zonaprop labels private owners ("dueño directo") separately from agencies, and this actor carries that label through as seller_type.

Agency phone numbers are always included — they are public business contacts. Private sellers are individuals, so their phone number is withheld by default. You can enable it, but only do so if you have a lawful basis for processing personal data.

partial_phone is a separate field and is not the phone number: it is the 5-digit fragment that Zonaprop itself renders on the public listing page for any visitor. It covers the area code plus three digits, so the last five digits — the part that identifies the line — are never included.

To request removal of specific data, email privacy@actorstack.dev.

Input

Everything has a default, so {} returns apartments for sale in Capital Federal. Give startUrls and the filters below are ignored — the URL already says what to fetch.

{
  "propertyType": "departamentos",
  "operationType": "sale",
  "location": "palermo",
  "maxItems": 200,
  "scrapeDetails": true,
  "proxyCountry": "mx"
}

The three filters are joined into Zonaprop's own URL shape, {propertyType}-{operation}-{location}, which is why each one has to be a slug the site publishes rather than free text.

entityType — one per run

listings (property listings) · developments (new developments) · agencies (real estate agencies). They have genuinely different fields, so mixing them would hand you a file full of empty columns.

propertyType — the 10 values

Value	Property type
departamentos	Apartments
casas	Houses
ph	PH (Buenos Aires "casa chorizo" style)
locales-comerciales	Retail units
oficinas	Offices
terrenos	Land
cocheras	Parking spaces
galpones	Warehouses
quintas	Country houses
campos	Farms

They are Zonaprop's own Spanish slugs and go into the URL verbatim, so the spelling above is the whole contract — departamento in the singular is not a value.

operationType — the 3 values

sale (venta) · rent (alquiler) · temporary_rent (alquiler temporal).

Here you write the English key and the actor translates it into the Spanish slug the site expects. Temporary rent is a genuinely separate market in Argentina, not a subset of rent.

location

A location slug as Zonaprop writes it: capital-federal, palermo, cordoba, gba-norte, rosario, mar-del-plata, belgrano, nordelta. Provinces, greater-Buenos Aires zones, cities and neighbourhoods all live in one namespace, progressively narrower. Leave it empty to search the whole country.

The reliable way to get one you are unsure about: run the search on zonaprop.com.ar and read it out of the address bar. zonaprop.com.ar/departamentos-venta-palermo.html → palermo. If you have the URL already, pass it in startUrls and skip the slug entirely.

proxyCountry — the 8 values

mx Mexico · es Spain · us United States · cl Chile · br Brazil · uy Uruguay · co Colombia · pe Peru.

Argentina is deliberately not on the list. Zonaprop's bot protection challenges Argentine residential IPs; Mexico measured best and is the default. Change it only if you are seeing challenges.