Legacy v2 homes-for-sale search (deprecated)

View all Realty in US Property & Mortgage Data endpoints →

Document a legacy buyer search for properties for sale with required city, state_code, limit, and offset query parameters. Optional criteria include price and property-size bounds, lot size, minimum beds and baths, property age bounds, prop_type, prop_sub_type, comma-separated features, radius, and sort. Boolean flags separately describe open houses, contingent listings, foreclosures, 3D tours, new construction, homes not yet built, and pending listings through has_open_house, is_contingent, is_foreclosure, is_matterports, is_new_construction, is_new_plan, and is_pending. The documented radius range is 1 to 20 miles. New York City, NY, limit 200, offset 0, and relevance sorting are supplied examples, not confirmed defaults. Location caveat: postal_code is documented as incompatible with city/state_code, although city and state_code remain required. The lat_min, lat_max, lng_min, and lng_max bounds are documented as having no effect when postal_code, city, or state_code has a value. Treat these conflicting legacy location modes as migration issues, not as verified postal-only, map-only, or city-plus-bounds search capabilities. Response documentation, not observed output: the truncated source-example fragment shows meta.matching_rows, meta.returned_rows, and a properties array. Visible property fields include property_id, listing_id, price, beds, baths, baths_full, prop_status, prop_type, prop_sub_type, photo_count, last_update, address, and mls. The address object shows line, city, state_code, postal_code, lat, and lon; the mls object shows id, abbreviation, name, and type. The fragment is not a complete parseable response, and no probe response is available. These historical fields do not confirm current inventory, response completeness, open-house availability, or the presence of tour data. Retain this deprecated route as a buyer-search migration reference only. Evaluate open-house, new-plan, new-construction, and listing-status intent against a replacement contract individually; do not assume a current property-search operation accepts the same GET query or identical filter semantics.

API Features

Open-house and tour intent audit Keep has_open_house separate from the is_matterports 3D-tour flag; neither documented filter proves that event details or tour media are returned.
New plans versus construction Preserve the distinction between is_new_plan for homes not yet built and the separate is_new_construction flag when assessing replacement behavior.
Contingent and pending status review Inventory is_contingent, is_pending, and is_foreclosure independently instead of flattening all legacy buyer searches into an undifferentiated sale query.
Buyer-specific physical criteria Document age_min, age_max, bedroom and bathroom minima, and separate property and lot size bounds as distinct purchase-search requirements.
Sale-search contract transition Use the documented GET parameters as a filter checklist and verify the replacement request shape instead of pasting the legacy query into a current search.

Live API Demo

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

city, state_code, limit, and offset are required. New York City, NY, 200, and 0 are the supplied examples. They are example inputs, not proof of server defaults, supported maximums, or current inventory in that location.

What is the difference between is_new_plan and is_new_construction?

The documentation describes is_new_plan as homes not yet built and is_new_construction as new-construction-only filtering. Both are optional booleans. Preserve their separate intent; the supplied evidence does not establish that they are equivalent or describe how combining them behaves.

Do open-house and 3D-tour filters return event schedules or playable tours?

That is not established. has_open_house is documented as open-houses-only filtering, while is_matterports is documented as 3D-tours-only filtering. The unverified, truncated source example does not confirm event schedules, tour URLs, or their present-day availability.

Which flags describe listing status or foreclosure intent?

is_contingent, is_pending, and is_foreclosure are separately documented true/false filters for contingent, pending, and foreclosure-only listings. The evidence does not define their mutual compatibility or guarantee that every replacement search exposes matching controls.

Can postal codes or map bounds be combined with the required city and state?

The legacy documentation says not to combine postal_code with city/state_code and says all four latitude/longitude bounds have no effect when a postal, city, or state value is present. city and state_code nevertheless remain required. Do not claim a working postal-only, map-only, or city-plus-bounds mode without a separately verified contract.

What do the historical sale response fields establish?

Only a source-example reference is available, not a probe response. The truncated example illustrates meta.matching_rows, meta.returned_rows, and properties entries with property_id, listing_id, price, bed/bath counts, prop_status, address, and mls. It does not establish current field coverage or filter behavior. This deprecated route is intended as migration documentation, not the recommended starting point for a new buyer-search integration.

Related operations

Guides

View Subscription Plans →