Search residential properties to rent with household filters
View all Rightmove UK Property Search & Sold Prices endpoints →Search rental listings using the required identifier from rental autocomplete data[].locationIdentifier, such as the documented REGION^1036 example. Optional inputs include price and bedroom bounds, comma-separated furnished_type, property_type and keywords, search_radius, page, amenity flags, accommodation inclusion and exclusion flags, added_to_site, sort_by and type_of_let. Furnishing, property-type and radius examples are documented; allowed values for added_to_site, sort_by and type_of_let, price currency and rental period, and interactions between positive and negative accommodation flags are not specified in the supplied parameter facts. No observed probe response is supplied for this operation. An incomplete, unverified source example names currentPage and a data array with listing fields including id, displayAddress, bedrooms, bathrooms, location.latitude, location.longitude, listingUpdate, price and propertyImages. The example price object names amount, currencyCode, frequency and displayPrices entries with displayPrice; propertyImages names an images array. These fields are example-only, not a verified response contract or pagination guarantee. Verify the returned price conventions and accommodation-filter behavior before presenting a relocation shortlist; do not infer live availability or complete inventory.
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 API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/rightmove/property-to-rent?key=<API_KEY>&identifier=REGION%5E1036&search_radius=0.0'
Query Result
Use Cases
- Prepare a household relocation shortlist that combines bedroom bounds and furnishing preferences, labeling rent only after confirming returned currency and period.
- Offer separate house-share, student and retirement rental browse presets while testing inclusion and exclusion flags independently rather than assuming they are complements.
- Build a renter preference form with documented property-type combinations, keyword phrases and radius values while retaining the selected rental location identifier.
- Let a relocation adviser compare garden and parking preferences without treating let-agreed listings as immediately available homes.
- Design a rental-result card around example address, price-frequency and image fields with fallbacks until an actual response establishes field availability.
Frequently asked questions
Which location identifier does rental search require?
Supply identifier from data[].locationIdentifier returned by rental autocomplete. The documented example is REGION^1036. Preserve that complete value rather than converting it into the separate identifier and type inputs used by historical sold-price search.
How do furnishing and property-type combinations work?
The documentation accepts comma-separated strings. Furnishing examples include Furnished,PartFurnished; documented values are Furnished, PartFurnished and Unfurnished. Property-type examples include Detached,SemiDetached, with additional documented values Terraced, Flat, Bungalow, Land, ParkHome and StudentHalls.
Are min_price and max_price monthly rental amounts?
The supplied parameter facts do not specify a currency or rental period, so do not label these bounds as monthly or weekly without verification. The unverified example names price.amount, currencyCode, frequency and displayPrices, but no observed response confirms their availability.
Can I combine inclusion and exclusion flags for the same accommodation type?
The operation exposes both has_* and do_not_show_* flags for house shares, retirement homes and student accommodation. Their precedence and interaction are not documented. Avoid contradictory combinations and validate each browse configuration rather than assuming the flags are exact complements.
Which rental response fields have been verified?
None have been verified by an observed probe for this operation. The incomplete source example names currentPage, data, listing IDs, addresses, bedrooms, bathrooms, coordinates, price information and propertyImages. Handle these as example-only fields, not guaranteed schema or pagination rules.
What values should I use for added_to_site, sort_by and type_of_let?
These optional string parameters are exposed but their supported values are not specified in the supplied facts. Leave them unset until their accepted values are established; do not reuse sort values from sold-price search.
Does including let-agreed properties confirm current availability?
No. has_include_let_agreed is an optional visibility flag whose detailed behavior is not verified here. A returned record is not a promise of immediate rental availability or complete market coverage.