# CZ Reality Scraper (`codingfrontend/cz-reality-scraper`) Actor

Scrapes property listings from sreality.cz and bezrealitky.cz. Supports filtering by portal, category, region, price, and floor area, with optional local price-history flags.

- **URL**: https://apify.com/codingfrontend/cz-reality-scraper.md
- **Developed by:** [Coding Frontned](https://apify.com/codingfrontend) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

### What does CZ Reality Scraper do?

**CZ Reality Scraper** is a public property-listing extractor for [Sreality](https://www.sreality.cz/) and [Bezrealitky](https://www.bezrealitky.cz/). It extracts visible listing facts and does not require an account or private endpoint.

### Why scrape Czech property portals?

Use structured listings for market research, comparable-property analysis, rental monitoring, and lead qualification. Select one or both portals, filter by sale/rent, category, region, price, and floor area, and optionally keep a local price history between runs. Apify adds scheduling, API access, exports, monitoring, and integrations.

### What data can it extract?

| Field | Type | Description |
| --- | --- | --- |
| `sourceId`, `title`, `url`, `sourceUrl`, `canonicalUrl`, `portal` | string | Normalized public listing identity, canonical URL, and source portal. |
| `source`, `sourceDomain`, `scrapedAt` | string/date-time | Source and provenance for the public observation. |
| `price`, `currency`, `area` | number/string | Observed price and area values. |
| `category`, `offerType`, `propertyType` | string | Public classification fields. |
| `locality`, `region`, `latitude`, `longitude` | string/number | Visible location information. |
| `images` | array | Absolute public image URLs. |
| `priceChanged`, `previousPrice`, `daysTracked` | mixed | Optional local history indicators. |
| `scrapedAt` | date-time | Time the public observation was normalized. |

### How to scrape Sreality or Bezrealitky

1. Choose `portals`, `categories`, and `offerType` in the Input tab, or provide exact public `startUrls` for individual Sreality or Bezrealitky listing/detail pages.
2. Add optional `regions`, `maxPrice`, or `minArea` filters.
3. Set `maxListings` and run the Actor.
4. Download the dataset as JSON, CSV, Excel, or HTML, or call it through the API.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

### Cost and performance

The Actor uses standard Apify compute units. Keep `maxListings` bounded and schedule only as often as your market-monitoring use case requires.

### Input and output

See the input tab for full configuration options. A listing row resembles:

```json
{
  "sourceId": "cz-reality:sreality:42",
  "sourceDomain": "www.sreality.cz",
  "canonicalUrl": "https://www.sreality.cz/detail/42",
  "source": "cz-reality",
  "portal": "sreality",
  "id": "42",
  "title": "Byt 2+1",
  "url": "https://www.sreality.cz/detail/42",
  "sourceUrl": "https://www.sreality.cz/hledani/prodej/byty",
  "scrapedAt": "2026-09-17T00:00:00.000Z"
}
```

If a portal blocks a public request, an exact diagnostic row with `recordType: "diagnostic"`, `diagnosticType`, source/final URL provenance, `sourceDomain`, `error`, `errorCode`, and `scrapedAt` explains the boundary instead of inventing listings. Exact `startUrls` are limited to HTTPS on the two official portal hosts and are useful when a public detail page is available while a generated search page is not.

Normal listing rows contain business and source fields only; instrumentation is not part of the active dataset contract. Requests stay public; `proxyConfiguration` optionally enables standard Apify Proxy routing and `OUTPUT_SUMMARY` reports whether it was used. No reader service, login, or access-control bypass is attempted.

For local verification, set `testMode` with a safe relative `fixtureFile` or bounded `fixtureJson`. Fixture mode never contacts either portal.

### FAQ, disclaimers, and support

Only public listing information is collected. Respect each portal's terms, robots guidance, rate limits, and applicable law. Public pages can contain personal data; do not process it without a legitimate reason. Use the Issues tab for feedback and the API tab for programmatic access.

# Actor input Schema

## `portals` (type: `array`):

Public property portals to query.

## `startUrls` (type: `array`):

Optional exact HTTPS listing or detail URLs on www.sreality.cz or www.bezrealitky.cz. When supplied, these are queried instead of generated portal searches.

## `categories` (type: `array`):

Property categories to include.

## `offerType` (type: `array`):

Transaction types to include.

## `regions` (type: `array`):

Optional locality or region text filters.

## `maxPrice` (type: `number`):

Exclude listings above this price.

## `minArea` (type: `number`):

Exclude listings below this area in square metres.

## `maxListings` (type: `integer`):

Maximum number of listings emitted per portal.

## `enableHistory` (type: `boolean`):

Compare listings with records stored from earlier runs.

## `historyStoreId` (type: `string`):

Named key-value store used for optional history tracking.

## `timeoutMs` (type: `integer`):

Maximum time allowed for each direct public request.

## `userAgent` (type: `string`):

Optional transparent HTTP user-agent string.

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

Optional standard Apify Proxy configuration for public portal requests; no access-control bypass is attempted.

## `testMode` (type: `boolean`):

Use a local fixture and never request either portal.

## `fixtureFile` (type: `string`):

Safe relative path to a local HTML or JSON fixture used only in test mode.

## `fixturePath` (type: `string`):

Compatibility alias for fixtureFile.

## `fixtureJson` (type: `string`):

Bounded fixture body used only in test mode.

## Actor input object example

```json
{
  "portals": [
    "sreality"
  ],
  "categories": [
    "domy"
  ],
  "offerType": [
    "prodej"
  ],
  "regions": [],
  "maxListings": 20,
  "enableHistory": false,
  "historyStoreId": "cz-reality-history",
  "timeoutMs": 30000,
  "testMode": false
}
```

# Actor output Schema

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

No description

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

No description

## `runSummaryLegacy` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("codingfrontend/cz-reality-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("codingfrontend/cz-reality-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 '{}' |
apify call codingfrontend/cz-reality-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,codingfrontend/cz-reality-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/ydl02B394fqlY6OvB/builds/aTnV5bRNmffqjijik/openapi.json