Find similar properties by property ID (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Retrieve suggested similar properties through a deprecated listing route. All three query parameters are required: property_id is the numeric property identifier from property-list results, prop_status selects for_sale or for_rent, and limit specifies the requested number of suggestions. These are recommendation candidates, not a verified set of completed-sale comparables or an appraisal. No probe response was recorded for this operation. The supplied legacy response example is truncated and unverified, so its fields document an example rather than a guaranteed current schema. It shows results.similar_homes.count and results.similar_homes.properties. Example property entries contain property_id, listing_id, status, list_price, list_date, last_update_date, location, photos, and primary_photo. The description object includes beds, baths, sqft, lot_sqft, type, and year_built; additional_info includes display values and comparison fields such as compared_price_diff and compared_sqft_diff. Price fields including last_sold_price can be null. Do not infer an exact ranking formula, equal coverage with newer routes, or a confirmed sale price from these example fields. Check identifier mapping and missing-field handling when replacing an older recommendation widget.
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-list-similarities-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-list-similarities-deprecated?key=<API_KEY>&limit=<limit>&prop_status=for_sale&property_id=<property_id>'
Query Result
Use Cases
- Inventory the property_id, prop_status, and limit inputs used by an older related-homes carousel before replacing its data source.
- Keep sale and rental suggestion panels distinct when documenting a legacy recommendation integration.
- Compare a saved set of suggested property identifiers with a replacement recommendation response without assuming identical ordering or coverage.
- Test a recommendation-card adapter against absent photos, null historical prices, and legacy additional_info display fields.
Frequently asked questions
Which inputs are required for the legacy similar-properties lookup?
property_id, prop_status, and limit are all required query parameters. This route declares property_id as a number; the documented example is 3109292331. Use a property identifier from listing results rather than a listing_id.
Which property statuses can I request?
The documented prop_status values are for_sale and for_rent. The value scopes the recommendation request; there is no documented sold status for this operation.
Are these suggestions verified sold comparables?
No. This is a similar-property recommendation route. Example comparison fields such as compared_price_diff do not establish a completed transaction, a valuation, or an appraisal-quality comparable set.
Where does the example place the suggested properties?
The unverified legacy example places them in results.similar_homes.properties with a sibling count field. Example entries include identifiers, listing status and price, location, photos, physical attributes, and additional_info comparison values. No probe response confirms the current shape.
Will a replacement route return the same suggestions?
That is not established. This route is deprecated, and no successful probe was recorded. During migration, compare reference identifiers, status selection, candidate identities, ordering, and null handling rather than assuming identical recommendations.