Legacy v2 rental property search (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Document an older rental-property search using the required city, state_code, limit, and offset query parameters. Optional inputs cover price bounds, minimum beds and baths, property and lot size, prop_type, prop_sub_type, allows_cats, allows_dogs, comma-separated features, radius, and sort. Documented examples are New York City, NY, 200 items, offset 0, and relevance sorting; these are not confirmed server defaults. radius is documented in miles from 1 to 20. Location caveat: the documentation says postal_code must not be combined with city and state_code, and the latitude/longitude bounds have no effect when postal_code, city, or state_code has a value. However, city and state_code remain required in this retained contract. Do not present postal-only or bounding-box-only search as a verified supported request or assume map bounds constrain the required city/state query. Response documentation, not observed output: the supplied source-example fragment shows meta.matching_rows, meta.returned_rows, and a properties array. Its first entry includes listing_id, listing_status, address, beds, building_size, lot_size, community, last_update, list_date, and photo_count. The address object includes line, city, state_code, postal_code, lat, and lon. The community object shows beds_min, beds_max, baths_min, baths_max, price_min, price_max, sqft_min, and sqft_max; the illustrated community size bounds are null. A photos field starts in the fragment, but the supplied example is truncated and is not a complete parseable response. No probe response is available; these historical fields do not confirm current rental availability, pet policies, amenity coverage, or response completeness. This deprecated route is a migration reference, not a recommended new rental integration. Inventory pet, subtype, and amenity requirements explicitly and verify a replacement contract rather than assuming every legacy filter transfers unchanged.
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-v2-list-for-rent-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-v2-list-for-rent-deprecated?key=<API_KEY>&city=<city>&limit=<limit>&offset=<offset>&state_code=<state_code>'
Query Result
Use Cases
- Audit a pet-friendly rental saved search to keep cat and dog permissions separate during migration.
- Create an explicit retained-or-unsupported checklist for furnished, no-fee, elevator, and laundry amenity requirements in an older rental experience.
- Review why a legacy rental map combined required city/state values with bounding-box fields that the documentation says have no effect.
- Compare historical community price and bedroom ranges with a replacement rental-results design while preserving null size values.
- Record rental price, bedroom, subtype, sort, and offset settings before rebuilding a paged rental shortlist against a verified current contract.
Frequently asked questions
What does the retained rental contract require?
city, state_code, limit, and offset are required. Documented examples are New York City, NY, 200, and 0. The city and state values are described as values returned by location autocomplete; the examples do not establish server defaults or a maximum page size.
Can I replace city and state with a postal code or map bounds?
That is not verified by this retained contract. The documentation says postal_code must not be combined with city/state and that lat_min, lat_max, lng_min, and lng_max have no effect when postal_code, city, or state_code is populated. Yet city and state_code remain required. Preserve this conflict in migration notes rather than claiming a postal-only or map-only request works.
How are cats, dogs, and rental amenities represented?
allows_cats and allows_dogs are separate optional true/false query inputs. features is a comma-separated string with documented tokens such as pets_allowed, furnished, washer_dryer, laundry_room, community_no_fee, community_doorman, and community_elevator. These filter names are not proof of current pet-policy or amenity accuracy.
How do property type and subtype differ in the rental query?
prop_type accepts comma-separated broad categories: single_family, multi_family, condo, mobile, land, farm, and other. prop_sub_type accepts comma-separated condo, cond_op, townhouse, and co_op values. Preserve the original tokens and verify replacement support instead of merging the two fields.
Which rental sort values and radius range are documented?
The sort tokens are relevance, newest, price_low, price_high, photos, open_house_date, sqft_high, and price_reduced_date. relevance is the supplied example, not a confirmed default. radius is documented as 1 to 20 miles; its behavior alongside conflicting location inputs is not verified.
Does the example prove the current rental response schema?
No. There is no probe response, and the source example is truncated. It illustrates meta counts and properties entries with listing_id, address, listing_status, community price/bed/bath ranges, and nullable community size ranges. Treat these as historical response references, not guaranteed present-day fields or available rentals; use this deprecated route only as a migration reference.