Retrieve deprecated property details using paired listing identifiers

View all Realty in US Property & Mortgage Data endpoints →

Legacy property-detail route retained for compatibility and migration work, not recommended for new integrations. It requires all three query strings: listing_id, property_id, and prop_status. The documented identifier sources are listing_id and property_id fields from property-listing search results, including the legacy list and version-2 list routes. Use the listing and property identifiers belonging to the same search result; they are distinct values and must not be substituted for each other. The documented prop_status choices are for_sale and for_rent. Examples such as listing_id=608763437 and property_id=4599450556 are illustrative, not verified current records. No recorded request to this operation is included, so availability, identifier validity, and the current response contract are unverified. The incomplete source example has a top-level listing object. Its address section shows city, county, state, state_code, postal_code, line, lat, long, neighborhood_name, neighborhoods, and time_zone. Other visible listing fields include beds, baths, baths_full, advertiser_type, agent, branding, broker, client_display_flags, client_display_text, client_event_data, and client_provider_data. These are documentation-example fields only; do not promise their current presence, completeness, or equivalence to a newer detail response. For migration, inventory stored identifier pairs and status values, then separately confirm the input and output contract of the current detail operation before changing links or field mappings. Deprecation does not establish a removal date or guarantee continued service.

API Features

Paired listing and property identifiers Require listing_id and property_id from the same listing-search record, preserving their separate meanings rather than using one identifier in both positions.
Sale-or-rental legacy status selector Set the documented prop_status value to for_sale or for_rent so the legacy request retains the status context associated with its identifier pair.
Documented legacy listing envelope The unverified, incomplete example nests address information and fields such as beds, baths, and baths_full under listing; current field availability is not established.
Stored-link compatibility auditing Use the three-input contract to inventory older links and data records before selecting verified mappings to a current detail interface.
Deprecation-aware migration boundary Treat the route as a legacy compatibility surface without promising continued availability, a removal date, or field-for-field compatibility with newer responses.

Live API Demo

GET /api/project/realty-in-us/properties-detail-deprecated

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-detail-deprecated?key=<API_KEY>&listing_id=<listing_id>&prop_status=for_sale&property_id=<property_id>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Should a new application use this property-detail route?

No. This operation is explicitly deprecated and is retained for legacy compatibility and migration work. Use a current detail operation for new work after checking its own input and response contract.

Do I need both listing_id and property_id?

Yes. Both strings are required, along with prop_status. Obtain the two identifiers from the same property-listing search result; the documentation points to legacy and version-2 list results. Do not reuse one value as the other identifier.

Which prop_status values are documented?

The documented choices are for_sale and for_rent. Use the status associated with the listing record rather than inferring it from an identifier. No request was recorded to verify either status with current records.

Are the sample identifiers guaranteed to return a property?

No. The sample listing and property identifiers are documentation examples, not verified current records. Retrieve a matching pair from an appropriate listing result rather than treating placeholders as known working properties.

Which response fields are confirmed for this deprecated operation?

None were confirmed by a recorded request. An incomplete source example shows listing.address, beds, baths, baths_full, advertiser_type, agent, branding, broker, and client-related sections. Their current presence and completeness remain unverified.

Can I migrate by only replacing the detail URL?

Do not assume so. First inventory the stored listing_id, property_id, and prop_status values, then confirm the current detail operation's required identifiers and field paths. Deprecation does not prove matching response layouts or provide a removal date.

Related operations

Guides

View Subscription Plans →