Get historical property details by UUID
View all Rightmove UK Property Search & Sold Prices endpoints →Retrieve one historical property record using the required uuid query parameter. The documented workflow obtains this value from data[].uuid in a sold-house-price search when that field is supplied; do not substitute a listing ID or derive a UUID from another identifier. This operation has no observed probe response in the supplied evidence. Its unverified response example contains boolean status, string message and an object-valued data field. The example data includes address.displayAddress, detailUrl, propertyType, source, location coordinates and map metadata, and disclaimer dates named earliestTransaction, mostRecentTransaction and lastLoadDate. Its propertyDetails object includes id, bedrooms, bathrooms, soldPropertyLastListed, images, floorplans and streetView metadata. Example transactions contain displayDeedDate, displayPrice, tenure, absoluteChangeType and displayAbsoluteChange. These example fields describe a possible historical-record view, not guaranteed field availability, a current listing or a valuation. Preserve displayed date and price strings rather than assuming they are numeric transaction values.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/rightmove/house-prices-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/house-prices-details?key=<API_KEY>&uuid=767749ea-f35a-4007-8371-41eeb0f9d525'
Query Result
Use Cases
- Open a historical-record detail panel after a user selects a sold-price row that actually supplies a uuid.
- Build a property transaction timeline from displayed deed dates and prices, keeping the original presentation strings.
- Show example-backed bedroom, bathroom and archived-media context beside a historical sale without representing it as a current listing.
- Let a valuation researcher inspect record coverage dates alongside separate asking-price research without inventing a join between historical UUIDs and listing IDs.
Frequently asked questions
Where should the uuid value come from?
The documented workflow uses data[].uuid from the sold-house-price search response when it is present. The parameter is required. If a selected row has no uuid, do not synthesize one or use a listing ID in its place.
Was the historical-details response verified by a probe?
No observed probe response is supplied for this operation. The documented fields here come from an unverified response example and should not be treated as guaranteed coverage.
What sale-history fields are shown in the example?
The example data.transactions array contains displayDeedDate, displayPrice, tenure, absoluteChangeType and displayAbsoluteChange. Displayed prices and dates are strings, so preserve them until your application has an explicit parsing rule.
Does this return a current listing or a property valuation?
It is a historical-record lookup, not a valuation engine or a promise of current availability. The example includes propertyDetails and archived media, but that does not establish a live listing or a verified join to another listing endpoint.
How can I explain the record coverage dates?
The unverified example includes data.disclaimer.earliestTransaction, mostRecentTransaction and lastLoadDate. Present them as supplied historical coverage and load-date metadata, not as a real-time freshness guarantee.