Find similar rental homes by postal code and property ID (deprecated)

View all Realty in US Property & Mortgage Data endpoints →

Legacy lookup for rental homes similar to a reference property. Both postal_code and property_id are required string query parameters: take postal_code from a listing response and property_id from a property-listing response. A postal code alone is not a complete request, and the documented contract does not establish a configurable search radius. This route is explicitly deprecated; its notice points to /properties/v2/list... endpoints without confirming an equivalent rental recommendation contract. No observed probe response or documented response example is available for this operation, so the response envelope, rental-status fields, asking-rent fields, ordering and empty-result format are unverified. Do not treat suggested rental candidates as evidence of completed leases or achieved rents.

API Features

Paired rental reference inputs Both postal_code and property_id are required strings, preserving the two-input contract used by existing related-rental integrations.
Listing-derived postal code The postal_code input is documented as a value returned by listing endpoints, not as an independently verified radius or geographic-boundary filter.
Rental-specific migration review The documented purpose is rental recommendations. Any replacement needs separate verification that it returns rental candidates rather than for-sale suggestions.
Lease-price interpretation guard No response example verifies rent or lease fields. Rental suggestions must not be presented as completed-lease records or achieved rental prices.

Live API Demo

GET /api/project/realty-in-us/properties-v2-list-similar-rental-homes-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-similar-rental-homes-deprecated?key=<API_KEY>&postal_code=<postal_code>&property_id=<property_id>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Which inputs does the legacy rental lookup require?

Both postal_code and property_id are required query parameters with string types. A request containing only one of them does not satisfy the documented contract.

Where do the postal code and property ID come from?

The documented postal_code value comes from listing results. The property_id comes from a property-listing response, including documented /properties/list-... or /properties/v2/list-... searches. Preserve identifier strings as returned rather than converting them to numbers.

Does postal_code define a guaranteed recommendation boundary?

The available documentation identifies postal_code as a required input but does not explain recommendation boundaries, distance rules or ranking. No radius input is documented, so geographic behavior must not be assumed.

Does this operation return completed leases or achieved rents?

Its stated purpose is to list similar homes for rent, not completed leases. No observed response or documented example verifies rental-status, asking-rent or achieved-rent fields for this route.

Can I replace this with a similar-homes-for-sale lookup?

Do not assume equivalence. The route is deprecated and its notice refers to /properties/v2/list... endpoints, but a replacement must be checked separately for rental candidates, input requirements and response compatibility.

Related operations

Guides

View Subscription Plans →