Retrieve details for one selected new-home listing
View all Rightmove UK Property Search & Sold Prices endpoints →Look up one new-home-for-sale record using the required id query string. The documentation specifies an id from new-homes-for-sale and gives 129254912 as an example; it is a listing identifier, not the location identifier used for area searches. This detail operation accepts no documented search filters. It was not included in the observed probe. The unverified, incomplete source response example shows a data object with address fields including displayAddress, countryCode, incode, outcode and ukCountry; bedrooms; a nullable bathrooms value; affordableBuyingScheme; channel; contactInfo; and a customer object. The visible customer fields include branchDisplayName, branchId, branchName, companyName, companyTradingName, developmentInfo and isNewHomeDeveloper, with developmentInfo containing sitePlanUri and micrositeFeatures. These are visible example attributes, not a verified exhaustive schema or a guarantee that every record includes them. Inspect the actual returned structure before rendering a detail view, and do not infer current availability, a complete development inventory or undocumented price and image fields from another endpoint.
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-detail API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/new-homes-for-sale-detail?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Open a comparison drawer only after a buyer selects a new-home search result, requesting details for that listing rather than every result.
- Refresh one shortlisted new-home record before assembling a buyer research pack, retaining the requested ID and retrieval time without claiming availability.
- Prototype a detail card with address and bedroom information, providing an unavailable state for the example nullable bathrooms field.
- Review returned branch and developer context for a selected listing before deciding whether a development-information section can be shown.
Frequently asked questions
Where should the id value come from?
Use a listing id from new-homes-for-sale. The documented example is 129254912, passed as a string. It is not an auto-complete location reference such as REGION^1036.
Can I filter by location, price or bedrooms in this detail request?
No such filters are documented here. This operation has only the required id query parameter. Apply location and buyer filters in new-homes-for-sale, then request a selected listing by ID.
What address and room information does the example contain?
The unverified example shows data.address with displayAddress, countryCode, incode, outcode and ukCountry, along with bedrooms and a null bathrooms value. The example is incomplete and does not establish that these fields appear in every response.
Does the example include developer information?
Its customer object includes branch and company fields, isNewHomeDeveloper and developmentInfo. The visible developmentInfo fields include sitePlanUri and micrositeFeatures. Validate their actual presence and values before using them in a detail layout.
Was this endpoint response verified in the observed probe?
No. This operation has no observed probe call in the supplied evidence. Its response description is based only on a partial, unverified source example; a successful probe of another endpoint does not verify this detail response.
Does a detail record prove a home is still available or describe an entire development?
No current-availability or complete-development guarantee is documented. Treat this as a lookup for one selected listing, retain the retrieval context for research, and verify any time-sensitive conclusions independently.