# Idealista Property Scraper & Listing Monitor (`luminar/idealista-property-scraper-listing-monitor`) Actor

Export public Idealista homes in Spain, Portugal, or Italy, request bounded details, or monitor complete comparable searches with safe removal semantics.

- **URL**: https://apify.com/luminar/idealista-property-scraper-listing-monitor.md
- **Developed by:** [Luka](https://apify.com/luminar) (community)
- **Categories:** Automation, Developer tools, Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.45 / 1,000 listing 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

<p><img src="https://apify-image-uploads-prod.s3.us-east-1.amazonaws.com/PauBFWuMMPOxlAejO-actor-szJKcRdeaqpow9lcC-iM0I7cF5bk-download-app-idealista-logo.png" alt="Official Idealista app logo" width="72" height="72"></p>

Export public homes from Idealista Spain, Portugal, and Italy. Choose fast listing cards, bounded public details, or a safe repeat-run monitor that never treats incomplete observation as a removal.

![Actual normalized Idealista listings and coverage receipt from a live public homes export](https://api.apify.com/v2/key-value-stores/DJgPR6wwS2tIaLDQW/records/idealista_property_monitor--a7a1ee37be4d2a04-real-public-output.png)

### Quick start

This example exports 25 homes for sale in Lisboa:

```json
{
  "workflow": "search_listings",
  "country": "PT",
  "location": "Lisboa",
  "operation": "sale",
  "detailLevel": "cards",
  "maxProperties": 25,
  "maxBuyerChargeUsd": 1
}
```

Use `ES` with Madrid, `PT` with Lisboa, or `IT` with Milano as simple starting points. You can also paste one or two matching public Idealista search URLs for other areas or source-backed filters.

### Choose the right workflow

`search_listings` exports current properties immediately. Card mode uses fewer source requests and supports up to 114 rows. `full_public_details` opens each selected public property page and is limited to 12 rows.

`track_listing_changes` is cards-only. The first run creates a quiet baseline when the requested scope finishes completely. A repeat run with the same country, targets, operation, limits, sorting, and `stateNamespace` compares current facts against that baseline. Later complete runs can return `NEW`, `UPDATED`, or confirmed `ENDED` changes.

### Output

Card rows can include stable ID, Idealista property code, canonical URL, sale/rent operation, requested homes category, price, currency, surface, deterministic price per m², rooms, floor, title, description, photos, amenities, and source placement.

Public detail rows can additionally include the published location or address, bathrooms, energy certificate, richer characteristics and media, agency or public contact data, and source timestamps when the page publishes them.

Every Dataset also includes a free `coverage` row. It explains targets, pages, discovered and delivered rows, rejected identities, caps, and whether the observation was safe for monitoring.

### Input guide

- `country` selects the matching Spain, Portugal, or Italy site.
- `location` creates the public homes search for a common city or area.
- `searchUrls` replaces the generated location with one or two matching public search URLs.
- `operation` chooses sale or rent.
- `detailLevel` chooses cards or bounded public details.
- `maxProperties` limits returned rows. Reaching the limit can produce valid `CAPPED` output.
- `stateNamespace` separates independent monitors. Keep one namespace and scope sequential.
- `maxBuyerChargeUsd` stops before the maximum projected charge can be exceeded.

### Pricing

Charges are event-based, so small successful exports cost less than large ones. Higher Apify plans receive lower unit prices automatically:

| Event | Free | Starter | Scale | Business |
|---|---:|---:|---:|---:|
| `listing_result` | $0.00045 | $0.00045 | $0.00045 | $0.00045 |
| `source_target` | $0.0045 | $0.0018 | $0.0009 | $0.0009 |
| `detailed_listing_result` | $0.0037 | $0.0037 | $0.0037 | $0.0037 |
| `monitor_page` | $0.0091 | $0.0091 | $0.0091 | $0.0091 |
| `change_event` | $0.0005 | $0.0005 | $0.0005 | $0.0005 |

A cards export is one successful `source_target` plus one `listing_result` per delivered property. Detail mode uses `detailed_listing_result` instead of the card event. Monitoring charges only trustworthy complete pages and delivered changes.

Blocked and failed targets do not create paid property rows. The Apify run screen and `maxBuyerChargeUsd` remain the final charge controls.

### Coverage and reliability

`COMPLETE` means every requested target finished inside the declared limits. `EMPTY_CONFIRMED` means the expected source shape positively confirmed zero rows. `CAPPED` means a row, page, byte, request, or runtime limit stopped full traversal; returned property rows remain useful, but removals cannot be evaluated.

`PARTIAL`, `FILTERED`, `CAPPED`, `BLOCKED`, and `FAILED` never advance absence state. `ENDED` requires two consecutive complete comparable absences. A missing observation is never treated as deletion.

No Idealista login is required. The Actor does not accept imported account cookies or tokens, does not access private content, and does not solve CAPTCHAs. A visible CAPTCHA stops the affected route.

### API and automation

Run the Actor from Apify Console, API, schedules, webhooks, or integrations. For monitoring, reuse the exact same input and `stateNamespace` on each scheduled run. Read property and change rows from the Dataset, and use the `coverage` row or `OUTPUT` record before acting on removals.

A naturally occurring market change was not observed during the bounded validation period. The same parser, normalizer, stable identity, comparison, atomic delivery, and saved-state path is exercised with deterministic transition fixtures.

### Support and FAQ

If a run is capped, raise the relevant limit only when you need broader observation; the existing rows are still valid. If a run is blocked or failed, retry later rather than interpreting it as an empty market. When asking for help, share the run ID, input, country, target URL, and coverage status, but never share private account cookies or tokens.

# Actor input Schema

## `workflow` (type: `string`):

Monitoring advances state only after trustworthy complete coverage. Capped, partial, filtered, blocked, failed, or malformed scans cannot confirm absence.

## `country` (type: `string`):

Selects the matching anonymous public Idealista site for Spain, Portugal, or Italy.

## `location` (type: `string`):

Common city names are normalized into the selected country's public homes-search route. Use an exact public search URL for other areas or source-backed filters.

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

Selects the country-specific public sale or rent route.

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

The canary-backed first release exports the public homes search only.

## `detailLevel` (type: `string`):

Public details adds one bounded property-page request per returned listing and is limited to 12 rows. Detail fields remain nullable when the source does not publish them; monitoring is cards-only.

## `maxProperties` (type: `integer`):

Card mode supports up to 114 rows. Public-detail mode is runtime-limited to 12 rows. Reaching an unexhausted source scope produces CAPPED coverage and cannot confirm removal.

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

Replaces the generated location target with one or two anonymous public search URLs from the selected country. The country host and sale/rent route must match the input.

## `maxPagesPerTarget` (type: `integer`):

A proven bounded ceiling. If the search still has another page, coverage is CAPPED and removal checks stay frozen.

## `sort` (type: `string`):

The canary-backed first release preserves Idealista source order.

## `stateNamespace` (type: `string`):

Separates saved monitors. Keep targets, filters, limits, and sorting identical across runs.

## `maxBuyerChargeUsd` (type: `number`):

Stops before source work if the maximum event vector would exceed this amount.

## `maxRequests` (type: `integer`):

Internal ceiling for first-party source requests in one run.

## `maxSourceBytes` (type: `integer`):

Internal ceiling for total source response bytes in one run.

## `maxRuntimeSecs` (type: `integer`):

Internal source-work runtime ceiling.

## `maxEstimatedPlatformUsd` (type: `number`):

Internal planning guard; settled Apify usage remains authoritative.

## Actor input object example

```json
{
  "workflow": "search_listings",
  "country": "PT",
  "location": "Lisboa",
  "operation": "sale",
  "propertyType": "homes",
  "detailLevel": "cards",
  "maxProperties": 25,
  "maxPagesPerTarget": 6,
  "sort": "source_order",
  "stateNamespace": "default",
  "maxBuyerChargeUsd": 1,
  "maxRequests": 20,
  "maxSourceBytes": 15000000,
  "maxRuntimeSecs": 300,
  "maxEstimatedPlatformUsd": 0.06
}
```

# Actor output Schema

## `dataset` (type: `string`):

Open every property, change, or coverage row.

## `properties` (type: `string`):

Open the mixed Dataset with property columns selected.

## `changes` (type: `string`):

Open deterministic NEW, UPDATED, and ENDED transition rows. Natural live change was not observed before publication.

## `coverage` (type: `string`):

Open completion and cap columns.

## `runSummary` (type: `string`):

Open the authoritative coverage, state, billing, public-source classification, and buyer-cost receipt.

# 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 = {
    "workflow": "search_listings",
    "country": "PT",
    "location": "Lisboa",
    "operation": "sale",
    "propertyType": "homes",
    "detailLevel": "cards",
    "maxProperties": 25,
    "maxPagesPerTarget": 6,
    "sort": "source_order",
    "stateNamespace": "default",
    "maxBuyerChargeUsd": 1,
    "maxRequests": 20,
    "maxSourceBytes": 15000000,
    "maxRuntimeSecs": 300,
    "maxEstimatedPlatformUsd": 0.06
};

// Run the Actor and wait for it to finish
const run = await client.actor("luminar/idealista-property-scraper-listing-monitor").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 = {
    "workflow": "search_listings",
    "country": "PT",
    "location": "Lisboa",
    "operation": "sale",
    "propertyType": "homes",
    "detailLevel": "cards",
    "maxProperties": 25,
    "maxPagesPerTarget": 6,
    "sort": "source_order",
    "stateNamespace": "default",
    "maxBuyerChargeUsd": 1,
    "maxRequests": 20,
    "maxSourceBytes": 15000000,
    "maxRuntimeSecs": 300,
    "maxEstimatedPlatformUsd": 0.06,
}

# Run the Actor and wait for it to finish
run = client.actor("luminar/idealista-property-scraper-listing-monitor").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 '{
  "workflow": "search_listings",
  "country": "PT",
  "location": "Lisboa",
  "operation": "sale",
  "propertyType": "homes",
  "detailLevel": "cards",
  "maxProperties": 25,
  "maxPagesPerTarget": 6,
  "sort": "source_order",
  "stateNamespace": "default",
  "maxBuyerChargeUsd": 1,
  "maxRequests": 20,
  "maxSourceBytes": 15000000,
  "maxRuntimeSecs": 300,
  "maxEstimatedPlatformUsd": 0.06
}' |
apify call luminar/idealista-property-scraper-listing-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,luminar/idealista-property-scraper-listing-monitor"
        }
    }
}

```

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/szJKcRdeaqpow9lcC/builds/CncSNVmSxIXftxsDS/openapi.json