Search historical sold house prices by area

View all Rightmove UK Property Search & Sold Prices endpoints →

Search historical sold-property records using the required identifier and type from house-price autocomplete: locationIdentifier supplies identifier, and type supplies the location type. Optional date_sold, property_type, search_radius and sort_by narrow or order results; page requests a numbered result page. A successful observed request used identifier=984, type=REGION, page=1 and sort_by=DeedDate. Its HTTP 200 JSON response had status=true, a string message, a data array of objects and an additional meta object. The optional legacy root fields currentPage, resultsPerPage and totalResultCount were absent, so do not require them or assume particular keys inside meta. The separate, incomplete and unverified source example names property fields such as address, bedrooms, detailUrl, propertyType, images, location and transactions, including dateSold, displayPrice, newBuild and tenure. Those row fields and source-example pagination are not established by the observed probe. The documented detail workflow refers to data[].uuid when available, but this probe does not establish that every row supplies it. This endpoint supports historical-sale research, not live asking prices, an exhaustive property register or an automated valuation.

API Features

Area and location-type pairing Use identifier and type from house-price autocomplete together. The observed successful example used 984 with REGION, rather than a prefixed rental-search identifier.
Completed-sale period and category filters Apply documented date_sold year-window values and property_type choices such as DETACHED, SEMI_DETACHED, TERRACED and FLAT to focus historical-sale research.
Deed-date, price and address ordering Choose one sort_by value: DeedDate for last sold, PriceAsc, PriceDesc or Address. The successful observed request used DeedDate.
Observed data-and-meta response envelope The successful probe returned status=true, a message string, object rows in data and a separate meta object, without optional legacy root pagination fields.
Radius-aware sold-price browsing Combine the documented mile-based search_radius with page while inspecting returned metadata before assuming how many pages can be retrieved.

Live API Demo

GET /api/project/rightmove/house-prices-sold-house-prices

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/rightmove/house-prices-sold-house-prices?key=<API_KEY>&identifier=984&page=1&search_radius=0&sort_by=DeedDate&type=REGION'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

How do I obtain identifier and type for sold-price search?

Use the house-price autocomplete operation: its locationIdentifier maps to identifier and its type maps to type. Both query parameters are required. The observed successful example used identifier=984 and type=REGION.

Which response fields were actually observed?

The successful HTTP 200 response contained status=true, a string message, a data array of objects and a meta object. The evidence does not establish a fixed schema for each property row or specific fields inside meta.

Can I rely on currentPage or totalResultCount at the root?

No. currentPage, resultsPerPage and totalResultCount were optional documented legacy fields and were absent from the observed response. Preserve meta and inspect its actual contents before deriving page counts or continuation behavior. The documented page default is 1.

What values can I use for date_sold and sort_by?

Documented date_sold examples are 1, 2, 3, 5, 10, 15, 20 and 30 for the corresponding number of past years; omission means any sale period. Use one sort_by value: DeedDate, PriceAsc, PriceDesc or Address. The documented default and observed sort value are DeedDate.

Does every result provide a UUID for historical details?

That is not established by this probe. The documented historical-details workflow uses data[].uuid when present. Only enable a UUID-based drill-down for rows that actually supply it; do not derive a UUID from another field.

Is this a current listing feed or a valuation service?

No. It is a historical sold-property search for research. The supplied evidence does not establish exhaustive geographic coverage, real-time updates or an automated valuation capability.

Related operations

Guides

View Subscription Plans →