By the end of this tutorial you will have a Python script that pulls flats for sale from sreality.cz into structured rows: asking price in CZK, layout, city and district, area read from the listing title, photo count and the agency that published each listing.

Sreality is the Czech real-estate portal. Sreality Scraper (reventadata/sreality-scraper) is the Apify Actor built for this site. You send it a search, and it returns one row per listing, read from public pages with no login.

The sample rows in this guide are the whole output of one run I made on 18 November 2026 with a cap of 10 listings. I copied them from that run's dataset and did not edit any value.

Prerequisites

You need three things:

  1. Python 3.11 or newer with pip.
  2. A free Apify account, which you can create with an email address or a GitHub login.
  3. Your API token, which you find in Apify Console.

Install the client and export the token:

pip install -U "apify-client~=3.0" export APIFY_API_TOKEN="your_apify_token_here" 

No scraping code is needed on your side. The Actor does the fetching.

What you'll achieve

In this tutorial you will search sreality.cz for flats for sale, cap the run at ten listings and print one summary line per listing from Python. The same script covers the other categories the Actor reads (houses, land, commercial and other property) and rentals. Only the input changes, and the script stays the same. You can also read the result in Python, as in the last step.

Each row holds the listing's own asking price in CZK and the price per square metre that comes with the listing. You will see one full row in the output section, so you know which fields to expect before you write code that reads them.

Step-by-step guide

Step 1: Open Sreality Scraper

Open the Sreality Scraper page on Apify Store. This tutorial calls the Actor from Python, so the only name you need is reventadata/sreality-scraper.

For current pricing and details, see the Store page.

Step 2: Choose the search

The search is described by a few input fields:

  • offerType: sale or rent. Any other value is refused before the run starts.
  • category: flats, houses, land, commercial or other. Any other value is refused before the run starts.
  • regionId: optional. Sreality's region (kraj) id. Every row carries its regionId.
  • priceFrom and priceTo: optional price limits in CZK.
  • fetchDetails: off by default. When it is on, each listing also gets its full description, usable area, building data, and the agency and broker contact that the listing publishes.
  • maxItems: a cap on the rows pushed. The default is 1000.
  • maxPages: an optional cap on pages of up to 100 listings each.

The proxy is handled for you.

Sreality serves only the first 10,000 listings of any one search. A search that matches more needs a regionId or a price range to reach the rest.

The input below is the one this guide's run used, with offerType and category written out. Both are the defaults.

{ "offerType": "sale", "category": "flats", "maxItems": 10, "maxPages": 1 } 

Step 3: Run it from Python

This script starts the Actor, waits for it, reads the dataset and prints one summary line per listing:

import os from apify_client import ApifyClient # 1. Initialise the client with your token from the environment client = ApifyClient(os.environ["APIFY_API_TOKEN"]) # 2. Describe the search: flats for sale, ten listings, one page run_input = { "offerType": "sale", "category": "flats", "maxItems": 10, "maxPages": 1, } # 3. Start the Actor and wait for it to finish run = client.actor("reventadata/sreality-scraper").call(run_input=run_input) if run is None or run.status != "SUCCEEDED": status = run.status if run else "unknown" raise SystemExit(f"Run did not succeed (status: {status}).") # 4. Read the rows from the run's default dataset items = client.dataset(run.default_dataset_id).list_items().items print(f"Retrieved {len(items)} listings.\n") # 5. Print one line per listing: title and price, then layout, price per m2 and photos for item in items: print(f"{item.get('title')} | {item.get('price')} CZK | {item.get('city')}") print(f" {item.get('subcategory')}, price per m2: {item.get('priceCzkPerM2')} CZK, photos: {item.get('imageCount')}") 

The Actor walks results one page at a time, so keep maxPages small while you test.

Step 4: Read one row

One row from the run's dataset is shown below. The detail columns that are null in this run are left out of the sample, and nothing else is cut.

{ "id": "2106564684", "url": "https://www.sreality.cz/detail/prodej/byt/2+1/x/2106564684", "title": "Prodej bytu 3+kk 62 m²", "offerType": "Prodej", "category": "Byty", "subcategory": "3+kk", "price": 4490000, "currency": "CZK", "priceCzk": 4490000, "priceUnit": "za nemovitost", "priceCzkPerM2": 72419, "areaFromTitleM2": 62, "city": "Uherský Brod", "cityPart": "Uherský Brod", "district": "Uherské Hradiště", "region": "Zlínský kraj", "regionId": 9, "street": "Horní Valy", "latitude": 49.02711769840923, "longitude": 17.649271503099705, "agencySlug": "g2-reality-s-r-o", "agencyId": 13566, "sellerUserId": 67719, "imageUrl": "https://d18-a.sdn.cz/d_18/c_img_qD_E/kQMlcCt5zmChFvGnEjHRPNLW/6962.png", "imageCount": 20, "hasVideo": false, "hasMatterport": false, "isDiscounted": false, "detailFetched": false } 

Understanding your results

Each row is one listing. These are the fields to read first:

  • price and priceCzk hold the asking price in CZK. In this run currency is CZK on all 10 rows, and price equals priceCzk on all 10.
  • priceCzkPerM2 is the price per square metre. On all 10 rows it equals price divided by areaFromTitleM2, rounded to a whole number.
  • areaFromTitleM2 is the area number read from the listing title, such as 62 in "Prodej bytu 3+kk 62 m²". In this run every row has a value.
  • priceUnit reads "za nemovitost" on all 10 rows. That is Czech for "per property".
  • imageCount runs from 15 to 37 in this run, and hasVideo is true on 4 of the 10 rows.
  • All 25 detail columns are null on all 10 rows in this run: the description, usable area, building and energy fields, and the agency and broker contact. detailFetched is false on each row.

Pro tips and advanced usage

  • Keep maxItems and maxPages small while you test. Each one is a hard cap on the run.
  • To reach past the 10,000-listing limit, split a large search with regionId and a price range. The run logs a warning on the first page when a search matches more listings than it serves.
  • Turn fetchDetails on only when you need descriptions and contacts. The run is slower with it on.
  • A price the site sends as zero comes out as null, not 0, so filter on price with that in mind.
  • Compare listings of different sizes on priceCzkPerM2, not on price. A 62 m² flat and a 95 m² flat have very different totals, but their per-square-metre prices can be read side by side.
  • Keep the rows as they come. The dataset holds every field, so you can drop columns in your own script rather than in the Actor's input.
  • When you split a search, run each part on its own and keep the rows from each run separate, so no listing is counted twice by accident.

Troubleshooting common issues

  • An offerType or category outside its list is refused before the run starts, so the Actor does not run.
  • A search with no matches ends as SUCCEEDED with a status message that says nothing matched. Your script then gets zero rows.
  • A run that cannot load any page ends as FAILED with a status message. The script prints the status and stops.
  • A field with no value comes back as null, not missing. Check the field name against the list in Understanding your results. The null columns in this guide are empty in this run only.

Next steps

Change regionId or the price range to compare towns, or set category to houses for a second dataset. To repeat a search on a schedule, save it as an Apify task and attach a schedule to it. Then read the rows in Python as shown above, and check each run's status before you trust its count.