# Zonaprop Scraper: Argentina Property Listing Alerts (`accountable_eel/zonaprop-listing-lookup`) Actor

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.

- **URL**: https://apify.com/accountable\_eel/zonaprop-listing-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Real estate, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.52 / 1,000 listing returneds

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Zonaprop Scraper: Argentina Property Listing Alerts

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`).

| Field | Type | Description |
|---|---|---|
| `query` | text | The search you submitted, echoed back |
| `found` | boolean | `true` if Zonaprop returned a real search-results page for this search |
| `status` | text | `OK` on a match; `NOT_FOUND`, `BLOCKED`, or `BAD_FORMAT` on a miss |
| `message` | text | Plain-English reason for a miss — only present when `found` is `false` |
| `searchQuery` | text | The search line actually run |
| `listingCount` | number | Listings returned and billed for this search |
| `totalAvailable` | number | Total listings Zonaprop reports matching this search |
| `truncated` | boolean | `true` if more results existed than were returned |
| `newCount` | number | New listings this run (monitoring only) |
| `priceDropCount` | number | Price drops this run (monitoring only) |
| `monitorStatus` | text | `NO_NEW_ROWS` on a quiet monitoring run, `SEEDED` on a silent first run, otherwise empty |
| `listingId` | text | Zonaprop's own numeric posting ID |
| `url` | text (link) | Permanent listing link |
| `title` | text | Listing title |
| `operation` | text | `Alquiler` (rent) or `Venta` (sale), as Zonaprop labels it |
| `price` | number | Listed price |
| `currency` | text | `ARS` or `USD` — Zonaprop mixes both (rentals mostly in pesos, sales often in dollars) |
| `expenses` | number | Monthly condo fee ("expensas"), when listed |
| `expensesCurrency` | text | Currency of `expenses` |
| `propertyType` | text | e.g. "Departamentos" |
| `postingType` | text | `PROPERTY` or `DEVELOPMENT` (a new-build project) |
| `totalAreaM2` / `coveredAreaM2` | number | Total and covered area in m² |
| `rooms` | number | "Ambientes" (Argentina's own combined room count) |
| `bedrooms` / `bathrooms` / `toilettes` | number | As Zonaprop's own feature fields report them |
| `ageYears` | number | Building age in years, when listed |
| `parking` | number | Parking spaces, when listed |
| `neighbourhood` / `city` / `country` | text | Walked from Zonaprop's own location hierarchy (Argentina's own taxonomy has no separate state/province level — see the FAQ) |
| `lat` / `lng` | number | Geolocation |
| `agencyName` / `agencyId` | text | The listing's business publisher (agency, developer, or brokerage) — never a private individual's name |
| `sellerType` | text | `business` for every sampled listing on this build (see the FAQ) |
| `sellerHash` | text | Anonymous seller ID (stable hash), always present |
| `isPremier` | boolean | Featured/paid-placement listing |
| `updatedAt` | text | Zonaprop's own `modified_date` (see the FAQ — this is not a posting date) |
| `photoCount` | number | Number of photos |
| `imageUrl` | text (link) | First listing image |
| `description` | text | Full listing description, with emails and phone-like strings redacted |
| `changeType` | text | `new`, `price-drop`, or `seen` (monitoring only) |
| `isNew` | boolean | `true` on this listing's first appearance (monitoring only) |
| `previousPrice` | number | The price last recorded for this listing, when it dropped (monitoring only) |
| `priceDropPct` | number | Percentage drop from the previous recorded price (monitoring only) |
| `firstSeenAt` | date | When this watchlist first saw this listing (monitoring only) |
| `scrapedAt` | date | When 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:
   ```bash
   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.

4) 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

```json
{
  "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

| query | found | status | searchQuery | listingCount | totalAvailable | truncated | newCount | priceDropCount | monitorStatus | listings | listingId | url | title | operation | price | currency | expenses | expensesCurrency | propertyType | postingType | totalAreaM2 | coveredAreaM2 | rooms | bedrooms | bathrooms | toilettes | ageYears | parking | neighbourhood | city | country | lat | lng | agencyName | agencyId | sellerType | sellerHash | isPremier | updatedAt | photoCount | imageUrl | description | isNew | changeType | previousPrice | priceDropPct | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Palermo | true | OK | Palermo | 30 | 3334 | true | 30 | 0 | | | 60123715 | https://www.zonaprop.com.ar/propiedades/clasificado/alclapin-departamento-en-palermo-60123715.html | Departamento en Palermo | Alquiler | 1100000 | ARS | 220000 | ARS | Departamentos | PROPERTY | 46 | 38 | 2 | 1 | 1 | | 15 | | Palermo | Capital Federal | Argentina | -34.5834108 | -58.4236871 | GUIMAT PROPIEDADES | 17016191 | business | fb5b294b1640eb77 | true | 2026-09-18T11:48:30-0400 | 8 | https://imgar.zonapropcdn.com/avisos/1/00/60/12/37/15/720x532/2079084672.jpg | Excelente departamento en alquiler... | true | new | | | 2026-09-18T18:21:19.956Z | 2026-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.

```bash
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 costs | What you get | Trade-off |
|---|---|---|---|
| **This actor** | Pay per listing returned; nothing for a miss or a quiet monitoring run | New-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 site | Free | Browsing only | No alerts, no export, no automation |
| `zonaprop-bot` (GitHub) | Free, but you host and maintain it | New-listing Telegram alerts | No 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").

### Related actors

- [Inmuebles24 Scraper](https://apify.com/accountable_eel/inmuebles24-listing-lookup) — the same
  search and monitoring shape for Inmuebles24.com, Mexico's member of the same Navent family.
- [ImovelWeb Scraper](https://apify.com/accountable_eel/imovelweb-listing-lookup) — the Brazilian
  member of the same family.

# Actor input Schema

## `searches` (type: `array`):

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. You're only charged for the ones we actually find — a miss costs nothing.

## `operation` (type: `string`):

Used to build the search URL for a bare location line (e.g. "Palermo"). Ignored for a pasted zonaprop.com.ar link, which already encodes its own operation.

## `propertyType` (type: `string`):

Only "apartment" was directly verified live for this build; the others use Zonaprop's own standard Spanish path words and are not independently verified — see the README FAQ. Ignored for a pasted link.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. One keyword per line, case-insensitive, matched against title, neighbourhood, city and property type.

## `excludeKeywords` (type: `array`):

Optional. One keyword per line.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `maxListingsPerSearch` (type: `integer`):

Zonaprop shows 30 listings per page. This actor pages up to 600 (20 pages) per search. You pay per listing returned, so this is also your budget control.

## `minPrice` (type: `integer`):

Optional. Drop listings priced below this, in the currency below. A listing priced in a different currency (Zonaprop mixes ARS rentals and USD sales) is never filtered by this bound.

## `maxPrice` (type: `integer`):

Optional. Drop listings priced above this, in the currency below.

## `priceCurrency` (type: `string`):

Zonaprop lists most rentals in ARS and most sales in USD. The min/max price filter only applies to listings in this currency; listings in the other currency are always returned unfiltered.

## `deltaMode` (type: `boolean`):

Turns a search into a watchlist. A listing is new when its Zonaprop listing ID was not returned by a previous run of the same watchlist, and a price drop when its price fell by at least the percentage below since it was last seen. Unchanged listings are removed before you are billed, so a quiet run only costs the start fee. Schedule it and send the results to Discord, Slack, Google Sheets or n8n.

## `deltaName` (type: `string`):

Leave empty and one is derived from this run's operation and property type. Type your own name to keep one memory across a settings change.

## `alertOnNew` (type: `boolean`):

With monitoring on, return listings this watchlist has never seen before.

## `alertOnPriceDrop` (type: `boolean`):

With monitoring on, return listings already seen whose price has dropped since the last sighting.

## `minPriceDropPct` (type: `integer`):

A listing must be at least this much cheaper than when it was last seen to count as a price drop.

## `skipFirstRun` (type: `boolean`):

The first run of a watchlist has nothing to compare with. Turn this on to remember everything it finds without returning or billing it, so a webhook does not get flooded on day one. Alerts start from the second run.

## `includeSellerInfo` (type: `boolean`):

Off by default. Every row already carries an anonymous seller hash and, for business publishers, an agency name. Turning this on adds Zonaprop's own numeric publisher ID (sellerId); you then need a lawful reason to process it. Phone numbers, WhatsApp numbers and emails are never returned, on or off.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each listing found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces.

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

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "searches": [
    "Palermo"
  ],
  "operation": "rent",
  "propertyType": "apartment",
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "maxListingsPerSearch": 60,
  "priceCurrency": "ARS",
  "deltaMode": false,
  "deltaName": "",
  "alertOnNew": true,
  "alertOnPriceDrop": true,
  "minPriceDropPct": 5,
  "skipFirstRun": false,
  "includeSellerInfo": false,
  "columns": [
    "searchQuery",
    "listingCount",
    "totalAvailable",
    "truncated",
    "newCount",
    "priceDropCount",
    "monitorStatus",
    "listings",
    "listingId",
    "url",
    "title",
    "operation",
    "price",
    "currency",
    "expenses",
    "expensesCurrency",
    "propertyType",
    "postingType",
    "totalAreaM2",
    "coveredAreaM2",
    "rooms",
    "bedrooms",
    "bathrooms",
    "toilettes",
    "ageYears",
    "parking",
    "neighbourhood",
    "city",
    "country",
    "lat",
    "lng",
    "agencyName",
    "agencyId",
    "sellerType",
    "sellerHash",
    "isPremier",
    "updatedAt",
    "photoCount",
    "imageUrl",
    "description",
    "isNew",
    "changeType",
    "previousPrice",
    "priceDropPct",
    "firstSeenAt"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "UNBLOCKER"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "searches": [
        "Palermo"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/zonaprop-listing-lookup").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 = {
    "searches": ["Palermo"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/zonaprop-listing-lookup").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 '{
  "searches": [
    "Palermo"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/zonaprop-listing-lookup --silent --output-dataset

```

## MCP server setup

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

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/yClrZgfIs5cdIVtz2/builds/HlyHnD0FJiPLWMKYc/openapi.json