Search new homes for sale by location and buyer preferences
View all Rightmove UK Property Search & Sold Prices endpoints →Search the new-homes-for-sale collection with a required identifier location reference. The parameter documentation directs callers to locationIdentifier in a selected auto-complete data item and gives REGION^1036 as an example. Optional inputs cover numeric price and bedroom bounds, numeric page, string search_radius, comma-separated keywords and property_type, added_to_site, sort_by, and boolean flags for garden, parking, auction properties, buying schemes, retirement homes and inclusion of under-offer or sold-STC listings. The permitted values of added_to_site and sort_by, the page base, and flag precedence are not documented. This operation was not included in the observed probe. Its unverified, incomplete source response example begins with currentPage and a data array; the visible listing fields include id, displayAddress, bedrooms, bathrooms, addedOrReduced, auction, channel, price.amount, price.currencyCode, price.displayPrices, location.latitude, location.longitude, listingUpdate and propertyImages.images. These are example fields rather than a verified complete schema. Do not borrow pagination totals, freshness guarantees or response requirements from another search operation.
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/new-homes-for-sale API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/new-homes-for-sale?key=<API_KEY>&identifier=<identifier>'
Query Result
Use Cases
- Build a new-build discovery tab where buyers combine a selected location with budget, bedroom and property-form filters.
- Prepare a family-home shortlist using garden and parking preferences alongside the buyer bedroom range.
- Create a new-home research queue with added_to_site after confirming its accepted values, keeping it separate from resale monitoring.
- Let buyers review buying-scheme and retirement-home preferences as distinct flags, avoiding conflicting settings until their behavior is validated.
- Offer a controlled radius comparison for new-home searches using the documented radius choices rather than inventing distance values or units.
Frequently asked questions
Where does the required identifier come from?
The parameter documentation points to locationIdentifier in a selected data item from auto-complete. REGION^1036 is the documented example. Inspect the selected suggestion and validate the reference before using it for a new-home search.
How do I send property types and keywords?
Both are optional comma-separated strings. Documented property types are Detached, SemiDetached, Terraced, Flat, Bungalow, Land and ParkHome; Detached,SemiDetached is the example combination. The documented keyword example is pool, garden.
Which search_radius values are documented?
The documented string values are 0.0, 0.25, 0.5, 1.0, 3.0, 5.0, 10.0, 15.0, 20.0, 30.0 and 40.0. No distance unit is specified in the supplied parameter documentation, so do not assume or relabel the unit.
Are page numbering, sort order and added-to-site values defined?
page is an optional number, while sort_by and added_to_site are optional strings. Their page base and accepted string values are not documented. Leave them unset unless you have validated the values required by your application.
Can buying-scheme and retirement flags be combined freely?
Separate inclusion-style and exclusion-style flags are exposed for buying schemes and retirement homes, but defaults and precedence are not documented. Avoid conflicting combinations and validate each intended combination before making it a saved-search setting.
Which response fields were verified for this search?
This operation was not part of the observed probe. The incomplete source example shows currentPage and a data array with visible listing identifiers, address, bedroom and bathroom counts, price, coordinates, update information and image structures. Treat these as unverified example fields, not a complete or guaranteed response contract.