Skip to content

Homes.com Scraper API for Property Data Pipelines

A Homes.com page is a JavaScript-heavy listing surface.

OUTPUT FORMATSHTMLJSONMarkdown

Pulling it reliably means rendering the page, rotating proxies, and shaping the result into fields your pipeline can query. This page explains how a managed scraping API does that in one HTTP request, which parameters control the behaviour, and what each request costs.

What one request returns

The API takes a Homes.com URL plus your API key. Behind the scenes it rotates proxies, spoofs browser fingerprints, and renders JavaScript, then returns a response ready to parse. The documented field set for a listing covers asking price, beds, baths, square footage, lot size, year built, neighborhood, agent name, days on market, and the full image gallery. You can also request rental rates and mortgage-related figures when the page carries them.

Field and control map

Use this table to decide which parameter to set for each part of the job. It is a planning aid, not a guarantee that every page exposes every field.

Choosing the right parameter

Start with the plain URL. Add render_js=true when the listing content only appears after client-side execution; the API runs the page in a real headless browser and returns post-render HTML. Add country_code when content varies by geography and you need a residential IP in a specific country. For structured output, pass extract_rules with CSS selectors mapped to field names, or ai_extract_rules with a natural-language description of the fields you want. If a target becomes aggressive, enable stealth_proxy.

Worked example: one listing request

Suppose you want the asking price, bed and bath counts, square footage, and agent name for a single Homes.com listing. You send the listing URL with render_js=true so the page finishes loading, and an extract_rules map that names each field against its selector. The response comes back as parsed JSON. If the selectors break after a site change, switch to ai_extract_rules with a plain-language field list and compare the output before promoting it to production.

Credit cost checklist

Credits are consumed per request, and the cost depends on which features you enable. Before you size a plan, walk through these questions: Does the page need JavaScript rendering? Each successful request that enables JS rendering costs 5 API credits. Do you need premium proxies? Each successful request that enables them costs 10 or 25 API credits, depending on whether JS rendering is disabled or not. Do you need geotargeting? It routes through 200+ countries and territories, or 40+ on classic proxies. Do you need screenshots or extraction rules? Both are available on every standard plan. Credits are valid for one month and do not roll over, and requests start at 1 credit each.

Concurrency versus target throttling

The API enforces concurrency limits per plan, not per-target rate limits. That means the ceiling is how many requests you can have in flight at once, not how many you can send to Homes.com in a given minute. If Homes.com throttles aggressive patterns, space out requests or use multiple sessions. Raising your plan raises concurrency; it does not change how the target responds.

Setup path

Create an account to get an API key and free starting credits. Install the SDK for your stack — Python, Node, Go, PHP, or Ruby — or call the HTTP endpoint directly. 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 test without writing code first. Code samples and documentation cover every major language.

Plan comparison

The plan table below lists the captured monthly prices, credit allowances, concurrency, and feature availability. Treat these as a dated reference and confirm current terms before purchasing.

Homes.com field and request control map
GoalParameter or fieldWhat it does
Render client-side listing contentrender_js=trueRuns the page in a headless browser and returns post-render HTML
Route through a specific countrycountry_codeUses a residential IP in that country
Get structured JSON via selectorsextract_rulesMaps CSS selectors to field names
Get structured JSON via descriptionai_extract_rulesAccepts a natural-language field spec
Handle aggressive blockingstealth_proxyEnables stealth proxy mode on the request
Capture listing fieldsasking price, beds, baths, square footage, lot size, year built, neighborhood, agent name, days on market, image galleryDocumented field set for a Homes.com listing

Field availability depends on the page; the map describes request controls, not a guarantee of every field on every listing.

Frequently asked questions

Will I get blocked when scraping Homes.com?

Requests rotate residential proxies and use a real headless browser, so they resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.

Can I scrape Homes.com without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL.

How do I handle JavaScript when scraping Homes.com?

Pass render_js=true. The page runs in a real headless browser, the JavaScript executes server-side, and you get the post-render HTML back.

Can I scrape Homes.com from a specific country?

Yes. Pass country_code to route through a residential IP in that country. This matters when content varies by geography.

What's the rate limit for scraping Homes.com?

The API applies concurrency limits per plan, not per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from Homes.com?

Choose one of two routes. With extract_rules you supply CSS selectors, each paired with the field name it should fill. With ai_extract_rules you describe the fields you want in plain language instead of writing selectors. Either way, the response arrives as parsed JSON rather than raw HTML.