Sale listings
Residential and commercial for-sale inventory.
- Asking price and price qualifier
- Property type and tenure
- Bedrooms, bathrooms, floor area
- Features, EPC and council band where published
- New build versus resale classification
With listing lifecycle tracked, not just a snapshot of what is live today.
A snapshot of live listings tells you what is for sale. Tracking the same listings over months tells you what is not selling, what reduced twice before it moved, and which agent's valuations are systematically optimistic. The second dataset is the valuable one.
Free pilot on your own sources, returned in 48 hours. No card, no trial clock — and you keep the sample data either way.
Last verified 5 August 2026 by the Actowiz Solutions Data Engineering team.
Real estate data scraping is the automated collection of property listing information from portals, agency websites and new-build developer sites: asking price or rent, property attributes, location, media, listing agent and current status.
Almost every buyer starts by asking for live listings. Almost every buyer ends up needing the lifecycle instead, because the analytically valuable facts about a property market are all changes rather than states.
Each listing receives a stable Actowiz ID derived from address, attributes and media fingerprinting, so it survives portal ID changes, relistings and agent switches. Where a listing reappears with a new portal reference, we link it and count the elapsed time rather than restarting the clock.
Every status transition is recorded with a timestamp, and where a listing vanishes we distinguish confirmed status changes from disappearance and confirm across subsequent runs before classifying. A withdrawal recorded as a sale corrupts every absorption metric downstream.
Sale and rental listings are the core. Lifecycle and agent data are what most clients build their analysis on once the basics are running.
Residential and commercial for-sale inventory.
Lettings inventory, which moves far faster than sales.
The lifecycle layer, reconstructed from our own runs.
Spatial context for catchment and comparable analysis.
The supply-side view of the market.
Listing presentation, which affects velocity.
A managed engagement, not a tool licence. We own the pipeline and everything that breaks in it.
Every engagement delivers a documented schema. These are the core fields; the full dictionary runs to 140+ and is agreed during scoping.
| Field | Type | What it captures | Refresh |
|---|---|---|---|
listing_id |
string | Stable Actowiz listing identity that survives relisting and portal ID changes | Every run |
portal / portal_ref |
string | Source portal and its own reference, retained for your joins | Every run |
listing_type / status |
enum | Sale, rent or new build, plus current status with transition timestamps | Every run |
price / rent_pcm / price_qualifier |
decimal / string | Asking price or rent with qualifier such as offers-over or guide price | Daily |
price_history |
array | Every price change we have observed, with dates, and a reduction count | Daily |
days_on_market / days_to_let |
int | Elapsed time from first observation, linked across relistings | Daily |
property_type / beds / baths |
enum / int | Property classification and room counts as published | Weekly |
floor_area / tenure / epc |
decimal / enum | Size, tenure and energy rating where the portal publishes them | Weekly |
lat / lon / postcode_sector |
decimal / string | Geolocation to coordinates where permitted, otherwise finest published unit | Weekly |
agent / branch |
string | Listing agency and branch as business entities, not individual agent personal data | Weekly |
image_count / has_floorplan |
int / boolean | Media richness signals, which correlate with listing velocity | Weekly |
Price history is reconstructed from our own observation runs, so it begins when we started collecting that listing. We report the archive start date rather than implying we hold history we never observed.
Property portal structure differs sharply by country. Coverage is built market by market with published-granularity limits stated upfront.
Several portals publish location only to an approximate area rather than an exact address. We geocode to the finest granularity actually published and label it, rather than inferring a precise point that the source never gave. Request a source we don't list →
We deliver into 40+ countries. These are the markets where this particular service is requested most, and the reason demand concentrates there.
| Market | Why demand concentrates here |
|---|---|
| United Kingdom | Two dominant portals with rich published attributes and price history, which makes lifecycle tracking unusually reliable. |
| United States | Large portal ecosystem and strong proptech demand, though MLS licensing shapes what is publicly collectable. |
| Spain, Germany & Netherlands | Deep portal coverage with strong rental datasets, heavily used for BTR and valuation modelling. |
| United Arab Emirates & India | Fast-moving markets with high listing churn, where relisting detection matters more than anywhere else. |
We run production collection across 40+ countries. Coverage depth varies by market and by source, so we confirm what is actually available for your specific markets during scoping rather than claiming uniform global coverage. Ask about a market we don't list →
Proptech and investment teams dominate, with lenders, developers and agencies following.
Your product needs comprehensive, current listing coverage, and maintaining portal scrapers is consuming the engineering roadmap.
A validated listing feed with lifecycle tracking and stable IDs into your systems, with portal changes fixed by us rather than by your team.
Engineering hours reclaimed
Identifying mispriced or stalled stock requires price reduction history and true days on market, which snapshots cannot provide.
Lifecycle-tracked listings with reduction counts, relisting-linked days on market and area-level absorption metrics.
Acquisition yield
Automated valuation and risk models need current asking-price and rental evidence at fine geographic granularity.
Geocoded listing and rental evidence with attributes and lifecycle, delivered as modelling-ready panels by area and property type.
Model accuracy
Site appraisal needs competing scheme pricing, absorption rates and local rental evidence that nobody aggregates.
Scheme-level new build pricing with sales velocity, plus local resale and rental comparables within a defined radius.
Absorption rate
You need to know competitor agency instruction volumes, pricing accuracy and market share by area.
Agent-level portfolio composition, new instruction volume and launch-price-versus-outcome patterns by branch and area.
Market share by area
Housing market analysis needs listing-level evidence rather than lagged transaction indices.
Longitudinal listing panels with asking price, rent, supply counts and absorption by geography and property type.
Signal lead time
Four patterns, with the outcome each is judged on.
Listings are tracked across their lifecycle with every price change recorded and days on market linked across relistings, surfacing properties that have reduced repeatedly and sat unsold — the population where negotiation leverage sits.
Outcome: Acquisition pipelines built from evidenced seller motivation rather than from current asking prices alone.
Rental listings are collected with attributes, geolocation and time-to-let, producing area-level rent evidence by property type and size, plus how quickly stock actually lets.
Outcome: Underwriting based on observed asking rents and letting velocity rather than on lagged index data.
New listing volume, status transitions and time to sold or let are aggregated by fine geographic unit and price band, giving a demand proxy well ahead of transaction data.
Outcome: Market direction visible months before completions data reflects it.
Listings are attributed to agency and branch, tracking portfolio composition, new instruction volume and how often launch prices are reduced before outcome.
Outcome: Competitive positioning and recruitment conversations grounded in observed instruction data.
Clients rarely permit naming. These are real engagement shapes with identifying detail removed, so you can judge whether the work resembles your situation.
The team screened live listings but could not see which properties had reduced repeatedly or been relisted to reset visible days on market.
Lifecycle-tracked listings with every observed price change, reduction counts and days on market linked across relistings and portal changes.
Targeting shifted to evidenced seller motivation rather than current asking price alone.
Underwriting used published rental indices that trailed the market by months, in micro-markets where conditions were changing quickly.
Daily rental listing collection with attributes, geolocation and time-to-let, aggregated to fine geographic units by property type and size.
Underwriting moved onto observed asking rents and letting velocity.
Examples are anonymised at client request. Named references are available on request under NDA. See published case studies →
Before you commit to anything, we run this service against your own sources and send you the output. If the coverage isn't there, the sample will show you that too — which is the point. We would rather lose the deal at the pilot than at month three.
Same collection pipeline and same QA underneath. The difference is who holds the schedule and how the data reaches you.
We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.
Best fit: Teams who need the data, not the infrastructure.
The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.
Best fit: Product and engineering teams building on live data.
A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.
Best fit: Research, strategy and diligence work with a deadline.
Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.
Lifecycle tracking and identity persistence across relistings are the parts in-house builds almost always lack.
| Consideration | In-house scraping team | Generic proxy / DIY tool | Actowiz managed feed |
|---|---|---|---|
| Time to first usable data | 6–12 weeks of engineering before anything is trustworthy | Days, but output needs manual cleanup before use | Free pilot in 48 hours, production in 5–10 business days |
| Who fixes it when a source changes | Your engineers, at the cost of their roadmap | You do — tools report failures, they don't resolve them | We do, same business day, inside the retainer |
| Data quality assurance | Whatever your team has time to build | None beyond HTTP success | Schema validation plus sampled human QA on every run |
| Compliance documentation | Rarely produced, then requested urgently by legal | Not provided; terms risk sits with you | Sources, method and lawful basis documented for review |
| Accountability | Distributed across a team with other priorities | A support ticket queue | A named engineer and an account owner |
| True annual cost | Engineer salaries, proxies, hosting, ongoing maintenance | Low licence fee plus significant hidden analyst time | One fixed monthly retainer, quoted after scoping |
In property data, the single most consequential judgement is what a listing's disappearance means. Get it wrong and every absorption, velocity and demand metric you build is corrupted — in a direction that looks plausible.
Disappearance is never itself recorded as a sale. We look for an explicit status transition where the portal publishes one, confirm absence across multiple subsequent runs before classifying anything, and check for the same property appearing under a different portal reference using address, attribute and media fingerprint matching.
Where the outcome remains genuinely unknown, the record says so — status: disappeared_unconfirmed rather than a guess. Clients modelling absorption can then decide how to treat that population, which is a decision that belongs to them rather than to our pipeline.
This is unglamorous work and it is where most property datasets quietly go wrong. A vendor reporting clean sold-status coverage on portals that never publish sold status is inferring, and inference presented as observation is the thing to worry about.
Buyers usually assume property data comes with an exact address. Often it does not, and the difference between what a portal publishes and what a dataset claims is where a lot of misplaced confidence lives.
We geocode to the finest granularity the source actually publishes, and we label which level that was. A record geocoded from a full address and one geocoded from an area name are not equivalent evidence, and treating them as equivalent produces valuation models with false precision.
We do not attempt to defeat deliberate obfuscation by cross-referencing sources to unmask a specific address the portal chose not to publish. That is both a privacy problem and often a terms problem. Where you need precise positioning, we tell you which markets and portals support it during scoping rather than delivering a coordinate that implies precision it does not have.
Portals, geographies and listing types are scoped first, with published location granularity confirmed per portal before build.
You send us target sites, regions, SKUs or keywords. We return a field-level schema proposal, coverage estimate and refresh recommendation — usually within two working days.
We extract a real sample from your actual targets so you can inspect field fill rates, edge cases and match quality before any commitment.
Our engineers build extractors, then wire validation rules: type checks, range checks, duplicate detection and golden-record comparison against a manually verified subset.
Feeds run at your chosen cadence and land in the warehouse or bucket you already use. Schema changes are versioned and announced before they ship.
We watch coverage drift, fill rates and source changes daily. A named engineer owns your account, and layout breaks are fixed by us — not queued for you.
JSON, JSONL, CSV, Parquet or XLSX, delivered to Amazon S3, Google Cloud Storage, Azure Blob, SFTP, Snowflake, BigQuery, Databricks or a REST/GraphQL endpoint. Webhooks fire on completion, and every batch ships with a manifest containing row counts, schema version and QA results so your pipeline can fail loudly instead of silently ingesting a bad file. Geocoded listings load directly into PostGIS or BigQuery GIS for catchment and comparable analysis.
We collect publicly accessible listing pages. We do not access agent portals, MLS systems or any source requiring credentials, and we do not attempt to unmask addresses a portal has deliberately obscured. Agent data is collected as business information — agency and branch — not as individual personal profiles. Vendor and tenant personal data is never part of the deliverable.
These are contractual, not marketing copy. They appear in the engagement document.
| Commitment | What we hold ourselves to |
|---|---|
| Pilot turnaround | A real sample from your own sources within 48 hours of scoping, at no cost. |
| Go-live | Production collection running within 5–10 business days of sign-off. |
| Delivery punctuality | 99.5% on-schedule delivery, measured monthly and reported to you. |
| Breakage response | Source layout changes triaged same business day; critical sources inside 4 hours. |
| Data quality | Schema validation on every run plus sampled human QA before any delivery leaves us. |
| Escalation | A named engineer and an account owner, not a shared ticket queue. |
| Change requests | Field additions and source changes handled inside the retainer, not re-quoted. |
| Exit | Your historical data exported in full on request. No lock-in, no export fee. |
Plain definitions of the terms used on this page, so procurement and legal reviewers are working from the same vocabulary as your data team.
What proptech, investment and risk teams ask during evaluation.
Where the portal publishes an explicit status transition, yes. Where it does not, we are honest that disappearance is ambiguous — it can mean sold, withdrawn unsold, moved portals or a portal error, and those have opposite analytical meanings.
We never record disappearance as a sale. We confirm absence across multiple runs, check for the property reappearing under a different portal reference via address and media fingerprinting, and where the outcome stays unknown the record says disappeared_unconfirmed. How to treat that population is your modelling decision, not something our pipeline should quietly make for you.
Where the portal publishes them. Location granularity varies enormously: some portals publish full addresses, most publish street level, and some deliberately publish only an approximate area or an offset map pin.
We geocode to the finest granularity actually published and label which level it came from, because a record geocoded from a full address is not equivalent evidence to one geocoded from an area name. We do not cross-reference sources to unmask an address a portal chose to obscure — that is a privacy and terms problem, and a dataset built on it is fragile.
Price history is reconstructed from our own observation runs, so it begins when we started collecting that listing. For many major portals and markets we hold multi-year archives and can backfill; for a portal or geography we have not previously covered, history does not exist.
We report the archive start date per portal so you know exactly what a reduction count is measuring. Some portals also display their own price history, which we capture where published — but we label it as portal-reported rather than blending it with our own observations.
No. MLS systems are credentialed, licensed environments, and access requires membership and a data licence with obligations attached. Scraping is not a legitimate route, and any vendor offering MLS content via extraction is selling you a rights problem.
What we collect is publicly accessible portal and agency listings, which in many markets covers the large majority of marketed stock. If you need MLS specifically, the route is membership or an approved licensed feed, and we will say so rather than quote for it.
Through cross-portal matching on address, attributes and media fingerprinting, delivered with a confidence score. Duplicate listings across portals are extremely common and, if uncollapsed, inflate supply counts substantially.
We deliver both the portal-level records and the resolved property entity, so you can count supply correctly while still seeing per-portal pricing — which occasionally differs for the same property, and is itself informative about agent behaviour.
Yes, with hourly collection on defined geographies for new-listing alerting. This is common for acquisition teams where being first to a listing matters materially.
The honest constraint is portal publication timing rather than our collection speed: many listings appear on portals in batches from agency feeds, so a genuinely real-time signal does not exist upstream. Hourly collection typically puts you within an hour of portal appearance, which is as fast as the underlying publication allows.
We collect agency and branch as business entities — company name, branch, portfolio composition, instruction volume. We do not build individual agent profiles, and we do not collect direct personal contact details for named individuals as a deliverable.
Where a listing displays a named negotiator, that name is not part of the standard schema. Vendor and tenant details are never collected. This keeps the dataset firmly on the business-information side, which is what makes it straightforward for your DPO to approve.
Yes, where portals publish it, including offices, retail units, industrial and land. Commercial listings are structurally messier: pricing is frequently quoted per square foot or per annum, terms vary widely, and many listings say price on application rather than publishing a figure.
We capture the quoted basis explicitly rather than normalising it into a single number, because a per-square-foot annual rent and a capital value are different quantities and blending them silently is a common source of error in commercial datasets.
We quote individually. The main drivers are portal count, geographic scope, whether you need lifecycle tracking with history reconstruction, and refresh frequency.
Lifecycle tracking costs more than snapshot collection because it requires continuous coverage of the same listing population — you cannot reconstruct a reduction you never observed. A defined region across two or three portals at daily refresh sits at the lighter end; multi-country coverage with hourly new-listing alerting and cross-portal deduplication sits higher. One scoping call, a free pilot on your own geography within 48 hours, then a fixed monthly quote. Request a quote.
Send us a region and the portals you care about. We return geocoded listings with attributes and lifecycle fields within 48 hours, with location granularity labelled per portal.
Free pilot, no card, no obligation. We'll tell you which portals in your markets publish precise locations and which do not.Our web scraping expertise is relied on by 4,000+ global enterprises including Zomato, Tata Consumer, Subway, and Expedia — helping them turn web data into growth.
Watch how businesses like yours are using Actowiz data to drive growth.
From Zomato to Expedia — see why global leaders trust us with their data.
Backed by automation, data volume, and enterprise-grade scale — we help businesses from startups to Fortune 500s extract competitive insights across the USA, UK, UAE, and beyond.
We partner with agencies, system integrators, and technology platforms to deliver end-to-end solutions across the retail and digital shelf ecosystem.
Unlock retail insights with Noon Saudi Arabia Product Data Extraction to track prices, inventory, discounts, and product trends in real time.
Unlock Hertz & Avis Rental Car Data for Dynamic Pricing Intelligence to track rental rates, availability, and market trends in real time.
Brazil Car Rental Pricing Intelligence Report 2026 reveals rental price trends, market shifts, competitor rates, and opportunities for smarter pricing.
Whether you're a startup or a Fortune 500 — we have the right plan for your data needs.