Find similar homes for a selected property
View all Realty in US Property & Mortgage Data endpoints →Request similar-home candidates with GET /properties/v3/list-similar-homes. Supply the required property_id query string from the property_id field of a property-list result, not its listing_id. The optional status query string accepts one documented value: for_sale, ready_to_build, for_rent, sold, off_market, other or new_community. The optional numeric limit controls the number of items per response; 10 is the documented example, not a verified default or maximum. Only limit is exposed for response sizing on this route; no offset, page number or cursor input is documented. There is no successful response probe or source response example in the supplied evidence. Consequently, the response envelope, candidate field names, actual result count, similarity criteria, ranking and geographic scope have not been verified. Present any returned homes as suggested alternatives, verify their geography, status and property attributes before comparison, and do not treat this operation as a comparable-sales appraisal or valuation.
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-v3-list-similar-homes API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-v3-list-similar-homes?key=<API_KEY>&property_id=<property_id>'
Query Result
Use Cases
- Place a limited "Similar homes" panel beside a selected property using its property_id and an explicit for_sale status.
- Offer a related-rental browsing path with the documented for_rent status after validating that status against returned candidates.
- Explore suggested sold-home candidates with status sold, checking location and home attributes before making any manual price comparison.
- Keep a property-detail recommendation module small by setting limit explicitly, without inventing offset or cursor paging controls.
- Let a user switch a related-home request to ready_to_build or new_community while clearly labeling the output as suggestions rather than guaranteed comparable properties.
Frequently asked questions
How do I select the reference home for similar results?
Pass its property_id from a property-list result as the required property_id query string. The operation does not document accepting listing_id or a street address in place of that identifier.
Which status values are documented for similar-home requests?
The optional status string accepts one of for_sale, ready_to_build, for_rent, sold, off_market, other or new_community. The example is for_sale. These are documented values, not successfully probed combinations, and array or comma-separated status syntax is not documented.
Does limit 10 guarantee ten candidates or represent a default?
No. 10 is the supplied example for the optional numeric limit. The evidence does not verify a default, maximum or guaranteed candidate count. No offset, page-number or cursor request parameter is documented for this route.
What fields and similarity scores are returned?
No successful probe or response example was supplied, so candidate fields, envelope structure, similarity scores, ordering and geographic scope remain unverified. Validate the actual response before designing a fixed recommendation-card schema.
Can sold similar homes be used as a verified appraisal?
No. The documented sold status can be used to request suggested candidates, but similarity criteria and comparability have not been established. Check geography, sale status, property attributes and relevant dates independently before comparing prices.