Find possible alternatives to a selected property

View all Rightmove UK Property Search & Sold Prices endpoints →

Request similar-property suggestions using the required string query parameter id. The documentation names property-for-sale/new-homes-for-sale as the source of that listing ID and supplies 86104788 as both the example and default. No location, price, bedroom, radius, sort or pagination parameters are declared for this operation. The supplied, truncated documentation example shows a data array with visible item fields bathrooms, bedrooms, detailsUrl, displayAddress, displayPrice, displayPriceQualifier, hasFloorplan, hasVirtualTour, id and images. In the visible example, room counts are integers, id and displayPrice are strings, media-presence flags are booleans and displayPriceQualifier is null; image objects have caption and url fields. These are unverified example fields, not an observed response or a complete guaranteed schema. No live probe response was supplied for this endpoint. Similarity criteria, ranking, result count and cross-listing ID compatibility remain unverified. Present results as possible alternatives and independently check suitability; they are not guaranteed to match a prior search budget or geography and are not sold-price valuation comparables.

API Features

Listing-seeded alternative discovery Request suggestions from one required property id, with property-for-sale/new-homes-for-sale named as the documented ID source.
Suggestion-card display fields The source example includes displayAddress, bedrooms, bathrooms and displayPrice for proposed alternative-listing cards; no observed contract is supplied.
Alternative detail references Documented suggestion items expose id and detailsUrl fields. Their compatibility with other detail operations has not been verified.
Floorplan and tour indicators The visible source example includes hasFloorplan and hasVirtualTour booleans, which indicate media-related fields rather than supplying the media themselves.
Captioned recommendation images The incomplete documentation example shows an images array with caption and url fields for alternative-property imagery.
Explicit similarity boundaries Keep recommendations separate from filtered search results because the matching criteria, geographic scope and price alignment are not documented.

Live API Demo

GET /api/project/rightmove/similar-to-property

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/similar-to-property?key=<API_KEY>&id=86104788'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Which ID should seed a similar-property request?

Use the required string id. The documentation identifies property-for-sale/new-homes-for-sale as the listing-ID source and provides 86104788 as the example and default. It does not call for an auto-complete location identifier. Compatibility with IDs from other operations is not verified.

Do similar-property results retain my original budget, location or bedroom filters?

That is not guaranteed. This operation declares only id and does not accept the original search filters. The supplied evidence does not define similarity criteria, so validate each alternative against your own requirements.

Are these properties sold-price comparables or valuations?

No valuation or completed-sale comparison contract is documented. Use the results for possible listing alternatives and discovery, not as proof of comparable sold values or as an automated valuation.

Which fields can an alternative-property card use?

The truncated source example shows a data array with bathrooms, bedrooms, detailsUrl, displayAddress, displayPrice, displayPriceQualifier, hasFloorplan, hasVirtualTour, id and images. Image objects show caption and url. No live probe response was supplied for this operation, so these are example fields rather than verified required fields.

Is displayPrice a numeric amount suitable for price calculations?

The visible example represents displayPrice as a string and displayPriceQualifier as null. No numeric amount field is shown in the supplied evidence for this endpoint. Do not substitute the separate sale-search price schema or silently treat display text as a standardized numeric price.

Can I set a recommendation limit, page or ranking rule?

No such parameters are declared for this operation; only id is supported. The documentation does not establish recommendation count, ordering rules or pagination, so the interface should not promise configurable ranking or exhaustive alternatives.

Related operations

Guides

View Subscription Plans →