Skip to content
Real estate · aggregators · portals

Property listingsTracked as they change.

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.

Built for

Property-data products

Investment & research teams

Brokerage & operations teams

Decisions this feed supports

See supply, price, and status in motion.

See supply as it changes

Track new, updated, relisted, and removed properties across the sources and markets you choose.

Compare like with like

Standardize prices, currencies, units, locations, property types, and status labels before analysis.

Build on a maintained feed

Use an agreed schema and delivery cadence while we monitor and maintain the collection pipeline.

Source coverage

A stable record for a moving listing.

Every project begins with a source review. Coverage is defined around technical feasibility, public or authorized access, and the fields your workflow genuinely needs.

  • Public property portals
  • Agency and broker listing pages
  • Developer and new-build inventories
  • Rental and short-stay marketplaces
  • Public property-auction listings
  • Commercial and land listing sites
Example agreed schema

Listing identity

Source URL and listing IDListing type and statusFirst seen and last seenAgent or advertiserRaw source labels

Property details

Address and coordinatesProperty typeBedrooms and bathroomsFloor and lot areaAmenities and featuresImages and floor plans

Price & lifecycle

Asking or rental priceCurrency and price periodPrice per unit areaPrice and status changesAvailability datesCapture timestamp

These fields illustrate a practical data model, not a fixed package. Final availability and definitions are agreed source by source.

What makes the feed difficult

A listing is a moving record, not a static row.

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.

Fragmented source schemas

One market can span portals, agency sites, and specialist listings, each with its own structure and terminology.

Unstable property identity

Source IDs can change, while duplicate listings may describe the same property differently across sites.

Silent source changes

Changes to layouts, navigation, and access controls can reduce coverage before the problem reaches a downstream dashboard.

Quality rules

Validated againstthe agreed rules.

Required-field completeness

Type, unit, and currency validation

Duplicate and relisting review

Count and change-rate anomaly checks

Delivery

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.

CSVJSONMicrosoft AzureAmazon S3Tailored dashboards
FAQ

Questions before scoping.

Can WebTruffle provide MLS or official property data?

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.

How often can the feed be updated?

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.

How are removed and relisted properties handled?

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.

Can you combine several portals into one schema?

Yes. We can map selected sources into one agreed schema while retaining source URLs, identifiers, timestamps, and useful raw values for traceability.

Start with a feasibility review

Turn the listings you monitor into data you can use.

Tell us the markets, sources, fields, and cadence. We’ll assess feasibility and define the schema, quality rules, and practical first delivery.