US rentals as JSON, with the asking rent per bed count
The Apartments.com API turns apartments.com, the largest US rental marketplace, into clean JSON in three actions.
3 active endpoints, on 0, 1 and 2 credit tiers.
- POST/apartments/v1/search
- POST/apartments/v1/property/detail
- POST/apartments/v1/locations
What Apartments.com endpoints does ReefAPI ship?
3 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Apartments.com API
3 of 3 endpoints, ready to run
Rental buildings in a place: listing id, URL, name, street address split into street, city, state and ZIP, one floor_plans entry per bed count with its asking rent, the amenity strip, the move-in specials, the leasing phone, the photos and the tour flags.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Apartments.com API works
Apartments.com is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 294 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Resolve the box once, then re-run it forever
A map box is stable and a place name is a lookup. Resolving once and storing the box turns a daily rent index into one paid call per page.
{"query": "austin"}Zero credits. Returns cities, ZIP codes, neighbourhoods and counties, each with its coordinates, its bounding box and the source's own count of available units. That last number sizes the market before you pay for a single row.
{"bounding_box": "<from above>", "limit": 40}2 credits for 40 buildings. Passing the box skips the lookup entirely. Each row carries floor_plans with one entry per bed count, which is the asking rent you want in a rent index rather than a single blended number.
{"property_id": "<a row's property_id>"}1 credit. Coordinates, the renter rating and the neighbourhood label. The seven-character key is stable across search, detail and a second search, so it is safe to store.
One row per building per day, with the rent per bed count and a listing key you can join on tomorrow.
curl -X POST https://api.reefapi.com/apartments/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"location":"Austin, TX","limit":40}'{
"ok": true,
"data": { … },
"meta": {
"api": "apartments",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What arrives on an Apartments.com row, and what the open surface never publishes
Field fill measured on 2026-09-24 over 480 rows, then re-checked on 320 rows across eight cities, counted per city rather than pooled. A sparse field here is the source being silent, and it is separated from a parse gap on purpose.
| Field | Fill | What it means |
|---|---|---|
| property_id, url, phone, image | 480 of 480 | Always present. The listing key is a stable seven-character code that survives search, detail and a second search. |
| floor_plans, beds_min, beds_max | 480 of 480 | One entry per bed count, which is how the source publishes rent. rent_min and rent_max are derived from it and carry a derived flag. |
| rent_min / rent_max | 471 of 480 | The other nine publish Call for Rent. They come back with rent_published false and their bed range intact, never a zero. |
| address, city, state | 466 of 480 | A handful of placards carry no address title at all. |
| amenities | 399 of 480 | A short marketing strip, not the full building amenity list. Some placards publish none. |
| pet_policy_summary | 366 of 480 | Derived from that same strip, and absent when the strip is. The full pet policy text is not on this surface. |
| square footage per floor plan, fee schedule, review count | 0 | Not published on the open surface. Absent rather than estimated. |
A row is a building, not a unit. total_units is the source's own count of available units inside the map box, which is a different number from the buildings returned: one measured Austin box reported 30,175 units against 40 buildings on the page.
A row is a building, and the rent is per bed count
Measured 2026-09-24: 56 calls, 480 rows, then a re-check on 320 rows across Seattle, Miami, Denver, Brooklyn, Phoenix, Boston, Portland and Atlanta, counted per city rather than pooled. Three of these lines go against us.
Apartments.com publishes rent for a whole property broken down by bed count, so floor_plans carries one entry per bed count with its own asking rent. rent_min and rent_max are derived from that and carry a derived flag. Flattening it to a single number would throw away the only price signal the source gives.
A city and state, a ZIP code, a neighbourhood or a street address are all resolved to a map box. Pass bounding_box, or latitude and longitude with radius_miles, and the lookup is skipped. locations returns the box for any of them and costs nothing, so an area can be resolved once and re-run indefinitely.
1,196 with a plus on a 1 Bed means the cheapest one-bedroom is 1196, not that one-bedrooms cost 1196. The flag is price_is_from, the printed string is rent_display and the number is rent_from.
471 of 480 rows carried a rent. The other nine publish Call for Rent, and they come back with rent_published false and their bed range intact rather than a zero. They are left out whenever a rent filter is set, because they cannot be confirmed to match, and quietly keeping them would report a building as being under budget when the source never said so.
Sorting is the source's and is echoed back. The rent, bed, pet, amenity, tour and specials filters are applied here, and filters_applied_by reads reefapi when any is set. Measured on Austin, min_beds, max_rent, pets, has_3d_tour and specials_only each removed the rows that violated them and let zero violations through, with a second upstream page read to refill the limit.
Per-plan square footage, unit-level availability dates, the fee schedule, the full pet policy text, the management company name and the review count are not published on the surface this reads. They are absent rather than estimated. A rating number is published on property/detail; the count behind it is not.
amenities arrived on 399 of 480 rows and pet_policy_summary, which is derived from the same strip, on 366. Some placards publish no strip at all. It is not the full building amenity list, and the pet filter matches that strip rather than a policy document.
It is the source's own count of available units inside the map box, which is a different measure from the buildings on the page: one measured Austin box reported 30,175 units against 40 buildings. Paging is real, with an overlap of 11, 0 and 0 between the first two pages on Austin, Chicago and Brooklyn, and rows are de-duplicated by property_id inside a call.
locations is free, so guessing a bounding box is never the cheaper option. search is 2 credits for up to 40 buildings and property/detail is 1.
What people build with Apartments.com
The jobs this data is most often used for.
endpoints
credits per call
Rent-index and market-tracking pipelines store one row per building per day from floor_plans, which gives the asking rent per bed count rather than a single blended number.
Relocation and HR tools resolve a destination with locations and then pull the buildings inside that box with search, filtered to a budget and a bed count.
Property managers and investors watch competing buildings in a submarket by re-running the same bounding box and diffing rent per bed count over time.
Lead-generation tools read the leasing-office phone and the move-in specials to see which buildings in a market are discounting this month.
What Apartments.com data costs
The cheapest call here is 0 credits, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 294 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/apartments/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"location":"Austin, TX","limit":40}'import requests
r = requests.post(
"https://api.reefapi.com/apartments/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"location": "Austin, TX",
"limit": 40
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Apartments.com.
Get a free key →Is an Apartments.com result one apartment or one building?▾
One building. Apartments.com publishes rent per bed count for a whole property, so each row carries floor_plans with one entry per bed count, Studio, 1 Bed, 2 Beds and so on, each with its own asking rent. Flattening that to a single number would throw away the only price signal the source gives, so it is kept and rent_min and rent_max are derived from it, marked as derived.
What does the plus sign on an Apartments.com rent mean?▾
It is the source's own from marker and it is preserved. 1,196 with a plus on a 1 Bed means the cheapest one-bedroom in that building is 1196, not that one-bedrooms cost 1196. The flag is price_is_from, the printed string is rent_display and the number is rent_from. A building that publishes no rent at all comes back with rent_display reading Call for Rent and rent_published false, never a zero.
Can I filter by price, beds, pets or amenities?▾
Yes, and the response tells you who applied each one. Sorting is done by the source and echoed back. The price, bed, pet, amenity, tour and specials filters are applied to the parsed rows, and filters_applied_by reads reefapi when any of them is set, so you always know whether a number came from the source's own filtering or from ours. Measured on Austin, each of min_beds, max_rent, pets, has_3d_tour and specials_only removed rows that violated it and let zero violations through. Buildings that publish no rent are left out whenever a rent filter is set, because they cannot be confirmed to match.
How do I search a specific area rather than a whole city?▾
Pass bounding_box as south,west,north,east, or latitude and longitude with radius_miles, and the location lookup is skipped entirely. The locations action returns the box for any city, ZIP, neighbourhood or address and costs nothing, so you can resolve once, store the box and re-run the same area for as long as you like.
Does it return floor plan square footage, fees or the full pet policy?▾
No, and it says so rather than guessing. Per-plan square footage, unit-level availability dates, the fee schedule, the full pet policy text, the management company name and the review count are not published on the surface this API reads, so those are absent rather than filled with an estimate. What you do get on every building is the rent per bed count, the address, the coordinates, the amenity strip, the specials, the photos and the leasing phone.
Does paging return fresh buildings?▾
Yes. Pages one, two and three were compared on Austin, Chicago and Brooklyn: 40 rows each, with an overlap of 11, 0 and 0 between the first two pages and 0, 0 and 2 between the first and third, because the source re-ranks sponsored placements between requests. Rows are de-duplicated by property_id inside one call, so the same building never appears twice in one response.
What is the Apartments.com API?▾
Apartments.com API is a ReefAPI endpoint group for us rental buildings with the asking rent per bed count, amenities, address, photos and the leasing phone. It returns live JSON through POST requests under /apartments/v1.
Is the Apartments.com API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Apartments.com calls use the same shared credit balance as every other ReefAPI engine.
Do I need an Apartments.com login or account?▾
No login to Apartments.com is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Apartments.com data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Apartments.com API use?▾
Apartments.com actions currently cost 1-2 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Apartments.com from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call apartments actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Apartments.com API an Apartments.com scraper?▾
It is the managed alternative to a DIY Apartments.com scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same us rental buildings with the asking rent per bed count, amenities, address, photos and the leasing phone back as clean JSON.
Why does my Apartments.com scraper keep getting blocked?▾
Most Apartments.com scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked calls are free.
16 Real Estate APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Apartments.com, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 293 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-09-24.