Look up legacy v2 property details (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Retrieve property detail information through the deprecated v2 detail route. Its sole documented input is the required property_id query parameter, declared as a string and obtained from property-list results. Preserve the identifier exactly: the documented example is O3599084026, with a leading letter, so numeric coercion can change the request. This operation does not document an address, listing_id, or geographic search input. No probe response was recorded for this operation. The supplied legacy example is truncated and unverified; it is not evidence of current availability or a complete response contract. The visible example has a meta object with matching_rows, returned_rows, and schema, plus a properties array. Its visible property fields include a structured address with coordinates, postal and state codes, neighborhood information, and time_zone; beds, baths, baths_full; building_size.size and building_size.units; description; and nested agents, broker, buyer_agent_for_far, and buyer_office objects. Optional attributes such as cooling and heating are null in the visible example. When migrating property-detail pages or cached records, keep this array-based example shape distinct from any replacement response. Do not assume a single top-level property object, complete field coverage, stable nesting, or interchangeable schemas. Handle a retrieval failure separately from a missing or null attribute, and validate identifier preservation and field mapping explicitly.
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-v2-detail-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-v2-detail-deprecated?key=<API_KEY>&property_id=<property_id>'
Query Result
Use Cases
- Inventory property_id-only detail links and cached v2 payloads in an older residential property portal.
- Test a detail-page request builder with the letter-prefixed O3599084026 example to detect destructive numeric conversion.
- Build a field-mapping checklist for legacy address, neighborhood, room-count, building-size, and representative objects before replacing a detail route.
- Separate retrieval failures from missing fields and null heating or cooling attributes in a property-detail migration adapter.
- Compare an archived properties-array parser with a replacement detail response without assuming matching envelope or nesting conventions.
Frequently asked questions
Is property_id a number in this v2 detail operation?
No. This operation declares property_id as a required string. The documented example O3599084026 begins with a letter. Preserve the exact value from listing results instead of converting it to a number or substituting listing_id.
Can I look up the property by address or coordinates instead?
Not through the documented request for this operation. property_id is its only query parameter; address, coordinates, and listing_id are not documented inputs.
Does the legacy example return a single property object?
The unverified source example shows a properties array and a meta object with matching_rows and returned_rows. It does not establish that a successful response always contains one record, and no probe response confirms its current envelope.
Which property details are visible in the supplied example?
The truncated legacy example includes structured address and neighborhood data, beds, baths, baths_full, building_size with size and units, description, and nested representative objects. Heating and cooling are null in the visible sample. These are example-only fields, not guaranteed live output.
Can a newer detail response be used without changing the parser?
Schema compatibility is not established. This route is deprecated and has no recorded probe response. Compare array handling, field paths, identifier types, size units, and missing or null values, and treat retrieval errors separately from attribute absence.