Find location suggestions for a UK property search
View all Rightmove UK Property Search & Sold Prices endpoints →Complete a location term or phrase using the required location query string. The documented example is ch; the successful observed probe used London. The observed JSON response contained status=true, a string message and a data array of location suggestion objects. Documented item fields are displayName for a display label, locationIdentifier for a location reference and normalisedSearchTerm for normalized search text; these fields are strings when present. No response keys are declared mandatory. The probe established the response envelope and the types of declared fields that were present, not that every suggestion always contains every field. Check the selected reference against the destination search endpoint before using it as an identifier; this operation alone does not establish cross-endpoint compatibility.
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/auto-complete API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/auto-complete?key=<API_KEY>&location=<location>'
Query Result
Use Cases
- Add a type-ahead location picker to a UK relocation form so users can review suggestions before choosing an area.
- Show an explicit location-disambiguation step when a property-search term could refer to more than one place.
- Store a selected suggestion label alongside its available location reference, then validate that reference before constructing a destination search.
- Compare the entered phrase with normalisedSearchTerm when present to keep a saved location choice consistent with the returned search text.
Frequently asked questions
What should I send in location?
Send a term or phrase in the required location query parameter. The documented example is ch, and the successful observed probe used London. This input is search text, not a property listing ID.
Which fields describe a location suggestion?
The documented data items can contain displayName, locationIdentifier and normalisedSearchTerm as strings. Use displayName for the label, inspect locationIdentifier as a location reference and read normalisedSearchTerm as normalized search text when each is present.
Does every response include all documented keys?
No response keys are declared mandatory. The observed success contained status=true, a string message and a data array of suggestion objects, with present declared fields matching their types. Handle missing item fields and do not require a nonempty suggestion list.
Can I pass locationIdentifier directly to any property-search endpoint?
Do not assume universal compatibility. Validate the selected location reference against the target endpoint and its identifier parameter before use; the autocomplete probe did not establish cross-endpoint identifier compatibility.