Skip to content

Real Estate Data Scraper: One Call In, Parse-Ready Listings Out

A property listing page is rarely a clean data source: prices sit inside JavaScript widgets, agent details hide behind lazy loading, and the same site may serve a different layout to every visitor.

OUTPUT FORMATSHTMLJSONMarkdown

A managed real estate data scraper removes that plumbing. You hand over a listing URL, the service renders the page in a real browser, rotates residential proxies, and returns HTML you can parse — or, with extraction rules enabled, structured JSON. This page explains what comes back, which request options change the output, and how the credit cost stacks up before you commit.

What a single call actually returns

The default response is rendered HTML for the target page, ready for your own parser. When you add extraction rules, the response becomes structured JSON. The fields the scraper is designed to surface from a listing page include the address, list price, bedroom and bathroom counts, square footage, lot size, year built, listing agent name, property type, and the image gallery. Anything else that renders on the public page is also reachable — the limit is what the page shows, not a fixed schema. Pages behind a login are out of scope.

Request options that change the output

Four parameters do most of the work on a real estate listing. render_js turns on JavaScript rendering so client-side price and gallery widgets populate before capture. stealth_proxy raises the anti-bot posture when a target gets aggressive. country_code routes the request through a specific geography, which matters when a portal serves different inventory by region. ai_extract_rules lets you describe the fields you want in natural language instead of writing CSS selectors; extract_rules with CSS or XPath is the deterministic alternative when you already know the page structure. Screenshots are available separately if you need to see how the page rendered.

A worked credit-cost example

Credit consumption is not flat per request — it depends on which options you enable. A plain request starts at 1 credit. Turning on JavaScript rendering makes a successful request cost 5 credits. Premium proxies cost 10 credits without JS rendering or 25 with it. Stealth proxy costs 75 credits. So a 1,000-listing crawl with JS rendering and premium proxies would consume roughly 25,000 credits; the same crawl on stealth proxy would consume about 75,000. Treat these per-request figures as a planning worksheet rather than a current price list: confirm the applicable credit rules with the provider before budgeting. That total is the number to compare against a plan's monthly credit allowance before you pick a tier.

Three different failures, three different fixes

A blocked response is not the same as an empty parse, and neither is the same as a wrong selector. If the request returns an error or a challenge page, the anti-bot layer is the problem — try stealth_proxy or a different country_code. If the request succeeds but the JSON is empty, the page probably rendered before the data loaded — check that render_js is on and consider a short wait. If the JSON has the right shape but the wrong values, your selector or AI rule is targeting the wrong element. Diagnosing which of the three you are looking at saves more time than tweaking options at random.

Field and control map

Use this map to pick the minimum options for the fields you need. Address, price, beds, baths and square footage usually require render_js because they are injected client-side. Agent name and property type often sit in static markup and may parse without JS. The image gallery almost always needs JS rendering plus a selector or AI rule. Lot size and year built are the fields most likely to be missing entirely from a listing — treat them as optional and validate before relying on them.

From signup to first request

Create an account to get an API key and any introductory credit allowance the provider offers; check the signup page for whether a card is needed to start. Client libraries are commonly available for Python, Node.js, Go, PHP, Ruby and Java, and raw cURL examples cover the rest — confirm the exact package names and versions in the provider's documentation. A first request is a GET with your API key and the target listing URL. The service handles proxy rotation and headless browser rendering on its side, so there is no browser fleet or proxy pool to maintain. Documentation and code samples are linked from the page's resource section.

Credit cost by request option
OptionCredits per successful request
Plain request1
JavaScript rendering5
Premium proxy, no JS rendering10
Premium proxy with JS rendering25
Stealth proxy75

Per-request credit costs are a planning reference; confirm the provider's current figures before budgeting.

Standard and enterprise plan reference
PlanMonthly priceAPI creditsConcurrent requestsPriority supportAccount managerTeam management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

Prices are exclusive of VAT and are set by the provider; confirm current list prices before subscribing. All standard and enterprise tiers include JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules. Credit validity follows the provider's current credit rules.

Frequently asked questions

Do I need an account to scrape real estate listings?

You need an API key from the provider, but no separate account on the target real estate site. Signing up may include an introductory credit allowance with no card required — check the signup page for the current terms; after that you send the listing URL and the service handles rendering and proxies.

Is scraping real estate listings legal?

Public-facing pages can usually be scraped, but the target site's terms of service decide what is allowed. Review those terms before deploying and avoid content that sits behind a login.

What data can I extract from real estate listings?

Anything that renders on the public page. Use extract_rules with CSS selectors for deterministic fields, or ai_extract_rules to describe the fields in natural language and get structured JSON back.

How do I start scraping real estate listings?

Sign up, copy your API key, and send a GET request with the target listing URL. The service renders the page, rotates proxies, and returns the response. Any introductory credit allowance is enough to test a small batch before you commit to a plan; confirm the current allowance at signup.

Will I get blocked when scraping real estate listings?

Residential proxy rotation and a real headless browser make requests look like normal traffic. If a target site tightens its defenses, enable stealth_proxy on the request to raise the anti-bot posture.

How much does it cost to scrape real estate listings?

Signup may include an introductory credit allowance with no card — check the signup page for current terms. Paid plans start at a monthly price set by the provider for higher volume and concurrency. Per-request cost depends on options: 5 credits with JavaScript rendering, 25 with premium proxy plus JS rendering, and 75 with stealth proxy. Confirm the applicable credit rules and credit validity with the provider before budgeting.

Can I get listing data as Markdown for an LLM?

Yes. The service can return a listing page as clean Markdown, which is useful for feeding property analysis or market-trend workflows into a language model without writing a parser first.

What is the difference between extract_rules and ai_extract_rules?

extract_rules uses CSS or XPath selectors you write yourself, so the output is deterministic and cheap to re-run. ai_extract_rules lets you describe the fields in natural language and the service infers the selectors, which is faster to set up but less predictable when a page layout changes.