Search sold properties with legacy filters and paging (deprecated)

View all Realty in US Property & Mortgage Data endpoints →

Deprecated sold-property search with required city, state_code, limit and offset query parameters. Use city and state_code strings from location autocomplete results; limit is a numeric requested page size and offset is a numeric count of records to skip. Optional numeric filters cover home age, minimum bedrooms and bathrooms, price, building size, lot size, geographic bounds and a radius of 1 to 20 miles. prop_type accepts documented property-type values, comma-separated for multiple types; sort accepts sold_date, beds_high, price_low, price_high or lot_sqft_high. The location documentation is internally constrained: postal_code must not be combined with city/state_code, but city/state_code remain required in this retained contract. Coordinate bounds are documented as ineffective whenever postal_code, city or state_code has a value; do not promise a postal-only or bounding-box-only request. No observed probe response is available. An unverified, truncated source example shows meta.matching_rows and meta.returned_rows, plus a properties array with property_id, listing_id, prop_status, prop_type, price, beds, baths, baths_full and nullable baths_half. It also shows address fields including line, city, state_code, postal_code, lat and lon; building_size and lot_size objects with size and units; photo_count, photos, list_date and last_update. These are source-example fields, not a verified response schema or a guarantee of current availability. The example does not establish that price is a completed sale price or that list_date is a closing date. Retain this endpoint for legacy migration review and independently verify sold status and transaction fields before valuation use.

API Features

City-state sold shortlist The retained request requires city and state_code from location autocomplete, alongside numeric limit and offset paging inputs.
Legacy age and room filters Optional age_min, age_max, beds_min and baths_min preserve documented home-age, bedroom and bathroom criteria when auditing an older sold-property shortlist.
Price, building and lot ranges Separate minimum and maximum parameters cover price, building size and lot size; the response example represents building_size and lot_size with explicit size and units fields.
Documented sold sorting choices The sort choices are sold_date, beds_high, price_low, price_high and lot_sqft_high. The example sold_date value is not an independently verified ordering guarantee.
Conflicting geographic modes exposed Postal-code exclusivity and inactive coordinate bounds are documented alongside required city/state_code inputs, so incompatible location modes are not advertised as interchangeable.
Source-only sold response map A truncated source example supplies count, identifier, address and property-attribute field names, but no live result verifies their availability or the meaning of a completed transaction price.

Live API Demo

GET /api/project/realty-in-us/properties-v2-list-sold-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-v2-list-sold-deprecated?key=<API_KEY>&city=<city>&limit=<limit>&offset=<offset>&state_code=<state_code>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Which parameters are required for this sold-property search?

The retained contract requires city and state_code as strings and limit and offset as numbers. City and state_code are documented as values from location autocomplete. The examples use a page size of 200 and an offset of 0; these are examples, not documented defaults or maximums.

Can I search using only a postal code or bounding box?

That is not supported by the retained required-input contract. The documentation says not to combine postal_code with city/state_code, yet city/state_code are required. It also says coordinate bounds have no effect when any of postal_code, city or state_code has a value. Do not assume these optional fields bypass the required city-state inputs.

What property types and sort values are documented?

prop_type accepts single_family, multi_family, condo, mobile, land, farm and other, with multiple values separated by commas. sort accepts sold_date, beds_high, price_low, price_high and lot_sqft_high. No other values are established by the available documentation.

Which response fields have been observed live?

None for this operation. An unverified, truncated source example shows meta.matching_rows, meta.returned_rows and properties with identifiers, status/type, price, room counts, address data, building_size, lot_size, photo fields and listing/update dates. These names do not establish a complete or currently available response schema.

Does the price field prove the completed sale amount?

No. The source example contains price and prop_status but does not establish completed transaction amounts. Likewise, list_date is not proof of a closing date. Verify sold status and transaction fields independently before treating results as valuation comparables.

How do the size and radius filters work?

sqft_min and sqft_max describe property-size limits, while lot_sqft_min and lot_sqft_max describe lot or acreage-size limits. The brief input descriptions do not fully define area units. radius is explicitly documented in miles from 1 to 20, but its interaction with the conflicting location modes is not verified.

Should I build a new sold-home integration around this route?

No. It is marked deprecated and is best retained for auditing existing requests and planning migration. Evaluate a current search operation separately and verify its filters, pagination and sold-property response semantics rather than assuming a drop-in replacement.

Related operations

Guides

View Subscription Plans →