# Argenprop Real Estate Scraper (Argentina) (`scrapyx/argenprop-properties-scraper`) Actor

Scrapes property listings from Argenprop — one of Argentina's largest real estate portals (188K+ listings in apartments-for-sale alone). Returns price, currency, address, bedrooms, expenses, photos, agency and Argenprop's own internal location/type taxonomy ids for any search you paste in.

- **URL**: https://apify.com/scrapyx/argenprop-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.56 / 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/actors/running/actors-in-store.md#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

## Argenprop Real Estate Scraper (Argentina)

Scrapes property listings from **[Argenprop](https://www.argenprop.com)** —
one of Argentina's largest real estate portals (188,801 results in
"Departamentos en venta" alone).

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

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

**You paste a search URL — you don't build one.** Filters (property type,
operation, neighbourhood, price, bedrooms) are applied through Argenprop's
own search UI and end up encoded in the URL **path**
(`/departamentos/venta/palermo`), not a query string. There's no public
directory mapping place/type names to Argenprop's internal path segments,
so this actor never guesses one — browse to any search on argenprop.com and
paste the resulting URL in. Any query string on the pasted URL is dropped:
Argenprop's `robots.txt` only permits a bare `?pagina-N` query string (see
Known limits), so a filter carried as a query param wouldn't survive
pagination anyway.

### What you get

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

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

Search cards are already rich — parsed straight from Argenprop's own inline
`data-*` attributes, no JSON blob or JSON-LD needed: `price` and
`priceNormalized` (raw integers, Argenprop's own currency-normalized
figure — no locale-format "2.400.000" string parsing involved),
`priceCurrency`, `address`, `locationLabel`, `bedrooms`, `expensesText`
(monthly HOA-style fee), a `features` list (variable per listing —
surface area, age, bathrooms, garage, whatever that card actually shows,
captured as `{icon, text}` rather than assumed fixed), photo count and
URLs, agency name and logo, and Argenprop's own internal taxonomy ids
(`propertyTypeId`, `operationTypeId`, `provinceId`, `partidoId`,
`localidadId`, `barrioId`, `subBarrioId`) — no public id→name lookup exists
for these, so they're passed through raw rather than guessed at.

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

Pages fetched, properties returned, and (best-effort) Argenprop's own total
match count from the page's `<h1>` when it renders one.

#### `ERROR` — one row per input that could not be processed

Every input maps to at least one row, so nothing disappears silently.

### Input

| Field | What it does |
| --- | --- |
| **Search URLs** | full `argenprop.com` search-result URLs, copied from the site — one crawl each |
| **Max properties per search URL** | `0` = unlimited, still capped at 200 (10 pages × 20/page — see Known limits) |
| **Max concurrent requests** | absorbs latency variance across search URLs — not the throttle |
| **Min interval between requests** | the actual speed control — 1.0s default |

#### Example

```json
{
  "searchUrls": [
    "https://www.argenprop.com/departamentos/venta",
    "https://www.argenprop.com/casas/alquiler"
  ],
  "maxItems": 200
}
```

### Notes on reliability

- **AWS WAF rate/volume gate, not a per-request block.** The first several
  dozen requests from a given exit IP go through clean (200, real content);
  past that budget, every response becomes HTTP 202 with an
  `window.gokuProps` challenge shell. Confirmed IP-based, not
  TLS-fingerprint-based. **Residential proxy IP rotation on retry is the
  real mitigation** — this is why proxy defaults to Residential/Argentina
  rather than being merely a defensive default, and why the default request
  interval is more conservative (1.0s) than most of this portfolio.
- **List-only — no detail-page pass.** The WAF gate tripped during recon
  before a detail page's shape could be verified, so this actor does not
  guess at one. The search card already carries price, address, bedrooms,
  expenses, photos and agency — enough for a browse without an extra
  request per listing.
- **Speed is controlled by request rate, not concurrency**, same design as
  the rest of this portfolio — `maxConcurrency` absorbs latency variance,
  `minRequestInterval` is the actual throttle.

### Known limits

- **10-page policy ceiling (200 listings) per search URL — from
  `robots.txt`, not a technical limit.** Argenprop's own Allow/Disallow
  rules permit only the bare query string `?pagina-1` through `?pagina-10`,
  end-anchored; anything else matching `pagina-` is disallowed. This actor
  respects that even though the WAF's own technical ceiling sits well
  higher — narrow your search (by neighbourhood, price, etc., all via the
  URL path) rather than requesting more pages of a broad one.
- **No location/type builder.** There is no authoritative public list of
  Argenprop's path segments for property type, operation or neighbourhood
  (the on-site location autocomplete posts to a separate API domain,
  `api.sosiva451.com`, not used here) — see "the one thing you need to know"
  above.

# Actor input Schema

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

Full Argenprop search-result URLs — one crawl per entry, each with its own SEARCH\_SUMMARY row. Browse to any property type / operation / neighborhood search on argenprop.com and paste the resulting URL here. Any query string on the pasted URL is dropped: Argenprop's robots.txt only permits a bare '?pagina-N' query string, so filters (location, price, bedrooms) must already be encoded in the URL PATH the way Argenprop's own site builds it — never hand-construct one from a category name.

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

Stop paginating a search URL after this many properties. Set to 0 for unlimited (still capped at 200 — see below).

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

How many requests may be in flight at once, across all search URLs. This absorbs latency variance; it is NOT the throttle — the crawl rate is set by 'Minimum interval between requests' below.

## `minRequestInterval` (type: `number`):

The actual speed control: the shortest gap between two requests to Argenprop, across all workers. Argenprop sits behind an AWS WAF rate/volume gate (confirmed during recon — not a per-request block, but a budget that runs out after enough unthrottled requests from one exit IP). Keeping this conservative and letting the Residential proxy rotate exit IPs is what keeps a run out of that gate.

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

Residential, pinned to Argentina, is the default and matters here more than usual: Argenprop's AWS WAF rate-gates by exit-IP volume (confirmed during recon — a fresh TLS session from an already-gated IP was still blocked), so IP rotation on retry is the actual mitigation, not just a defensive default.

## Actor input object example

```json
{
  "searchUrls": [
    "https://www.argenprop.com/departamentos/venta",
    "https://www.argenprop.com/casas/alquiler"
  ],
  "maxItems": 100,
  "maxConcurrency": 3,
  "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.argenprop.com/departamentos/venta",
        "https://www.argenprop.com/casas/alquiler"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/argenprop-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.argenprop.com/departamentos/venta",
        "https://www.argenprop.com/casas/alquiler",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/argenprop-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.argenprop.com/departamentos/venta",
    "https://www.argenprop.com/casas/alquiler"
  ]
}' |
apify call scrapyx/argenprop-properties-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/argenprop-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/DtOd0vUc6PSyDWmUc/builds/kE5mHIPzmaNNbDN7H/openapi.json