Get Legacy Property Details (Deprecated)
View All Realtor Property Data APIs →Legacy detail read requiring both propertyId and listingId from the same search row. This documented route is deprecated and was not live-tested; response fields and continued availability are unconfirmed. It remains in the reference for existing integrations, not as a new quick-start recommendation. New development should use property-v2-detail with a freshly obtained property_id. Compare actual field availability before migrating and preserve the distinction between a property identity and its listing identity.
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/realtor/property-detail-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realtor/property-detail-deprecated?key=<API_KEY>&propertyId=<propertyId>&listingId=<listingId>'
Query Result
Use Cases
- Maintain a preexisting dual-ID detail integration while evaluating its current availability.
- Plan a migration test from legacy ID pairs to the tested v2 query contract.
- Compare required fields before retiring an older property-detail client.
- Identify stored records with mismatched property and listing IDs during a legacy-data cleanup.
Frequently asked questions
Should new integrations start with the legacy detail operation?
No. This operation is deprecated and was not live-tested. Prefer property-v2-detail for new development using property_id from a current search.
Can the legacy propertyId and listingId come from different records?
No. Both must come from the same search listing. Mixing them risks an incorrect association, and behavior for outdated pairs is also unconfirmed.
Can I migrate to version two without checking fields?
No. No legacy response was observed. Compare actual field availability, nulls and business dependencies before replacing parsing, and change the dual-ID input to the version-two query contract.