Search UK residential properties for sale
View all Rightmove UK Property Search & Sold Prices endpoints →Search residential sale listings using the required location identifier from the auto-complete result field data[].locationIdentifier. Optional inputs cover minimum and maximum price, minimum and maximum bedrooms, comma-separated property types and keywords, search radius, listing-age window, page and sorting. Boolean flags request garden, parking, auction, buying-scheme, new-home and retirement-home filtering, inclusion of under-offer or sold-subject-to-contract listings, or exclusion of selected housing categories. The documentation does not define how overlapping inclusion and exclusion flags interact. The supplied, truncated documentation example shows currentPage and a data array. Visible listing fields include id, displayAddress, bedrooms, bathrooms, propertySubType, propertyTypeFullDescription, propertyUrl, addedOrReduced, firstVisibleDate, auction, location.latitude and location.longitude. Its price object contains amount, currencyCode, displayPrices and frequency; listingUpdate contains listingUpdateDate and listingUpdateReason; propertyImages contains images, mainImageSrc and mainMapImageSrc. These are unverified example fields, not an observed response for this endpoint or a guarantee that every listing contains them. No live probe response was supplied for this operation; result coverage, filter behavior and inventory freshness remain unverified.
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/property-for-sale API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/property-for-sale?key=<API_KEY>&identifier=<identifier>'
Query Result
Use Cases
- Build buyer brief searches that save the location identifier, price range, bedroom range and property types alongside each shortlist.
- Offer a garden-and-parking search preset for homebuyers while checking the returned listings rather than assuming strict amenity matching.
- Create separately configured auction, new-home and retirement-home discovery views without treating inclusion and exclusion flags as exact complements.
- Let buyers revisit a saved area with a documented 24-hour, 3-day, 7-day or 14-day listing-age filter; do not present it as a complete change feed.
- Prototype map-based sale shortlists using documented coordinate and price fields with graceful fallbacks for absent listing data.
Frequently asked questions
Which location value does the sale search require?
The required identifier is the locationIdentifier from data[] in the auto-complete response. The documented example is REGION^1036. It is a location identifier, not an individual property ID.
How do I combine property types or keywords?
property_type accepts comma-separated values; documented types are Detached, SemiDetached, Terraced, Flat, Bungalow, Land and ParkHome. keywords is also comma-separated, with pool, garden given as an example. Matching and keyword ranking behavior are not specified.
Which added_to_site values are documented?
Use 1 for the last 24 hours, 3 for the last 3 days, 7 for the last 7 days or 14 for the last 14 days. Leaving the value empty means Anytime; the existing empty default is preserved.
Can I combine new-home or buying-scheme inclusion and exclusion flags?
Separate has_* and do_not_show_* parameters exist for these categories, but the documentation does not define precedence or prove that the flags are strict complements. Use deliberate configurations and inspect results instead of assuming conflicting flags cancel each other.
Does the response include verified sale-listing fields?
No observed response was supplied for this endpoint. A truncated documentation example shows currentPage and data rows containing identifiers, address, bedroom and bathroom counts, property type, price, coordinates and image-related fields. Treat these as example fields, not a verified complete schema or availability guarantee.
Are page numbering, sorting codes and radius units defined?
page is an optional number and sort_by is an optional string, but the documentation supplies no page-origin rule or sorting values. search_radius has documented string choices from 0.0 through 40.0; its unit is not stated. Do not infer these details from other endpoints.