Find similar homes for sale by property ID (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Legacy lookup for homes for sale similar to a reference property. Send the required property_id query parameter as a string, using a property_id returned by a property-listing response. This route is explicitly deprecated and should be retained only for reviewing or migrating an existing sale-recommendation workflow. The deprecation notice points to /properties/v2/list... endpoints; it does not establish an equivalent replacement or identical recommendation ranking. No observed probe response or documented response example is available for this operation. Consequently, no response envelope, result-field names, recommendation count, ordering or current availability is verified.
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/realty-in-us/properties-v2-list-similar-homes-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-v2-list-similar-homes-deprecated?key=<API_KEY>&property_id=<property_id>'
Query Result
Use Cases
- Inventory existing for-sale recommendation panels that still call this property_id-based legacy route.
- Trace which property-listing response supplies the reference property_id before changing a sale-recommendation integration.
- Build a migration checklist that compares sale-candidate identifiers, ordering and empty results only after separately verifying a current alternative.
- Mark this deprecated sale-similarity route as legacy-only in developer documentation while keeping its request contract visible.
Frequently asked questions
What does this deprecated operation look up?
Its documented purpose is to list homes for sale similar to a reference property. It is not a general city search or the separate rental-similarity operation.
Where should I get property_id?
Use the property_id field returned by a property-listing response, including documented /properties/list-... or /properties/v2/list-... searches. Send it as a string. The sample identifier is illustrative and does not guarantee an available match.
Can I filter the similar sale results by price or distance?
No such inputs are documented for this route. Its only documented parameter is the required property_id, so do not assume that sale-price, bedroom or radius filters are supported.
Which response fields and ranking are verified?
None are verified for this operation: there is no observed probe response or documented response example in the available evidence. The result envelope, property fields, count, order and empty-result format remain unverified.
Is there a confirmed drop-in replacement?
No. The deprecation notice points to /properties/v2/list... endpoints, but it does not establish a specific equivalent contract or matching ranking. Evaluate an appropriate current operation separately before replacing an existing recommendation panel.