Look up a residential sale listing by property ID
View all Rightmove UK Property Search & Sold Prices endpoints →Retrieve the detail record for a sale listing using the required string query parameter id. The documented source for this identifier is the property-for-sale endpoint; retain the returned listing ID as a string and validate that search-to-detail mapping in your integration. The supplied, truncated documentation example begins with a data object. Visible detail fields include address.countryCode, address.displayAddress, address.incode, address.outcode and address.ukCountry, along with bedrooms, bathrooms, affordableBuyingScheme, businessForSale, channel and commercial. It also shows broadband.broadbandCheckerUrl and broadband.disclaimer; a brochures array; a commercialUseClasses array; contactInfo.contactMethod and contactInfo.telephoneNumbers; and customer fields such as branchDisplayName, branchId, branchName, companyName, companyTradingName, isNewHomeDeveloper and developmentInfo. The example has null values for address.deliveryPointId, auctionProvider and countryGuide, and empty brochures and commercialUseClasses arrays, which do not establish permanent absence. These fields come from an unverified, incomplete source example, not an observed response for this endpoint. No live probe response was supplied for this operation, and the full detail schema, update timing and missing-ID behavior 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-detail API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/property-for-sale-detail?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Open an on-demand buyer detail panel after a user selects a sale search result, with the search-to-detail ID mapping checked during integration.
- Refresh selected sale records before preparing a viewing shortlist and store the retrieval time without claiming that it is the listing update time.
- Enrich a saved buyer record with postcode components and room counts when those documented fields are available.
- Present a broadband reference and its disclaimer on an individual sale-detail screen without turning the reference into a speed guarantee.
- Show branch or developer context for a chosen sale listing while preserving null and absent attributes as unknown.
Frequently asked questions
Where does the required sale-detail id come from?
The documentation specifies an id from the property-for-sale endpoint. Send it in the required string query parameter id; 126451514 is the documented placeholder. Validate the mapping from a selected search record before relying on it.
What response structure is documented for this detail endpoint?
The supplied source example starts with a data object containing an address object, bedroom and bathroom counts, housing flags, broadband references, contactInfo and customer details. The example is truncated and was not confirmed by a live probe for this endpoint, so it is not a complete verified response contract.
Do broadband fields report a verified connection speed?
No. The visible broadband object contains broadbandCheckerUrl and disclaimer. The supplied evidence does not document measured speed fields or establish broadband availability for a property.
Do null values or empty brochures mean that a property has no such information?
Not necessarily. The example shows null values such as auctionProvider and countryGuide and empty arrays such as brochures. Preserve these states as unknown or not supplied; one example does not establish a negative property feature or a permanent absence.
Can a successful detail request prove that a listing is current or still available?
No freshness or availability guarantee is documented, and no observed response was supplied for this operation. Record your own retrieval time and avoid treating a returned detail record as proof of current sale availability.
How should the application handle an unknown or removed property ID?
The supplied documentation does not specify missing-ID or removed-listing behavior. Handle unsuccessful responses and absent detail data defensively instead of assuming a particular error code or transferring another endpoint's behavior.