Skip to content

Sreality Listings Scraper for Czech Property Data

Sreality is a Czech property portal where listings include asking price or rent, floor area, room count, neighborhood, agent details, and photo galleries.

OUTPUT FORMATSHTMLJSONMarkdown

This scraper API accepts a public Sreality URL, renders the page in a real browser, rotates residential proxies, and returns either rendered HTML or parsed JSON. The workflow is built for developers assembling market-comps, rental-yield, or location-scoring datasets without running their own headless browser fleet.

What a Sreality request returns

Each public Sreality listing page can yield asking price or rent, beds, square meters, neighborhood, city, agent name, days on market, and the full image gallery. The API handles JavaScript rendering, proxy rotation, and bot-detection measures so the response is ready to parse rather than a blocked page. You can request rendered HTML and parse it yourself, or supply extraction rules and receive JSON directly.

Three workflows this scraper supports

Property-listing extraction: collect asking prices, room counts, floor areas, neighborhoods, and agent details for Czech market analysis. Rental-price tracking: follow rental rates across neighborhoods over time for rental-yield models or relocation pricing. Neighborhood-amenity extraction: pull amenity and walkability signals tied to each listing for buyer-search or location-scoring tools. All three use the same request pattern: one Sreality URL in, rendered content or structured data out.

Field map for common analysis tasks

Use this map to decide which extraction fields matter for your dataset. Asking price or rent is the core numeric field for market-comps and rental-yield work. Beds and square meters support price-per-square-meter and price-per-room calculations. Neighborhood and city are the grouping keys for geographic comparison. Agent name helps identify listing sources. Days on market supports liquidity and pricing-trend analysis. The image gallery is useful for visual verification or media pipelines. If a field is not visible on the public page, it will not be available to extract.

Choosing between extract_rules and ai_extract_rules

Use extract_rules when you know the page structure and want deterministic CSS-selector mapping to named fields. Use ai_extract_rules when you want to describe the fields in natural language and let the API return structured JSON without writing selectors. A practical checklist: if the Sreality page layout is stable and you need repeatable field names, start with extract_rules. If you are exploring a new listing type or the markup changes often, start with ai_extract_rules and move to selectors once the shape is known. Both paths return parsed JSON.

Request controls and when to use them

render_js enables JavaScript rendering when the listing content depends on client-side execution. stealth_proxy adds stealth handling for pages that present CAPTCHAs or stronger bot checks. country_code routes the request through a chosen country or territory for geo-targeting. premium_proxy uses premium proxies when standard rotation is not enough. Screenshots and extraction rules are available for visual capture and structured output. Each option affects credit consumption, so enable only what the target page requires.

Worked example: tracking rental prices by neighborhood

Suppose you want to compare rents across Prague districts. Send a Sreality rental-search URL with render_js enabled and extract_rules mapping rent, floor area, room count, and neighborhood to named fields. The response is parsed JSON you can load into a table grouped by neighborhood. Because JavaScript rendering costs 5 credits per successful request, a run of 200 rendered pages consumes 1,000 credits. If the same pages also need stealth_proxy, the cost rises to 75 credits per request, so budget accordingly before scaling. This example uses the captured credit rules; confirm current pricing before committing to a large run.

Distinguishing common failure modes

A blocked or CAPTCHA response usually means the target page rejected the request; try stealth_proxy or premium_proxy. Missing fields in the JSON usually mean the selector did not match the rendered page; check extract_rules against the current markup or switch to ai_extract_rules. A geo-restriction or wrong regional content usually means the request exited from an unexpected location; set country_code to the target market. A timeout or empty render usually means JavaScript did not finish; confirm render_js is enabled and the page is publicly reachable. These are diagnostic starting points, not guarantees of resolution.

Credits and plan structure

{{OWNER_FREE_CREDIT_OFFER}} {{OWNER_PRICING_TABLE}} {{OWNER_CREDIT_RULES}} The plan table below lists every tier with its credit allowance, concurrency, and feature inclusions. All prices are exclusive of VAT. Plan names, prices, and feature availability are reference values; confirm current terms before purchase.

Languages and setup

SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works as well. The setup sequence is: create an account to get an API key and free credits, install the SDK for your stack or use cURL, then send a GET request with a Sreality URL. Advanced parameters such as render_js, stealth_proxy, country_code, and ai_extract_rules are added when the page needs them. The goal is a single function call per scrape with no proxy rotation or headless Chrome to manage.

Plan comparison
PlanPriceAPI creditsConcurrent requestsJS renderingProxiesGeotargetingScreenshots & extractionPriority supportAccount managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

All prices are exclusive of VAT. Plan names, prices, and feature availability are reference values; confirm current terms before purchase. {{OWNER_SUPPORT_COMMITMENT}}

Frequently asked questions

Do I need an account to scrape Sreality?

No external account is required on Sreality itself. You sign up for an API key, receive 1,000 free credits without a card, send the Sreality URL, and the API handles rendering and proxy rotation.

Is scraping Sreality legal?

Public-facing pages can usually be scraped, but review the target site's terms of service before deploying and avoid post-login content. Legal compliance depends on your jurisdiction and use case.

What data can I extract from Sreality?

Whatever renders on the public page is fair game. Map CSS selectors with extract_rules, or hand the AI a plain-language description via ai_extract_rules, and structured JSON comes back.

How do I get structured JSON from Sreality?

Two routes work. With extract_rules you attach CSS selectors to the field names you want; with ai_extract_rules you write a natural-language spec instead. Both return parsed JSON.

Which programming languages can I use to scrape Sreality?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape Sreality?

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.