Search homes for sale with legacy filters (deprecated)

View all Realty in US Property & Mortgage Data endpoints →

Deprecated for-sale property search for maintaining older buyer-search forms and auditing saved-search migrations. city, state_code, limit, and offset are required by the legacy schema; city and state_code are described as location-autocomplete values. postal_code is documented as an alternative that must not be combined with city and state_code, which conflicts with their requiredness in this contract; postal-only behavior is unverified. The four bounding-box parameters lat_min, lat_max, lng_min, and lng_max are documented as ineffective whenever postal_code, city, or state_code has a value, so they are not a confirmed additional restriction on the required city/state search. Optional buyer-search inputs cover price, bedrooms, bathrooms, home age, property area, lot size, listing date, radius in miles, comma-separated property types and features, and the is_contingent, is_foreclosure, is_matterports, is_new_construction, and is_pending boolean flags. reduced remains a string parameter with documented true/false values, unlike the boolean status flags. Sort values include relevance, price_low, price_high, photos, newest, open_house_date, sqft_high, and price_reduced_date. No live sale-search response was observed in the supplied evidence. A truncated, unverified documentation example begins with a listings array and includes property_id, listing_id, address, address_new, beds, baths, baths_full, price, price_raw, sqft, sqft_raw, prop_type, prop_sub_type, prop_status, is_new_construction, is_new_listing, photo_count, list_date, last_update, and an mls object with id, name, and abbreviation. The fragment represents beds and baths as numbers, price and sqft as display strings, price_raw as a number, and sqft_raw as null. address_new includes city, state_code, postal_code, lat, and lon. Because the example is incomplete, a complete envelope, result totals, current field availability, and successful request behavior are not established. Before migrating, verify each purchase-search status and feature constraint, especially foreclosure, pending, and price-reduction requirements; do not silently drop unsupported filters.

API Features

Buyer-search status flag inventory Preserves the separate is_contingent, is_foreclosure, is_pending, and is_new_construction boolean inputs instead of collapsing distinct purchase-search requirements.
String-valued price-reduction filter Keeps reduced as a string accepting documented true/false text, while price_reduced_date is a separate sort value rather than the filter itself.
Home-age and lot-size boundaries Documents age_min, age_max, lot_sqft_min, and lot_sqft_max as distinct constraints so a saved buyer search is not reduced to price and bedroom counts.
Comma-separated home feature vocabulary Retains the documented features tokens for rooms, parking, accessibility, views, outdoor amenities, and community facilities without claiming a verified current equivalent.
Open-house and area ordering options Includes open_house_date and sqft_high alongside price and recency sort values; selecting an ordering is not represented as an open-house-only search filter.
Three-dimensional tour selector Retains the boolean is_matterports input documented for 3D-tour-only searches, separate from general photo sorting or construction status.

Live API Demo

GET /api/project/realty-in-us/properties-list-for-sale-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-list-for-sale-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 inputs are required for the deprecated for-sale search?

The schema requires city, state_code, limit, and offset. Location-autocomplete values are documented for city and state_code. The supplied examples are New York City, NY, 200, and 0; none is documented as a default.

Can a sale search combine city/state with postal code or bounding-box coordinates?

postal_code is documented as an alternative that must not be combined with city and state_code, even though the schema requires both city and state_code. The coordinate bounds are documented as having no effect when any city, state_code, or postal_code value is present. Neither a postal-only nor a bounds-only request was verified.

How do the sale status flags differ from reduced?

is_contingent, is_foreclosure, is_pending, is_new_construction, and is_matterports are boolean parameters. reduced is a string parameter documented with true/false text. Preserve these types and verify flag combinations rather than assuming the status filters can be freely combined.

Does sorting by price_reduced_date mean only reduced-price homes are returned?

That is not established. price_reduced_date is a sort value, while reduced is the separate price-reduction filter. Likewise open_house_date specifies ordering, not a documented open-house-only boolean filter.

How are sale property types and home features supplied?

Use comma-separated documented tokens. prop_type supports single_family, condo, mobile, multi_family, farm, and land. features has its own legacy vocabulary, including basement, garage_2_or_more, disability_features, waterfront, and community_park. The supplied facts do not establish the multi-value matching rule.

Are the sale response fields and result totals verified?

No live response was supplied. The incomplete documentation example shows listings and selected identity, address, price, room-count, area, status, and MLS fields. It shows numeric beds and baths, string price and sqft, numeric price_raw, and null sqft_raw, but does not establish current types or a complete envelope with result totals.

What needs special attention when migrating a saved purchase search?

Verify equivalent syntax and behavior for foreclosure, pending, contingent, price reduction, home age, lot size, features, and 3D tours. Do not silently discard a constraint that lacks a verified equivalent, and do not assume the legacy location alternatives are usable merely because the parameters are listed.

Related operations

Guides

View Subscription Plans →