# Bezrealitky Scraper - Czech Property Listings & Prices (`listingworks/bezrealitky-scraper`) Actor

Scrape Bezrealitky.cz apartments and houses for sale: price, size, Czech layout code (2+kk), city and GPS. No proxy needed, one flat price per result, no personal data.

- **URL**: https://apify.com/listingworks/bezrealitky-scraper.md
- **Developed by:** [Yusuke Suda](https://apify.com/listingworks) (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.50 / 1,000 result items

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

## Bezrealitky Scraper — Czech property listings without the agency

### Three rows from a real run

| Listing | Price | Layout | Size | Town |
| --- | --- | --- | --- | --- |
| Prodej bytu 3+kk 89 m², Vodárenská, Praha | 13,467,500 CZK | 3+kk | 89 m² | Praha |
| Prodej bytu 4+1 82 m², Sokolovská, Sokolov | 2,790,000 CZK | 4+1 | 82 m² | Sokolov |
| Prodej bytu 4+1 92 m², Družstevní, Hlinsko | 4,490,000 CZK | 4+1 | 92 m² | Hlinsko |

The default run (no place, `maxItems: 100`) on 2026-10-20 returned 100 apartments for sale from all over the Czech Republic in 18 seconds and costs $0.15 at $1.50 per 1,000 listings. Apartments are searched first, so 100 rows are all apartments; raise `maxItems` or set `propertyType: ["house"]` for houses.

Bezrealitky is the Czech Republic's largest site for selling a home without
an estate agent. This Actor turns its apartment and house listings into a
clean table: what the property is, what it costs, where it is, and the Czech
floor-plan code buyers actually search by.

Press Start. The defaults return apartments and houses for sale, with no
configuration needed.

### What a row looks like

```json
{
  "title": "Prodej bytu 2+kk, 54 m², Praha 3 - Žižkov",
  "property_type": "apartment",
  "layout": "2+kk",
  "rooms": 2,
  "price": 7490000,
  "currency": "CZK",
  "living_area_sqm": 54,
  "city": "Praha",
  "state": "Hlavní město Praha",
  "address": "Seifertova, Praha 3 - Žižkov",
  "latitude": 50.0847,
  "longitude": 14.4487,
  "source_url": "https://www.bezrealitky.cz/nemovitosti-byty-domy/…",
  "image_urls": ["https://api.bezrealitky.cz/media/…", "…"],
  "external_id": "812345"
}
```

#### `rooms` and `bedrooms`

Property portals in different countries count different things, so this
catalogue keeps the two apart rather than putting whichever number a site
happens to publish into one column. `rooms` is a real room count. `bedrooms`
is a bedroom count. A site that publishes only one of the two leaves the other
out of the row entirely, so you never have to guess which quantity you are
looking at:

| Site | `rooms` | `bedrooms` |
|---|---|---|
| Willhaben (Austria) | yes | not published |
| Immowelt (Germany) | yes | not published |
| Bezrealitky (Czech Republic) | yes, from the `2+kk` layout | not published |
| Immoweb (Belgium) | not comparable, so left out | yes |
| Rightmove (UK) | not published | yes |

Immoweb does publish a `roomCount`, and it is not a room count in the sense the
other countries use: on one Gent search page a 102 m² three-bedroom flat
reported 1 and an 81 m² one-bedroom reported 9. Rather than ship a column that
cannot be compared, this Actor leaves `rooms` out and gives you `bedrooms`.
Rightmove publishes bedrooms and bathrooms and no total room count at all,
which is the British convention.

`image_urls` is a list of the ad's photo URLs, up to twelve, not a single
thumbnail.

`layout` keeps the Czech floor-plan code as written (`2+kk`, `3+1`, and so
on), because that is how the Czech market describes a home; `rooms` is the
leading number from it, for sorting and filtering.

Bezrealitky is a private-to-private marketplace, so there is no agency
column and no seller information of any kind. Names, phone numbers and email
addresses are never collected — this Actor reads the search results only and
never opens the listing page.

### What people use it for

Price monitoring for the Czech market, where Bezrealitky prices are set by
owners rather than agencies and often move first. Feeding a valuation or
comparison tool that needs Czech data it cannot get from an official API. And
cross-border research, since the site also carries listings in Germany and
Austria (priced in EUR, with the address kept as one line).

### Input

| Field | What it does |
|---|---|
| `propertyType` | `apartment`, `house`, or both (the default). |
| `location` | A Bezrealitky region slug, such as `praha`, `brno` or `jihomoravsky-kraj`. Uses the site's own region pages. Leave empty for everything. |
| `maxItems` | Hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need one. |

There is no `postedAfter` input for this site. Bezrealitky does not publish
listing dates at all, so the Actor refuses the input rather than guessing.
Results come newest first, so a daily run compared on `external_id` against
the previous run gives you what is new.

### Pricing

$1.50 per 1,000 listings (event `result-item`), no start fee. Platform usage is not passed on to you.

You are charged for rows you actually receive. If you set a maximum charge for
the run, it stops cleanly at that limit instead of overshooting it.

### Scope and limits

Public listings only, from the search results page. Year built, floor and
postal code are not on that page. City and region are parsed from Czech
addresses; for German and Austrian listings the whole address stays in
`address` and `city` is left empty. Prices are kept in the listing's own
currency (CZK or EUR) rather than converted.

If the region slug is not one Bezrealitky recognises, the run fails and tells
you.

If Bezrealitky changes its page structure, the run goes red. It does not
return zero rows and report success — a silent scraper is worse than a broken
one, because you find out weeks later.

A run that is blocked or cut short partway also goes red, even though the rows
it did collect are in the dataset and yours to keep. Red here means "this is
not the complete answer", not "you lost the data" — on a schedule, a run that
quietly came back short is the thing you most need to hear about.

Every run also publishes the site's own result count next to the rows it
delivered, so you can see "60 rows of 9,969 the site reports" without going
back to the site to check. That number is what the site says, not a promise
about what one run returns.

### Same data, other countries

This Actor shares its output shape with the Immoweb Scraper (Belgium) and the
Willhaben Immobilien Scraper (Austria). A parser you write for one keeps
working on the others.

### Support

Open an issue on this Actor with the run ID and your input. Answered within
one business day.

# Actor input Schema

## `propertyType` (type: `array`):

Which lists to walk: apartment, house, or both. Leave empty for both.

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

A city or region as bezrealitky writes it in its own URL, e.g. praha, brno, ostrava. Leave empty for the whole country. An unrecognised place fails the run rather than returning unfiltered results.

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

Stop after this many listings. bezrealitky serves 15 per page.

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

Off by default. Turn on (residential, in the site's country) only if runs start getting blocked with 403/429.

## Actor input object example

```json
{
  "propertyType": [],
  "location": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

All owner-listed Czech properties for sale from this run: what each one is, what it costs, and where.

## `pricing` (type: `string`):

The same listings reduced to the fields used for price analysis.

## `runReport` (type: `string`):

Pages read, records delivered, errors, and the verdict (ok, degraded or broken).

# 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 = {
    "propertyType": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/bezrealitky-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 = {
    "propertyType": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/bezrealitky-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 '{
  "propertyType": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call listingworks/bezrealitky-scraper --silent --output-dataset

```

## MCP server setup

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