Suggest locations for house-price research
View all Rightmove UK Property Search & Sold Prices endpoints →Find location suggestions for a UK sold-house-price research form using the required string location. The documented example is ch; no minimum query length, paging controls or additional filters are documented. No observed probe response is supplied for this operation. The unverified source example is a JSON object with boolean status, string message and a data array of suggestion objects. Each example suggestion contains string displayName, highlighting, id, locationIdentifier and type fields, plus a highlights array whose objects contain boolean highlighted and string text. REGION appears as a type value in that example but is not established as the only supported type. Use the actual returned labels and validate the selected identifier mapping against the receiving house-price search contract; do not assume id and locationIdentifier are interchangeable or substitute the general property-location autocomplete. This operation suggests search locations, not sold transactions, prices, valuations or listing records. The source example does not establish live suggestion counts, coverage, ordering or freshness.
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-auto-complete API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/house-prices-auto-complete?key=<API_KEY>&location=<location>'
Query Result
Use Cases
- Add a dedicated location picker to a historical sold-house-price research form, using location text as its only documented query input.
- Help a researcher choose among similarly named towns or districts by displaying the returned suggestion labels and type values.
- Keep the selected id and locationIdentifier in separate form fields until their mapping to a house-price search is validated.
- Build a text-safe suggestion renderer that emphasizes highlights segments only when their returned highlighted flags are true.
Frequently asked questions
What does the location parameter accept?
location is a required string used to find house-price research locations. ch is the documented example. The supplied documentation does not specify a minimum character count, a default query, pagination or extra filters.
What response fields are documented, and were they observed?
No observed response is supplied for this operation. The source example shows an object with status, message and a data array. Suggestion objects contain displayName, highlighting, highlights, id, locationIdentifier and type. Treat these as source-example fields rather than verified required keys.
Should a selected suggestion use id or locationIdentifier for the next search?
The source example includes both as distinct string fields. Preserve both and validate the receiving house-price search contract before choosing which one to pass. This evidence does not establish that they are interchangeable or equivalent to identifiers from general listing autocomplete.
How can I display matching text without trusting embedded markup?
The example includes highlights objects with text and highlighted fields, as well as a separate highlighting string. Prefer escaped text segments with application-controlled emphasis, or sanitize any markup before rendering. The highlight structure has not been independently verified.
Does autocomplete return sold prices or cover every UK location?
No prices or transaction records are shown in this autocomplete example; it is a location-suggestion step. The example does not establish exhaustive coverage, a fixed number of suggestions, a guaranteed order or freshness. REGION is an example type, not a proven complete type list.