Zonaprop Argentina Real Estate & Agency Scraper

What it does

Extracts property listings, new developments and real estate agencies from Zonaprop, Argentina's largest property portal, with exact coordinates and every attribute the listing exposes. It runs one entity type per run so the table you download has a single clean shape, and it states its coverage ceiling instead of implying it scraped the whole country.

{
  "posting_id": "54321098",
  "url": "https://www.zonaprop.com.ar/propiedades/...",
  "title": "Departamento 3 ambientes en Palermo Hollywood",
  "property_type": "Departamento",
  "operation_type": "sale",
  "price_amount": 245000,
  "price_currency": "USD",
  "price_formatted": "USD 245.000",
  "expenses_amount": 95000,
  "expenses_currency": "ARS",
  "total_area_m2": 78,
  "covered_area_m2": 71,
  "rooms": 3,
  "bedrooms": 2,
  "bathrooms": 2,
  "age_years": 12,
  "condition": "Muy bueno",
  "address": "Bonpland 1500",
  "address_visibility": "exact",
  "neighborhood": "Palermo Hollywood",
  "city": "Capital Federal",
  "province": "Capital Federal",
  "latitude": -34.5885,
  "longitude": -58.4372,
  "seller_type": "agency",
  "publisher_name": "Example Propiedades",
  "phone": "+541140000000",
  "partial_phone": "11400",
  "pictures_total_count": 24,
  "status": "active",
  "from_cache": false,
  "data_age_hours": 0
}

Why this one

Use cases

• Build a priced, geolocated dataset of a neighbourhood's for-sale or rental inventory.
• Track asking prices in USD and ARS over time in a market where both currencies are quoted.
• Separate agency inventory from private-owner listings using Zonaprop's own labelling.
• Map new-build developments against existing stock in the same zone.
• Build an agency directory with listing counts, profile URLs and public business phones.
• Feed a valuation or yield model with area, rooms, age, condition and exact coordinates.

Input

Every field has a default, and the defaults are deliberately small so a first run is cheap enough to inspect before you commit to a sweep. This table mirrors the Actor's own input schema field for field.

Output and fill rates

A field being in the schema is not the same as it having a value. The percentages below were counted on real runs; the sample sizes are in Measurements. Anything not listed here is not promised.

Every key is always present. A field that exists but is empty comes back as explicit null, so a parser never has to guess.

Datasets

Different record types go to different datasets, so the main table never carries columns that are blank on most rows.

Pricing

Pay per delivered result. Charges are applied as each row is produced rather than in a lump at the end, so an aborted run bills only for what it actually gave you.

Measurements

Each figure is shown with the method that produced it. A benchmark without a method is a marketing claim wearing a number's clothes.

What it will not do

Stated plainly so you can judge fit before spending anything.

• A few hundred results per search URL is the site's ceiling — about 270 — regardless of how many listings match. Large searches must be split by location.
• robots.txt caps pagination at 5 pages per URL, which is 150 listings, and this Actor does not go beyond it.
• One entity type per run. Listings, developments and agencies each need their own run.
• A residential proxy is required, and an Argentine one will be challenged.
• Detail pages cost roughly ten times a search result, so `scrapeDetails` is off by default.
• No CAPTCHA solving and no fingerprint spoofing. If the public data becomes unreachable without them, the run reports the failure.

Privacy

• Agency phone numbers are always returned: they are public business contact details.
• Private sellers are individuals, so their phone number is withheld unless `includePrivateSellerPhone` is enabled — and enabling it is your decision, with your lawful basis.
• `partial_phone` is not a phone number. It is the five-digit fragment Zonaprop publishes to every visitor, covering the area code and three digits; the five digits that identify the line are never included.
• Removal requests: privacy@actorstack.dev

See also the data removal process.

Guides for this Actor

• Scrape ZonapropA walkthrough of extracting Argentine property data: why the proxy country matters, what the 5-page robots.txt cap means for coverage, and how to read prices quoted in two currencies.
• Zonaprop APIZonaprop has no public listing API. What it does have is a detailed robots.txt and a Cloudflare layer, which together define what a compliant integration can read.
• The coverage ceilingThe gap between what a portal says it has and what it will hand over is where most real-estate datasets quietly go wrong. Here is the ceiling, where it comes from, and the only way past it.
• The proxy requirementZonaprop sits behind Cloudflare and challenges the country its listings are in. The proxy requirement is a measurement, not a preference — and the concurrency default is part of the same finding.
• USD and ARS pricesArgentine listings are priced in dollars or pesos, and expenses almost always in pesos. Mixing them without care produces analysis that is wrong by two orders of magnitude.
• Zonaprop data fieldsA field-by-field reference for the property, development and agency rows — including an explicit note about which fields carry a measured fill rate and which do not.
• Agency vs private sellerZonaprop labels private owners separately from agencies, and that label decides whether a phone number is a business contact or an individual's personal data.
• Geolocated property dataMost property datasets give you a neighbourhood. Coordinates on the listing itself let you do the analysis that neighbourhood averages cannot.
• New developmentsNew-build projects have their own fields, their own pricing logic and their own reason to be tracked separately from resale stock.
• Agency lead listsAgency profiles come with public business phones and a listing count, which together are a better qualification signal than either alone.