Search sold property listings with legacy filters (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Search sold-home listing records through a deprecated route. The request contract requires city, state_code, limit, and offset. Optional filters cover price, home age, property size, lot size, property type, radius in miles, postal code, coordinate bounds, and sort order. prop_type accepts comma-separated documented values: single_family, condo, mobile, multi_family, farm, and land. offset is the number of items to skip for pagination, not a page number. The location documentation has important limitations: it says not to combine postal_code with city or state_code, and says coordinate bounds have no effect when postal_code, city, or state_code has a value. Because city and state_code remain required in this request contract, neither postal-only nor bounds-only search is established as usable here. Preserve these constraints rather than silently dropping required inputs. The sort description lists price_low and price_high, while its documented example is relevance; acceptance of that example has not been verified. No maximum limit or complete ordering behavior is documented. No probe response was recorded for this operation. The supplied source example is truncated and unverified. Its visible listings array contains property_id, listing_id, prop_status, prop_type, sold_date, list_date, last_update, address, structured address_new data, coordinates, beds, baths, photo, and photo_count. It also distinguishes formatted price and sqft values from price_raw and sqft_raw. These example fields are not a guaranteed current schema. Neither the price filters nor price_raw alone establish a verified closing price. Record request dates and candidate identifiers when auditing or migrating historical sold-home queries.
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-list-sold-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-list-sold-deprecated?key=<API_KEY>&city=<city>&limit=<limit>&offset=<offset>&state_code=<state_code>'
Query Result
Use Cases
- Audit a saved city-and-state sold-home query, including price, home-age, lot-size, and floor-area filters, before changing the integration.
- Reproduce legacy sold-listing pagination by recording the request date, limit, offset, and selected property and listing identifiers.
- Review an older map-search form for ineffective coordinate bounds when its requests also supply required city and state values.
- Migrate sold-result tables that display sold_date, formatted price, and square footage while keeping raw values distinct and avoiding verified-closing-price claims.
- Test documented property-type combinations and price sort values separately from the unverified relevance example during a sold-search migration.
Frequently asked questions
Which inputs are required for this deprecated sold-home search?
city, state_code, limit, and offset are required. The documented examples are New York City, NY, 200, and 0 respectively. Optional filters do not remove those requirements.
Can I use only a postal code or a bounding box?
That behavior is not established by this contract. The location notes say not to combine postal_code with city or state_code, and say coordinate bounds are ignored when any of those location fields has a value. Because city and state_code are required here, do not assume postal-only or bounds-only requests are supported.
How do limit and offset control pagination?
limit is the requested number of records and offset is the number of records to skip. For example, offset 0 starts without skipping records; it is not page 0. No maximum limit, stable ordering guarantee, or complete-result guarantee is provided.
Which property types and sort values are documented?
prop_type supports single_family, condo, mobile, multi_family, farm, and land, with commas for multiple types. The sort description lists price_low and price_high. Its separate example is relevance, but no probe confirms that example's acceptance.
Does a returned price represent the verified sale amount?
Not necessarily. The unverified legacy example includes price, price_raw, and sold_date, but it does not establish that price or the price filters are verified transaction amounts. Keep listing prices separate from any independently verified closing-price data.
Which sold-listing response fields have been observed live?
None in the supplied evidence: no probe response was recorded. The truncated source example shows a listings array with identifiers, address data, status, property type, dates, beds, baths, photos, price fields, and size fields. Treat these as example-only fields when designing a migration adapter.