Use case
Zillow rental building API
A rental search returns apartment buildings and single homes as two marked shapes. A building's id opens its floor plans — every plan with beds, baths, square feet, the rent range and lease term — and the units available under each, with price and move-in date.
curl "https://zillow-full-data-api.p.rapidapi.com/building/floor-plans?buildingId=2738891304" \
-H "X-RapidAPI-Key: YOUR_KEY" -H "X-RapidAPI-Host: zillow-full-data-api.p.rapidapi.com"{
"buildingId": "2738891304",
"count": 13,
"floorPlans": [
{
"name": "A1",
"beds": 1,
"baths": 1,
"sqft": 568,
"minPrice": 1320,
"maxPrice": 1370,
"leaseTerm": "12 Months",
"units": [
{
"unitNumber": "Unit 1402",
"price": 1320,
"sqft": 568,
"availableFrom": "2026-09-04"
},
"… 2 more units"
]
},
{
"name": "A2",
"beds": 1,
"baths": 1,
"sqft": 633,
"minPrice": 1325,
"maxPrice": 1420,
"leaseTerm": "12 Months",
"units": [
{
"unitNumber": "Unit 2211",
"price": 1325,
"sqft": 633,
"availableFrom": "2026-09-28"
},
"… 7 more units"
]
},
"… 11 more floor plans"
]
}Shown: two floor plans and one unit each. Photos, virtual tours and the building's amenities are in the full answer.
What you get
/building for the building itself — name, address, amenities, photos — and /building/floor-plans for the plans and units. Either takes a buildingId or a lat/lng.
Where the id comes from
A forRent search: rows with resultType: "propertyGroup" are buildings and carry buildingId, the rent range and the count of matching units; rows marked property are single homes and units.
Where it fits
Rental comps by bedroom count for a ZIP, a leasing team's competitive set, a daily watch on availability and price changes, or a map of buildings with units under a rent.
Batch it
/batch takes building and floor-plans items: a ZIP's worth of buildings in one call, each with its own status.
Endpoints: GET /building/floor-plans, /building and POST /search with status: forRent.