New fields

Estimated rebuild cost for different kind of finishes.

• premium.property.value.rebuild.basic_finish_rebuild_cost_estimate
• premium.property.value.rebuild.modern_finish_rebuild_cost_estimate
• premium.property.value.rebuild.luxury_finish_rebuild_cost_estimate

Breakdowns on material and labour cost for modern finish rebuilds.

• premium.property.value.rebuild.modern_finish_material_cost_estimate
• premium.property.value.rebuild.modern_finish_labour_cost_estimate

Please note that the premium.property.value.rebuild.estimated_rebuild_cost is now deprecated and these new fields should be used instead, although the former field will be kept indefinitely for backwards compatibility.

Commercial Property Data API released.

The force_residential field is now deprecated, please use the new commercial data endpoints to request data for commercial and dual use properties.

New fields

Images of the property from previous listings.

• property.attributes.images.listing_images

Floorplans of the property.

• property.attributes.images.floorplan_images

Clearer predicted fields

We've improved how we expose predicted values by splitting them into three distinct categories:

• [field]_declared_only: Values officially declared in public records.
• [field]_predicted_only: Values derived purely from our prediction models. Will be null when there is a declared value available.
• [field]_declared_and_predicted: Combined values from both predicted and declared.

While the legacy fields are now deprecated, they will remain available for backwards compatibility.

For example, the bedrooms count fields are now structured as:

• New field: bedrooms_declared_only - Legacy field: bedrooms

• New field: bedrooms_declared_and_predicted - Legacy field: bedrooms_predicted

• New field: bedrooms_predicted_only -  Legacy field: N/A