Get US property details by property ID
View all Realty in US Property & Mortgage Data endpoints →Retrieve a selected US home using the required property_id from property search. An optional listing_id can carry the listing context returned by search; it does not replace property_id. Both inputs are query strings. The successful observed response used data.home and returned property_id, listing_id, list_price, last_update_date, address information, description text and photos. The checked home had a list_price of 1325000 and 75 photos; these are observations for one record, not required values or guaranteed media coverage. Treat last_update_date as the returned record timestamp, not a guarantee of feed-wide freshness. Inspect the response body as well as the HTTP status. An observed invalid property_id returned HTTP 200 with data.home=null and an errors entry containing extensions.code=HTTP_ERROR and extensions.data.code=500. Do not treat every HTTP 200 as a found home or every null home as a clean not-found result. The endpoint documentation mentions a Home Value feature, but the supplied successful observation does not establish valuation field names, an automated valuation model, or a historical value series. The retained source example is truncated and listing-oriented; it is unverified and should not override the observed data.home response shape.
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-detail API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-v3-detail?key=<API_KEY>&property_id=<property_id>'
Query Result
Use Cases
- Populate a selected-home detail page from a property_id discovered in property search.
- Carry an available listing_id into a detail request and display both returned identifiers for record correlation.
- Present the returned asking price beside its record update timestamp, with missing-field handling.
- Detect unresolved-home responses by checking data.home and errors even when the HTTP status is 200.
Frequently asked questions
Where do property_id and listing_id come from?
Use the property_id returned by a property-list operation. It is required here. If the selected search result also provides listing_id, pass it as the optional listing context; listing_id cannot replace property_id.
Where are the property details in a successful response?
The verified success placed the home under data.home, including property_id, listing_id, list_price, last_update_date, address information, description text and photos. That observation does not guarantee every property supplies every item.
Does HTTP 200 mean the requested home was found?
No. An invalid property_id produced HTTP 200 with data.home=null and errors containing extensions.code=HTTP_ERROR and extensions.data.code=500. Check both the home value and the error array before rendering a successful detail page.
Can I rely on this endpoint for an automated home valuation?
Not from the supplied evidence. Home Value is mentioned in the endpoint documentation, but the successful observation did not establish valuation fields, their interpretation, or a historical valuation series. Verify those fields before offering a valuation feature.
Does last_update_date guarantee that the entire listing feed is current?
No. It is a timestamp returned for the individual record. The observed value does not establish a refresh schedule, a maximum age, or completeness across all US listings.