Get residential rental listing details by ID
View all Rightmove UK Property Search & Sold Prices endpoints →Retrieve the detail record for a residential rental listing using the required query parameter id. Use an ID from property-to-rent search and send it as a string. The documented default, 135161867, is an example listing ID, not a promise that the listing remains available. Do not assume sales, commercial or student-rental identifiers work with this operation. The documented success example contains a data object with address fields countryCode, deliveryPointId, displayAddress, incode, outcode and ukCountry, plus numeric bedrooms and bathrooms, a string channel and a boolean commercial flag. It also shows broadband with broadbandCheckerUrl and disclaimer, a brochures array, contactInfo with contactMethod and telephoneNumbers, and a customer object with branchDisplayName, branchId, branchName and companyName. The example includes nullable values and an empty brochures array; brochure-item content is not established. No live probe response was recorded for this operation. These response fields come from a truncated documentation example, not an observed response contract; the complete schema and field availability are unverified. Do not infer current tenancy availability, rent or fees, eligibility, viewing appointments or booking support from the example.
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-to-rent-detail API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/property-to-rent-detail?key=<API_KEY>&id=135161867'
Query Result
Use Cases
- Open a residential-rental shortlist drawer after a renter selects a search result, requesting detail only for that listing.
- Refresh a relocation adviser's chosen rental record before sharing a viewing shortlist, recording retrieval time without claiming it confirms availability.
- Populate a tenant comparison card with the documented address and room-count fields when returned, leaving absent values unknown.
- Route a letting-branch review task from returned customer metadata without treating the lookup as a viewing booking.
Frequently asked questions
Where should the rental listing id come from?
Use the id from property-to-rent search and pass it as a string in the required id query parameter. The documented default is 135161867. The search-to-detail handoff has not been live-verified here, and IDs from other listing channels are not established as compatible.
Which rental detail fields are documented?
A truncated success example shows data.address, bedrooms, bathrooms, channel, commercial, broadband, brochures, contactInfo and customer. Address and customer have nested fields, including displayAddress and branchDisplayName. There is no saved live probe response for this operation, so these are example fields rather than guaranteed output.
Does the detail lookup confirm the current rent or availability?
No. The supplied evidence does not establish current rent, fees, tenancy eligibility or availability. Check what the actual response provides and keep unavailable fields unknown instead of treating the example ID as an available rental.
Can this endpoint book a viewing or start a tenancy?
No such action is documented. This GET operation retrieves a rental detail record by id; contactInfo or customer fields, if returned, do not mean a viewing or tenancy has been arranged.