Rightmove Scraper API for UK Property Data
A hosted scraping API lets a property-data pipeline request a Rightmove listing URL and receive either rendered HTML or structured JSON back.
The service handles proxy rotation, headless-browser rendering and anti-bot measures, so the caller does not manage a browser fleet. This page explains what comes back, which request options control rendering and extraction, how credits are consumed, and where the practical limits sit.
What the API returns from a Rightmove listing
Each Rightmove listing request can return the asking price or rent, number of beds and baths, square footage, postcode, agent name, days on market, and the full image gallery. The response arrives as either rendered HTML or parsed JSON, depending on the extraction options supplied. That covers the three common developer tasks: price and valuation trend analysis, mapping which agencies list properties across UK postcodes, and analysing property locations for market expansion decisions. The agency-coverage use case works at the listing level and does not require harvesting individual agent contact details.
Request options that change what you get back
Four request parameters do most of the work. render_js=true runs the page in a real headless browser, executes JavaScript server-side, and returns post-render HTML. country_code routes the request through a residential IP in a chosen country, which matters when content varies by geography. extract_rules maps CSS selectors to field names and returns parsed JSON. ai_extract_rules accepts a natural-language specification instead of selectors. A stealth_proxy option is available for pages that present CAPTCHAs. The API applies concurrency limits per plan rather than per-target rate limits, so if Rightmove throttles aggressive patterns, spacing out requests or using multiple sessions is the practical remedy.
Field map: what each returned value is useful for
The table below pairs each returned field with a typical downstream use. It is a reader aid, not a schema contract; the exact response shape depends on the extraction rules supplied.
How request options affect credit cost
Credit consumption depends on which options are enabled per successful request. A plain request starts at one credit. Enabling JavaScript rendering costs 5 credits. Premium proxies cost 10 credits without JS rendering or 25 with it. Stealth proxy costs 75 credits. API credits are valid for one month and do not roll over. New accounts receive a free credit allowance without a credit card, and paid plans begin at a monthly price for higher volume and concurrency. All plan prices are exclusive of VAT; the applicable VAT treatment depends on the customer's billing location and the current terms in force.
Getting from documentation to a first request
The workflow has four steps. Create an account to receive an API key and a free credit allowance. Install one of the published SDKs (Python, Node.js, Go, PHP, Ruby, or Java) or use plain cURL. Send one HTTP call containing the API key and a Rightmove URL. Add advanced parameters only when the page requires them: render_js for JavaScript, stealth_proxy for CAPTCHAs, country_code for geo-targeting, and ai_extract_rules for natural-language extraction. The six SDKs plus cURL examples are documented, and the intended path from docs to first request is a short one: copy an example, substitute your key and target URL, and run it.
Distinguishing the three common failure modes
A request that returns empty or skeleton HTML usually means JavaScript did not execute; add render_js=true. A request that returns a CAPTCHA or block page usually means the IP was flagged; switch to stealth_proxy. A request that succeeds intermittently under load usually means the target is throttling aggressive patterns; the API itself enforces concurrency per plan rather than per-target rate limits, so spacing requests or using multiple sessions is the fix. Geo-varying content is a fourth case: if the same URL returns different listings from different locations, set country_code.
Choosing between HTML, JSON and Markdown
Rendered HTML suits pipelines that already have a parser. extract_rules or ai_extract_rules return parsed JSON directly, which removes a parsing step. A Markdown output option exists for feeding listing content into an LLM for UK property analysis or market-comparison workflows. Screenshots are available to see how a real browser renders a page. No-code automation through n8n is also supported for property-monitoring workflows that should not require scraper code.
Scale, compliance and where the limits sit
The platform is built to scale across thousands of headless browsers and rotating proxies, and typical responses arrive within a few seconds. On the compliance side, the service is designed not to collect or store personal data from scraped sites unless the user explicitly requests it; confirm the current data-processing terms before relying on this for a regulated workflow. Proxy rotation and headless-browser rendering are used to reduce IP-based blocking. These are platform capabilities, not guarantees for any specific target; actual success rates depend on the site's current defences and the request configuration.
| Returned field | Typical use |
|---|---|
| Asking price or rent | Valuation trends, price monitoring |
| Beds and baths | Property segmentation, comparables |
| Square footage | Price-per-area analysis |
| Postcode | Agency coverage mapping, location analysis |
| Agent name | Agency market-share aggregation |
| Days on market | Liquidity and demand signals |
| Full image gallery | Visual records, listing archives |
Field availability depends on the extraction rules supplied; this table describes the fields the API is documented to return from Rightmove listing pages.
| Options enabled | Credits per successful request |
|---|---|
| Plain request | 1 |
| render_js=true | 5 |
| Premium proxy, no JS rendering | 10 |
| Premium proxy with JS rendering | 25 |
| stealth_proxy | 75 |
Credit costs are per successful request and depend on which options are enabled. API credits are valid for one month and do not roll over. Plan prices are exclusive of VAT.
Frequently asked questions
How do I handle JavaScript when scraping Rightmove?
Pass render_js=true on the request. The page runs in a real headless browser, JavaScript executes server-side, and the post-render HTML is returned.
Can I scrape Rightmove from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.
What is the rate limit for scraping Rightmove?
The API enforces 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 Rightmove?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response comes back as parsed JSON.
Which programming languages can I use to scrape Rightmove?
Any language works. Published SDKs cover Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL is also supported.
How much does it cost to scrape Rightmove?
New accounts receive a free credit allowance without a credit card. Paid plans start at a monthly price for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.