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

Selected sale-record lookup Use the required id query input to request one sale detail record rather than submitting the full discovery filter set again.
Structured sale address example The documented data.address object includes displayAddress, incode, outcode, countryCode and ukCountry, with deliveryPointId null in the supplied example.
Detailed housing and room attributes The source example includes bedrooms, bathrooms and affordableBuyingScheme alongside businessForSale, channel and commercial fields; coverage is unverified.
Broadband reference fields The visible broadband object contains broadbandCheckerUrl and disclaimer. Treat them as documented references, not measured connection speeds.
Agency and developer context Example customer fields include branch and company names, isNewHomeDeveloper and developmentInfo for a richer selected-listing view.
Unknown-aware detail rendering Distinguish missing fields, null values and empty arrays when presenting a sale record; the incomplete example does not prove a fixed complete schema.

Live API Demo

GET /api/project/rightmove/property-for-sale-detail

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/rightmove/property-for-sale-detail?key=<API_KEY>&id=<id>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →