# Otodom Poland Real Estate Scraper (`devilscrapes/otodom-poland-real-estate-scraper`) Actor

Scrape sale and rent listings from Otodom.pl, Poland's #1 property portal. Get clean numeric price, area, room, district, and city data per listing while we handle blocks and fingerprint rotation for you.

- **URL**: https://apify.com/devilscrapes/otodom-poland-real-estate-scraper.md
- **Developed by:** [DevilScrapes](https://apify.com/devilscrapes) (community)
- **Categories:** Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

<div align="center">
  <img src=".actor/icon.svg" width="160" alt="Devil Scrapes mark" />

## Otodom Poland Real Estate Scraper

**💰 $2.00 / 1 000 results**  ·  pay only for results  ·  no credit card to try

*We do the dirty work so your dataset stays clean.* 😈

Scrape sale and rent listings from Otodom.pl, Poland's #1 property portal — clean numeric price, area, room, district, and city data per listing.

</div>

***

### 🎯 What this scrapes

Otodom.pl is Poland's #1 property portal, and the rival cluster targeting it is the deepest we've measured in this fleet: 41 Actors already compete for it on the Apify Store, 16 with real paying users, the leader (`fatihtahta/otodom-pl-scraper`) running 90 jobs a month for 145 users. This Actor pulls listing cards straight off Otodom's own search-results JSON for both sprzedaż (sale) and wynajem (rent) — flats, houses, plots, commercial units, warehouses, and garages — across as many Polish cities and districts as you want in a single run, and normalizes every card into clean numeric fields: bare PLN price, price-per-m², floor area, room count, and district/city/province, instead of forcing you to scrape the rendered page yourself.

### 🔥 What we handle for you

- 🛡️ **Browser fingerprint rotation** — `curl-cffi` impersonates real Chrome and Firefox TLS handshakes, rotated across requests, so the target sees a browser, not Python.
- 🌐 **Proxy session rotation** via Apify Proxy — fresh session and exit IP on every block, always pinned to a Polish (`PL`) residential exit so you never get a wrong-country page silently.
- 🔁 **Retries with exponential backoff** on `408 / 429 / 5xx` — up to 5 attempts per page, `Retry-After` honoured.
- 🧱 **Search- and page-level fault isolation** — one blocked search or one bad listing is skipped and logged, never crashes the run.
- 🧊 **Clean, typed dataset rows** — Pydantic-validated, ISO-8601 timestamps, numeric price/area/room fields with an explicit currency instead of one rendered blob.
- 💰 **Pay-Per-Event pricing** — you only pay for results that hit your dataset. No data, no charge.

### 💡 Use cases

- **Home-buyer market research** — pull current sprzedaż listings for a Polish city, price-per-m² included, to compare districts fast.
- **Rental market benchmarking** — track wynajem listing prices and area across Warsaw, Kraków, Wrocław, and other cities in one run.
- **PropTech and real-estate analytics** — feed a clean, deduped listings dataset into a pricing or valuation model.
- **Relocation services** — build client-facing property shortlists with district, room-count, and fee data included.

### ⚙️ How to use it

1. Click **Try for free** at the top of the page.
2. Add one or more searches — pick a transaction type (sale/rent), a property type, and a location path copied from an otodom.pl search URL (e.g. `mazowieckie/warszawa/warszawa/warszawa`).
3. Click **Start**. Output streams into the run's dataset.
4. Export from **Storage → Dataset** as JSON, CSV, or Excel — or fetch via the API.

### 📥 Input

| Field | Type | Required | Default | Notes |
|---|---|:--:|---|---|
| `searches` | `array` | **yes** | — | 1-50 structured searches: `transactionType` ('sale'|'rent'), `propertyType` ('flat'|'house'|'room'|'plot'|'commercial'|'warehouse'|'garage'), `locationPath`, `maxPages` (1-50). |
| `maxResults` | `integer` | no | 100 | Cap on rows this run, summed across all Searches. |
| `proxyConfiguration` | `object` | no | RESIDENTIAL group | The Actor pins country\_code='PL' internally whenever a proxy is used (never user-configurable). |

#### Example input

```json
{
  "searches": [
    {
      "transactionType": "sale",
      "propertyType": "flat",
      "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
      "maxPages": 2
    },
    {
      "transactionType": "rent",
      "propertyType": "flat",
      "locationPath": "malopolskie/krakow/krakow/krakow",
      "maxPages": 1
    }
  ],
  "maxResults": 40,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

### 📤 Output

Every row is one dataset item.

| Field | Type | Notes |
|---|---|---|
| `listing_id` | `string` | Otodom's numeric ad id, stringified — stable, globally unique. |
| `url` | `string` | Canonical https://www.otodom.pl/pl/oferta/<slug> detail URL. |
| `transaction_type` | `string` | 'sale' or 'rent', from the listing itself. |
| `property_type` | `string` | Otodom's estate label, e.g. 'flat', 'house', 'investment'. |
| `title` | `string` | Listing headline as shown on the search card. |
| `price` | `['number', 'null']` | Asking price (sale) or monthly rent (rent). |
| `currency` | `string` | Always 'PLN'. |
| `price_per_sqm` | `['number', 'null']` | Otodom's own computed price/m². |
| `additional_rent_fee` | `['number', 'null']` | Monthly administrative/maintenance fee (czynsz), separate from price. |
| `area_sqm` | `['number', 'null']` | Floor area in square metres. |
| `terrain_area_sqm` | `['number', 'null']` | Plot/terrain area in square metres, for houses and plots. |
| `rooms` | `['integer', 'null']` | Room count, parsed from Otodom's enum label. |
| `floor` | `['string', 'null']` | Otodom's raw floor label, e.g. 'FIRST', 'GROUND'. |
| `district` | `['string', 'null']` | District/neighbourhood name, when geocoded. |
| `city` | `['string', 'null']` | City name from the listing's address. |
| `province` | `['string', 'null']` | Voivodeship (province) name. |
| `is_private_owner` | `['boolean', 'null']` | True when listed directly by owner. |
| `is_promoted` | `['boolean', 'null']` | True when Otodom marks the ad as promoted. |
| `image_urls` | `array` | Gallery photo URLs (empty OK). |
| `scraped_at` | `string` | ISO 8601 UTC row-creation timestamp. |

#### Example output

```json
{
  "listing_id": "65432101",
  "url": "https://www.otodom.pl/pl/oferta/mieszkanie-3-pokoje-mokotow-warszawa-ID4abcd",
  "transaction_type": "sale",
  "property_type": "flat",
  "title": "Przestronne mieszkanie na Mokotowie",
  "price": 850000.0,
  "currency": "PLN",
  "price_per_sqm": 15454.5,
  "additional_rent_fee": 600.0,
  "area_sqm": 55.0,
  "rooms": 3,
  "floor": "FIRST",
  "district": "Mokotów",
  "city": "Warszawa",
  "province": "mazowieckie",
  "is_private_owner": false,
  "is_promoted": true,
  "image_urls": [
    "https://ap.otodom.pl/img/65432101_large.jpg"
  ],
  "scraped_at": "2026-09-17T12:00:00+00:00"
}
```

### 💰 Pricing

Pay-Per-Event — you pay only when these events fire:

| Event | USD | What it is |
|---|---:|---|
| `actor-start` | $0.20 | One-off warm-up charge per run |
| `result-row` | $0.0018 | Per unique dataset item |

Example: 1 000 results at the rates above ≈ **$2.00**. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit.

### 🚧 Limitations

v1 is search-results only — no detail-page enrichment, so fields only the detail page carries (full description text, energy label, exact address, building year) are out of scope for v1. `district` is null when a listing's reverse-geocoding doesn't carry one (common for some rural/plot listings). A `location_path` must be copied from a real otodom.pl search URL's path segments — a free-text city name alone is not accepted, since Otodom's own path vocabulary is what determines which listings a search matches.

### ❓ FAQ

**Do I need an Otodom account or API key?**

No. This Actor scrapes Otodom.pl's own publicly listed property data — no login, no API key.

**How do I find my `locationPath`?**

Search on otodom.pl with your filters, then copy the path segments after `/wyniki/sprzedaz/mieszkanie/` (or `/wynajem/...`) from the resulting URL — e.g. `mazowieckie/warszawa/warszawa/warszawa`.

**Can I scrape multiple cities and both sale and rent in one run?**

Yes — add as many `searches` entries as you want (up to 50), mixing transaction types, property types, and cities freely; we dedupe across all of them.

**Why is there no `enrich` option like some of your other real-estate Actors?**

Otodom's search-results JSON already carries price, area, rooms, fees, and location — v1 focuses on getting that data reliably rather than shipping a partial detail-page enrichment toggle.

### 💬 Your feedback

Spotted a bug, hit a weird edge case, or need a new field? Open an
issue on the Actor's **Issues** tab on Apify Console — we ship
fixes weekly and we read every report.

***

<div align="center">

Built by **[Devil Scrapes](https://apify.com/DevilScrapes)** 😈 — a small fleet of
opinionated public-data Actors. Honest pricing, real engineering, zero fine print.

</div>

# Actor input Schema

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

1-50 structured searches. Each item: transactionType ('sale'|'rent'), propertyType ('flat'|'house'|'room'|'plot'|'commercial'|'warehouse'|'garage'), locationPath (region/city/district slug path copied from an otodom.pl search URL, e.g. 'mazowieckie/warszawa/warszawa/warszawa'), and maxPages (result pages to fetch, 1-50).

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

Cap on rows this run, summed across all Searches.

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

Defaults to RESIDENTIAL. The Actor pins country\_code='PL' internally whenever a proxy is used (never user-configurable) — our DATACENTER pack is US-only and would 407 against a PL pin, so RESIDENTIAL is required here.

## Actor input object example

```json
{
  "searches": [
    {
      "transactionType": "sale",
      "propertyType": "flat",
      "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
      "maxPages": 2
    },
    {
      "transactionType": "rent",
      "propertyType": "flat",
      "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
      "maxPages": 2
    },
    {
      "transactionType": "sale",
      "propertyType": "house",
      "locationPath": "malopolskie/krakow/krakow/krakow",
      "maxPages": 1
    },
    {
      "transactionType": "rent",
      "propertyType": "flat",
      "locationPath": "dolnoslaskie/wroclaw/wroclaw/wroclaw",
      "maxPages": 1
    }
  ],
  "maxResults": 40,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `datasetItems` (type: `string`):

All dataset items as JSON.

## `datasetItemsCsv` (type: `string`):

Same data exported to CSV.

## `datasetView` (type: `string`):

Open the run dataset in the Console.

# 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": [
        {
            "transactionType": "sale",
            "propertyType": "flat",
            "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
            "maxPages": 2
        },
        {
            "transactionType": "rent",
            "propertyType": "flat",
            "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
            "maxPages": 2
        },
        {
            "transactionType": "sale",
            "propertyType": "house",
            "locationPath": "malopolskie/krakow/krakow/krakow",
            "maxPages": 1
        },
        {
            "transactionType": "rent",
            "propertyType": "flat",
            "locationPath": "dolnoslaskie/wroclaw/wroclaw/wroclaw",
            "maxPages": 1
        }
    ],
    "maxResults": 40,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("devilscrapes/otodom-poland-real-estate-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 = {
    "searches": [
        {
            "transactionType": "sale",
            "propertyType": "flat",
            "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
            "maxPages": 2,
        },
        {
            "transactionType": "rent",
            "propertyType": "flat",
            "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
            "maxPages": 2,
        },
        {
            "transactionType": "sale",
            "propertyType": "house",
            "locationPath": "malopolskie/krakow/krakow/krakow",
            "maxPages": 1,
        },
        {
            "transactionType": "rent",
            "propertyType": "flat",
            "locationPath": "dolnoslaskie/wroclaw/wroclaw/wroclaw",
            "maxPages": 1,
        },
    ],
    "maxResults": 40,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("devilscrapes/otodom-poland-real-estate-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 '{
  "searches": [
    {
      "transactionType": "sale",
      "propertyType": "flat",
      "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
      "maxPages": 2
    },
    {
      "transactionType": "rent",
      "propertyType": "flat",
      "locationPath": "mazowieckie/warszawa/warszawa/warszawa",
      "maxPages": 2
    },
    {
      "transactionType": "sale",
      "propertyType": "house",
      "locationPath": "malopolskie/krakow/krakow/krakow",
      "maxPages": 1
    },
    {
      "transactionType": "rent",
      "propertyType": "flat",
      "locationPath": "dolnoslaskie/wroclaw/wroclaw/wroclaw",
      "maxPages": 1
    }
  ],
  "maxResults": 40,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call devilscrapes/otodom-poland-real-estate-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,devilscrapes/otodom-poland-real-estate-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/Ka79bj5YaV9fXRo48/builds/ZvMgZ5HJB4gkeTXQb/openapi.json