See supply as it changes
Track new, updated, relisted, and removed properties across the sources and markets you choose.
WebTruffle builds and operates custom feeds from public real estate portals, agency sites, and other listing sources. We normalize the fields, preserve source context, track changes, and deliver the data in the format your systems expect.
Property-data products
Investment & research teams
Brokerage & operations teams
Track new, updated, relisted, and removed properties across the sources and markets you choose.
Standardize prices, currencies, units, locations, property types, and status labels before analysis.
Use an agreed schema and delivery cadence while we monitor and maintain the collection pipeline.
Every project begins with a source review. Coverage is defined around technical feasibility, public or authorized access, and the fields your workflow genuinely needs.
These fields illustrate a practical data model, not a fixed package. Final availability and definitions are agreed source by source.
Portals use different fields, identifiers, units, and status labels. The same property may appear more than once, change price, disappear, and return under a new listing.
One market can span portals, agency sites, and specialist listings, each with its own structure and terminology.
Source IDs can change, while duplicate listings may describe the same property differently across sites.
Changes to layouts, navigation, and access controls can reduce coverage before the problem reaches a downstream dashboard.
Required-field completeness
Type, unit, and currency validation
Duplicate and relisting review
Count and change-rate anomaly checks
Receive full snapshots or incremental updates as CSV or JSON through Microsoft Azure Blob Storage, Amazon S3, or a tailored dashboard. Cadence, history, and retry behavior are defined during scoping.
Our standard scope covers publicly accessible listing pages. Private MLS feeds, registry records, transactions, ownership data, and other licensed or official datasets require separate authorized access. We do not present public-web listing extraction as official or licensed property data.
Cadence is agreed per source after a feasibility review. It may be daily, weekly, or another practical schedule. We only describe a feed as real time when the source and implementation genuinely support it.
Where the source and collection cadence allow, we retain first-seen and last-seen timestamps, compare snapshots, and apply agreed rules for removals, duplicates, and relistings.
Yes. We can map selected sources into one agreed schema while retaining source URLs, identifiers, timestamps, and useful raw values for traceability.
Tell us the markets, sources, fields, and cadence. We’ll assess feasibility and define the schema, quality rules, and practical first delivery.