Search rental property listings (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Deprecated rental-search contract for auditing existing rental applications and planning filter-by-filter migrations. The legacy schema marks city, state_code, limit, and offset as required. City and state_code should use values from location autocomplete. Although postal_code is documented as an alternative that must not be combined with city and state_code, those two fields remain required in this schema; a postal-code-only request is not verified. The lat_min, lat_max, lng_min, and lng_max bounding-box inputs are documented as having no effect when postal_code, city, or state_code has a value, so they must not be presented as an effective additional restriction on the required city/state request. Optional filters cover price, bedroom and bathroom minimums, property area, property types, listing date, radius in miles, pet-policy flags, and community amenities. allows_cats and allows_dogs cannot be combined with no_pets_allowed. prop_type and mapi_community_features accept comma-separated documented values. The sort description lists completeness, photos, freshest, price_low, price_high, and newest, while the supplied example uses relevance; this discrepancy is unresolved. No live rental response was observed. A truncated, unverified documentation example begins with a listings array and includes property_id, listing_id, address, address_new, beds, baths, pet_policy, has_specials, price, price_raw, price_reduced, price_reduced_date, sqft, photo, photo_count, prop_type, prop_status, list_date, and last_update. In that fragment beds, baths, price, and sqft are strings, while price_raw is numeric; address_new includes city, state_code, postal_code, lat, and long. The fragment is incomplete and does not establish a complete response envelope, current field availability, freshness, or successful request behavior. Verify pet-policy and community-feature equivalents explicitly before migrating a saved rental search; do not silently omit unsupported constraints.
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-for-rent-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-list-for-rent-deprecated?key=<API_KEY>&city=<city>&limit=<limit>&offset=<offset>&state_code=<state_code>'
Query Result
Use Cases
- Audit an existing pet-friendly rental screen for incompatible combinations of no_pets_allowed, allows_cats, and allows_dogs.
- Build a rental migration checklist that separately verifies parking, laundry, pool, gym, and air-conditioning community filters.
- Explain to maintainers why a map rectangle is not documented to narrow a rental search that already supplies city and state_code.
- Prepare rental parser fixtures for string bedroom and bathroom fields, a text pet_policy, and formatted versus numeric price fields from the incomplete example.
- Review saved rental searches for sort=relevance without assuming the mismatched documented sort list confirms current support.
Frequently asked questions
Which inputs does the deprecated rental contract mark as required?
city, state_code, limit, and offset are required. City and state_code are described as values returned by location autocomplete. The example uses New York City, NY, a limit of 200, and an offset of 0; these are examples, not stated defaults.
Can postal_code or map bounds replace the required city and state?
The documentation describes postal_code as an alternative that must not be combined with city and state_code, but the schema still requires city and state_code. It also says all four coordinate bounds have no effect when any postal_code, city, or state_code value is present. Postal-only and bounds-only request behavior is unverified, so do not treat those alternatives as confirmed working modes.
How should rental pet flags be combined?
Do not combine no_pets_allowed with allows_cats or allows_dogs. These are optional boolean query parameters. The documentation does not establish whether a missing flag is equivalent to false or verify more detailed pet-policy rules.
Which community amenities can the rental endpoint request?
mapi_community_features documents community_washer_dryer, community_parking, central_air, community_pool, and community_gym. Separate multiple values with commas. A replacement endpoint must be checked for equivalent amenity syntax and meaning rather than assumed to support these legacy names.
Is relevance a confirmed rental sort option?
relevance is the supplied example, but the sort description instead lists completeness, photos, freshest, price_low, price_high, and newest. No live probe resolves that mismatch; preserve the example during an audit without claiming its current acceptance is confirmed.
What rental response fields were actually observed?
No live response was observed. An incomplete documentation fragment shows listings with identifiers, address data, beds, baths, pet_policy, prices, property status, area, and photo fields. It represents beds and baths as strings, but neither the full envelope nor current field availability is verified.