Improvments to Property Search by Address String and Postcode​ 🏘️​

• Replaced ElasticSearch address matching with custom filtering algorithms

Get Multiple Properties 🏘️​

• Add filter[min_plot_size] and filter[max_plot_size] to Get Multiple Properties endpoints. This allows filtering the results to restrict the plot size of properties.
• Add filter[min_outdoor_space_size] and filter[max_outdoor_space_size] to Get Multiple Properties endpoints. This allows filtering the results to restrict the outdoor space size of properties.

All Endpoints 🏠🏘️​

• General bug fixes

All Endpoints 🏠🏘️​

• General bug fixes

All Endpoints 🏠🏘️​

• Greatly increased the concurrency effectiveness of Street Data. When making multiple concurrent requests, there is a noticable performance increase of response times.

All Endpoints 🏠🏘️​

• Add years_at_property to fields[property]. Years at property is a new property field in the core tier. When requested, the number of years the owner has been at the property will be returned. This can be used with the new filter filter[years_at_property] in mulitple properties endpoints.

Get Multiple Properties 🏘️​

• Fix bug where using filter[min_internal_area_square_metres]/filter[max_internal_area_square_metres] returned 0 results.

Get Single Property by Address String and Postcode 🏠​

• .data.postcode in the request body now accepts the postcode with a space. E.g both E15 3JZ and E153JZ are valid postcodes.
• Fix bug where postcodes that contain a letter in their district (e.g SW1A 2AA) returned a HTTP 422.

All Endpoints 🏠🏘️​

• Fix bug when requesting fields[property]=latest_transaction_date where Street Data would always return a HTTP 500 error.
• Fix bug when requesting tier=premium where Street Data would always return a HTTP 500 error.

All Endpoints 🏠🏘️​

• Add construction_materials to fields[property]. Construction materials is a new property field in the core tier. When requested, if a property has a recent EPC certificate, information about the property's construction materials (floor type, roof type, wall type and window type) will be returned.
• Add ownership to fields[property]. Ownership is a new property field in the core tier. When requested, information about a property's ownership (if the property is company owned, overseas owned or is social housing) will be returned.
• Add utilities to fields[property]. Utilities is a new property field in the core tier. When requested, if a property has a recent EPC certificate, information about the property's utilities (mains gas, mains fuel type, solar power, wind turbines) will be returned.
• Add year_built to fields[property] Year built is a new property field in the core tier. When requested a range for the year the property was built will be returned if known. This is a predicted field - if not known a machine learning model returns a predicted value range. The source of the value (predicted or actual) can be found in the response meta object for this field.
• Add propensity_to_let_score to fields[property]. Propensity to let score is a new property field in the premium tier. When requested, a value between 0.0 - 1.0 is returned. Higher values indicate the property is more likely to be able to let. This functions similar to propensity_to_sell_score

🐛 Bug Fixes​

All Endpoints 🏠🏘️​

• Fix bug when requesting fields[property]=estimated_rental_value where Street Data would always return a HTTP 500 error.

Get Single Property by Address String and Postcode 🏠​

• Fix bug where a property would always be returned even if the property requested did not exist. This endpoint will now return a HTTP 404 if it cannot find a property that matches the user address.

All Endpoints 🏠🏘️​

• When passing an incorrect query parameter Street Data will now explictly return a HTTP 400 and will suggest the correct parameter to use. This should help reduce HTTP 500 errors if a typo/incorrect query parameter is used.
• When Street Data returns a status code >=300, contact information for developer support is now included in the response.

🐛 Bug Fixes​

Get Multiple Properties by Point & Radius​ 🏘️​

• Fix bug where explicitly sorting by distance from point (both ascending and descending) resulted in HTTP 500 errors from Street Data.
• Fix bug where when using both distance from point and another sort field, the distance from point was ignored.

All Endpoints 🏠🏘️​

• Add airport_noise to fields[property]. Airport noise is a new property field in the core tier. When requested, if a property has an airport noise report, information about the level of disruption, an assessment and a description will be returned for the property. Properties close to an airport are more likely to have an airport noise report. This is much more likely if properties are located under active flight plans (take off/landing routes).
• Add right_of_way to fields[property]. Right of way is a new property field in the core tier. When requested, if a property has a public right of way that passes through its plot, information about the right of way will be returned for this property. Not all local authorities make this information public - for properties where we don't have this information right_of_way will return None.

Get Single Property by Address String & Postcode 🏠​

• Fix bug causing HTTP 500 errors where the address_match_confidence in the response body could be greater than 1.

Get Multiple Properties 🏘️​

• When requesting a a preview of the cost of a request using the query parameter dry_run, Street Data will always show you a preview of the cost instead of using the cache and showing a preview of £0.00.

All Endpoints 🏠🏘️​

• All endpoints have been updated to fix any inaccuracies in their query parameters. This should lower the chances of getting errors when making valid requests.

📘 Documentation​

All Endpoints 🏠🏘️​

• Street Data now has new documentation to help users when using the API.
• The API documentation has been refreshed and updated to remove any inaccuracies.