Otodom Listing Scraper for Real Estate Teams
Otodom holds a large share of Poland's residential listings.
Collecting those pages at scale usually means managing headless browsers, proxy pools, and anti-bot defenses. A hosted scraping API moves that infrastructure behind a single HTTP request: you send an Otodom URL, the service renders the page in a real browser, rotates the IP, and returns the response your scraper can parse.
What teams pull from Otodom
Most Otodom scraping projects fall into three jobs. The first is fetching property listings for lead generation or inventory tracking. The second is analyzing pricing trends over time. The third is comparing prices across Polish localities before aggregators catch up.
A listing page typically exposes asking price or rent, square meters, room count, locality, year built, agent name, days on market, and the full image gallery. Those fields support a locality-level comparison: pull median asking prices, price-per-m2, and inventory counts, then watch for shifts before they appear in aggregated reports.
Use the field map below to decide which attributes matter for your workflow. If a field renders on the public page, it can be targeted with CSS selectors or requested through AI-driven extraction.
Otodom field and control map
The table below maps common Otodom listing attributes to the request controls that retrieve them. It is a planning aid, not a guarantee that every listing exposes every field.
| Reader goal | Otodom attribute | Request control |
|---|---|---|
| Capture the asking price | Asking price or rent | extract_rules with a CSS selector, or ai_extract_rules |
| Size the property | Square meters | extract_rules or ai_extract_rules |
| Filter by layout | Room count | extract_rules or ai_extract_rules |
| Group by market | Locality | extract_rules or ai_extract_rules |
| Age the building | Year built | extract_rules or ai_extract_rules |
| Contact the lister | Agent name | extract_rules or ai_extract_rules |
| Measure listing freshness | Days on market | extract_rules or ai_extract_rules |
| Review the visuals | Full image gallery | Screenshots and extraction rules |
| Render dynamic content | JavaScript-rendered fields | render_js |
| Handle aggressive blocking | CAPTCHA or IP blocks | stealth_proxy |
| Match a Polish audience | Geo-targeted responses | country_code |
| Get LLM-ready text | Page content as Markdown | Markdown output |
Two failure modes look similar but need different fixes. A blocked request returns a challenge page or an error before the listing content loads; enable stealth_proxy or adjust proxy rotation. A parsing failure returns the page but empty or mismatched fields; inspect the selector or refine the AI extraction prompt. Check which one you have before changing request settings.
How a request runs
- Create an account to get an API key and free test credits.
- Install the SDK for your stack, or use raw cURL. Python, Node.js, Go, PHP, Ruby, and Java are supported.
- Send the Otodom URL with your API key. The renderer executes the page in a real browser and rotates the IP.
- Add advanced parameters when needed: render_js for JavaScript, stealth_proxy for CAPTCHAs, country_code for geo-targeting, and ai_extract_rules for natural-language extraction.
The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL, so you can start without writing scraper code. Documentation and code samples cover the same languages.
Plans, credits, and request controls
Plan prices, credit allowances, concurrency limits, and feature availability are commercial terms that change over time. The figures below are a reference snapshot and should be checked against current pricing before purchase. All prices are exclusive of VAT.
Standard plans:
| Plan | Price | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
Enterprise plans:
| Plan | Price | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
Every standard and enterprise plan includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules.
Credit rules:
- API credits are valid for one month and do not roll over.
- Requests start at 1 credit each.
- Each successful request that enables JS rendering costs 5 API credits.
- Each successful request that enables premium proxies costs 10 or 25 API credits, depending on whether JS rendering is disabled or not.
- Geotargeting routes requests through any of 200+ countries and territories (40+ on classic proxies).
- Team management lets you invite multiple users to your organization and assign a custom quota of credits and concurrency.
Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.
Decision checklist before you commit
- Confirm that the Otodom pages you need are public and do not require login. Review Otodom's terms of service before deploying.
- Estimate your monthly request volume and multiply by the credit cost of your chosen controls. JavaScript rendering alone raises the per-request cost from 1 to 5 credits.
- Decide whether you need premium proxies. They add 10 or 25 credits per successful request, depending on whether JS rendering is enabled.
- Check whether geotargeting matters for Polish locality coverage.
- Plan your extraction method: CSS selectors are predictable but break when markup changes; AI extraction is more resilient but may cost more.
- Verify concurrency needs against the plan limits. Startup supports 100 concurrent requests; Enterprise 120 supports 900.
- Confirm current pricing, VAT treatment, and trial terms with the provider before purchase.
Worked example: comparing two localities
Suppose you want to compare asking prices in two Polish cities. You collect listing pages for each locality, then extract asking price and square meters for every listing. Divide price by square meters to get price-per-m2. Group by locality and compute the median.
A simple table makes the comparison readable:
| Locality | Listings captured | Median asking price | Median price per m2 |
|---|---|---|---|
| City A | Count from your dataset | Median of asking prices | Median of price divided by square meters |
| City B | Count from your dataset | Median of asking prices | Median of price divided by square meters |
Because Otodom listings include days on market, you can also compare how quickly inventory turns over in each locality. Treat the result as a snapshot of the pages you captured, not as a market-wide index, and re-run the comparison on a schedule if you need trend data.
Frequently asked questions
Do I need an account to scrape Otodom?
You do not need an Otodom account. You do need an API key from the scraping provider. Signing up provides free test credits without a card, and then you send the target URL.
Is scraping Otodom legal?
Public-facing pages can usually be scraped, but you should review Otodom's terms of service before deploying and avoid post-login content. Legal requirements vary by jurisdiction and use case.
What data can I extract from Otodom?
You can capture any attribute that appears on the public listing page. Two extraction paths return structured JSON: define CSS selectors through extract_rules, or describe the fields you want and let ai_extract_rules handle the parsing.
How do I start scraping Otodom?
Sign up, get your API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. Free test credits are available.
Will I get blocked when scraping Otodom?
The service rotates residential proxies and uses a real headless browser so requests look like normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.
Can I scrape Otodom without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.
What is the difference between a blocked request and a parsing failure?
A blocked request returns a challenge page or an error before the listing content loads; enable stealth_proxy or adjust proxy rotation. A parsing failure returns the page but empty or mismatched fields; inspect the selector or refine the AI extraction prompt.