# ZonaProp Properties Scraper (Argentina) (`scrapyx/zonaprop-properties-scraper`) Actor

Scrapes real estate listings from ZonaProp, Argentina's #1 property portal (Navent group). Paste a search URL and get price, rooms, surface area, orientation, age, publisher and description for every listing, up to the 5-page policy ceiling per URL (150 properties).

- **URL**: https://apify.com/scrapyx/zonaprop-properties-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.84 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ZonaProp Properties Scraper (Argentina)

Scrapes real estate listings from **[ZonaProp](https://www.zonaprop.com.ar)**
— Argentina's #1 property portal, run by Navent (the same group behind
Brazil's VivaReal/ZAP Imóveis — both already saturated with sellers in
this portfolio's research; ZonaProp itself had zero). Never covered by
this portfolio before.

Public data only. No login, no cookies, no browser.

### The one thing you need to know before using this

**Only 3 of 8 TLS profiles pass** (`safari184`/`chrome99_android`/
`edge101`) — the other 5 answer a deterministic 403 (not a flake,
repeated). And `robots.txt`, while clean of any Claude/anthropic-ai
mention, carves out a narrow allowlist: pages 1-5 of a search result are
explicitly `Allow`ed, everything past page 5 (and every sort order except
one) is `Disallow`ed. This actor never requests page 6+, regardless of
what `totalPages` upstream claims — see
[`CRAWLING_METHOD.md`](CRAWLING_METHOD.md) for the full trail.

### What you get

Three record types share one dataset, told apart by `recordType`.

#### `PROPERTY` — one row per listing

Convenience fields (price, operation, type, publisher...) are pulled to
the top level; the **full upstream object is also nested verbatim** under
`posting` — every structured feature (rooms, bathrooms, surface area,
orientation, age), publisher details, geolocation and a normalised
description, nothing lost to the projection.

#### `SEARCH_SUMMARY` — one row per input URL

Upstream's own `totalCount`/`totalPages`, pages actually fetched, and —
important — `locationApplied`/`locationLabel`: whether the location
segment in your pasted URL genuinely resolved (see **Notes on
reliability** below).

#### `ERROR` — one row per input that failed

So every entry in **ZonaProp search URLs** maps to at least one output row.

### Input

| Field | What it does |
| --- | --- |
| **ZonaProp search URLs** | full search-result URLs copied from zonaprop.com.ar (not typed filters — see below) |
| **Max properties per search URL** | pagination cap, still bounded by the 5-page policy ceiling (150 max) |
| **Max concurrent requests / Min seconds between requests** | kept moderate given the 3/8 TLS pass rate |

#### Example

```json
{
  "searchUrls": [
    "https://www.zonaprop.com.ar/departamentos-venta-palermo.html",
    "https://www.zonaprop.com.ar/departamentos-venta-caballito.html"
  ],
  "maxItems": 90
}
```

**Why paste a URL instead of typing a city/neighbourhood?** ZonaProp's
grammar is `{propertyType}-{operation}-{location}.html` with 19 property
types and a huge, unenumerated Argentina location taxonomy. Guess-building
one from a typed name risks landing exactly on the trap below. Copy the
URL the site itself generated for your filters instead — same approach
this portfolio already uses for `property24-properties-scraper` and
`kijiji-real-estate-scraper`, whose location namespaces are equally opaque.

### Notes on reliability

- **Bogus/unrecognised location → SILENT-WIDEN to the entire country.**
  Verified live: `departamentos-venta-notarealbarrio.html` answers HTTP
  200 with `total: 218183` (all of Argentina), not an error or a 404.
  This actor cannot stop you from pasting a URL with a typo, but it DOES
  detect it after the fact: `locationApplied: false` and
  `breadCrumbLabels` shortening from 5 entries (country → city →
  neighbourhood) to 3 (country-only) are both reported on the
  `SEARCH_SUMMARY` row. Check that field before trusting a run.
- **Pagination is genuinely honest within the allowed window** — page 2
  carries a different `offset`/zero id-overlap from page 1 — but this
  actor stops at page 5 **by policy**, not because the site itself would
  refuse page 6 (it likely wouldn't; `totalPages` routinely claims
  hundreds). Don't expect more than 150 rows from one URL.
- **`price: 0`** on a row means the listing is priced "on request"
  upstream (`hasPriceOnRequest`) — not a parsing gap.
- A `-pagina-N` segment pasted into the URL is stripped and rebuilt by
  this actor's own pagination loop, so pasting a mid-search-results page
  is safe and starts from page 1 regardless.

### Output envelope

Every record carries `_input`, `_source` and `_scrapedAt`. Upstream field
names pass through **verbatim**, nested under `posting` — no renaming.

See [`CRAWLING_METHOD.md`](CRAWLING_METHOD.md) for the full
reverse-engineering trail.

# Actor input Schema

## `searchUrls` (type: `array`):

Full search-result URLs copied from zonaprop.com.ar, e.g. 'https://www.zonaprop.com.ar/departamentos-venta-palermo.html'. Paste the exact URL the site itself generated for your filters (property type + operation + location) -- ZonaProp's location namespace is too large to safely guess/validate, and an unrecognised location silently falls back to nationwide results (see README). One entry = one independent search, its own SEARCH\_SUMMARY row.

## `maxItems` (type: `integer`):

Stop paginating one search URL after this many properties. Set to 0 for unlimited -- still bounded by the 5-page ceiling below (150 properties at 30/page).

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight at once, across search URLs. Kept moderate: 5 of 8 TLS profiles probed in recon answered a deterministic 403.

## `minRequestInterval` (type: `integer`):

Paces request starts (not held inside a concurrency slot) rather than raw concurrency.

## `proxyConfiguration` (type: `object`):

Residential proxy pinned to Argentina is the default -- this portfolio's standard baseline for a single-country site, even without a confirmed geo-fencing WAF finding here.

## Actor input object example

```json
{
  "searchUrls": [
    "https://www.zonaprop.com.ar/departamentos-venta-palermo.html"
  ],
  "maxItems": 90,
  "maxConcurrency": 4,
  "minRequestInterval": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "AR"
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchUrls": [
        "https://www.zonaprop.com.ar/departamentos-venta-palermo.html"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/zonaprop-properties-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "searchUrls": ["https://www.zonaprop.com.ar/departamentos-venta-palermo.html"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/zonaprop-properties-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchUrls": [
    "https://www.zonaprop.com.ar/departamentos-venta-palermo.html"
  ]
}' |
apify call scrapyx/zonaprop-properties-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/zonaprop-properties-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/MTSsdJv6EagFzJTTZ/builds/Nh0VIsXSz3CsBTJOZ/openapi.json