Realtor.com API & Scraper
The Realtor.com API returns US real-estate data — for-sale, sold and rental listings — as clean JSON.
🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.
The primary search endpoint returns properties with property id, URL, list price, status, type, beds, baths, square footage, lot size, year built and the RealEstimate value, and you can pull a detail, estimates, sold history, market_trends and comps. It is built for real-estate investors, brokerage tools and property dashboards that need live Realtor.com data without a scraper. One ReefAPI key, one shared credit pool, the standard envelope.
Realtor.com ids, prices and what a non-disclosure state hides
Two things bite people here: the property_id does not look like the code in the URL, and sold prices are missing across a large part of the country by law rather than by any failure to read the page. Measured 2026-08-27 across Austin TX, Miami FL, Sacramento CA, Seattle WA and Denver CO.
| Field | What it holds | Measured 2026-08-27 |
|---|---|---|
| property_id to URL M-code | Split the 10-digit id after five digits and prefix M | 8112218355 becomes ..._M81122-18355; the rule held on 25 of 25 Austin rows |
| listing_id | A separate id for the listing, not the property. Do not pass it as property_id | property_id 8112218355 carried listing_id 3000103553 |
| last_sold_price_usd | null in non-disclosure states, where sale prices are not public record | 0 of 25 Austin TX sold rows had it; 10 of 10 did in Miami, Sacramento, Seattle and Denver |
| list_price_usd on for_rent | Monthly rent in USD, while realestimate_usd on the same row is still the sale value | An Austin rental read list_price_usd 3200 next to realestimate_usd 648000 |
| realestimate_usd | Realtor.com's own automated valuation, returned on search cards as well as on detail | A card listed at 1,879,000 carried realestimate_usd 1,792,400 |
| lot_sqft | Square feet, never acres (43,560 sqft is one acre) | lot_sqft 47393 is 1.09 acres |
| estimates source_type | corelogic (Cotality), quantarium, collateral (Collateral Analytics); one is flagged is_best | Three AVMs for 7211899596: 192,500 / 188,427 / 196,000 |
| property_type | single_family, condos, townhomes, multi_family, mobile, land, farm, the same words you filter with | One 25-row sold page returned land, condos, mobile, townhomes and single_family |
| autocomplete id prefixes | city:, ps: for a ZIP, county:, school: | city:tx_austin, ps:tx_78704, county:tx_travis, school:0758585001 |
| market_trends geo_type | City for a place name, PostalCode for five digits | "Austin, TX" returned geo_type City; "78704" returned PostalCode |
| detail price_history Sold event | price_usd 0 where the sale price is not public | The 2026-07-17 Sold event read price_usd 0 with list_price_usd 185,000 |
search and sold cap at limit 200 per call and page with offset; meta.total tells you how deep the result set goes, which was 7,100 active and 126,854 sold for Austin on 2026-08-27. An unknown property_id is a clean failure rather than an empty success: detail on 1234567890 returned ok:false with NOT_FOUND.
Real request and response JSON
Captured from the indexed primary action, search, on .
{
"method": "POST",
"url": "https://api.reefapi.com/realtor/v1/search",
"headers": {
"x-api-key": "$REEF_KEY",
"content-type": "application/json"
},
"body": {
"location": "Austin, TX"
}
}{
"ok": true,
"meta": {
"api": "realtor",
"endpoint": "search",
"mode": "live",
"latency_ms": 681.6,
"record_count": 42,
"bytes": 128240,
"cache_hit": false,
"stop_reason": "limit_reached",
"total": 7009,
"count": 42,
"filters_applied": {},
"status": "for_sale",
"offset": 0,
"limit": 42,
"charged_credits": 2,
"version": "1.1.0"
},
"data": {
"results": [
{
"property_id": "9529141354",
"listing_id": "3001044282",
"status": "for_sale",
"list_price_usd": 389000,
"list_date": "2026-09-23T21:28:53.000000Z",
"last_sold_price_usd": null,
"last_sold_date": null,
"price_reduced_amount_usd": null,
"realestimate_usd": null,
"beds": 3,
"baths": 3,
"baths_full": 2,
"baths_half": 1,
"sqft": 2475,
"lot_sqft": 4478,
"year_built": 1986,
"property_type": "condos",
"sub_type": "condo",
"garage": 2,
"stories": 2,
"primary_photo_url": "http://ap.rdcpix.com/3b1abfc8904ec03887fe803fdbcd31ccl-m2778611991s.jpg",
"photo_count": 39,
"flags": {
"is_new_listing": true,
"is_price_reduced": null,
"is_pending": null,
"is_foreclosure": null,
"is_contingent": null
},
"branding": [
"Coldwell Banker Realty"
],
"url": "https://www.realtor.com/realestateandhomes-detail/10900-Crown-Colony-Dr-2_Austin_TX_78747_M95291-41354",
"address_line": "10900 Crown Colony Dr Unit 2",
"city": "Austin",
"state_code": "TX",
"postal_code": "78747",
"county": "Travis",
"latitude": 30.139282,
"longitude": -97.794312
},
{
"property_id": "8848017238",
"listing_id": "3001044214",
"status": "for_sale",
"list_price_usd": 319000,
"list_date": "2026-09-23T21:26:19.000000Z",
"last_sold_price_usd": null,
"last_sold_date": "2020-06-30",
"price_reduced_amount_usd": null,
"realestimate_usd": 314300,
"beds": 2,
"baths": 2,
"baths_full": 2,
"baths_half": null,
"sqft": 1141,
"lot_sqft": 2374,
"year_built": 1982,
"property_type": "condos",
"sub_type": "condo",
"garage": 1,
"stories": 1,
"primary_photo_url": "http://ap.rdcpix.com/e30d23c1408abac586dcbc0b33c3ca90l-m1433322130s.jpg",
"photo_count": 25,
"flags": {
"is_new_listing": true,
"is_price_reduced": null,
"is_pending": null,
"is_foreclosure": null,
"is_contingent": null
},
"branding": [
"Keller Williams Realty"
],
"url": "https://www.realtor.com/realestateandhomes-detail/2612-San-Pedro-St-Apt-211_Austin_TX_78705_M88480-17238",
"address_line": "2612 San Pedro St Apt 211",
"city": "Austin",
"state_code": "TX",
"postal_code": "78705",
"county": "Travis",
"latitude": 30.292127,
"longitude": -97.746309
},
{
"property_id": "8766806006",
"listing_id": "3001043617",
"status": "for_sale",
"list_price_usd": 515000,
"list_date": "2026-09-23T21:22:16.000000Z",
"last_sold_price_usd": null,
"last_sold_date": "2021-12-09",
"price_reduced_amount_usd": null,
"realestimate_usd": 471800,
"beds": 4,
"baths": 4,
"baths_full": 2,
"baths_half": 2,
"sqft": 1959,
"lot_sqft": 7562,
"year_built": 1981,
"property_type": "multi_family",
"sub_type": null,
"garage": 2,
"stories": 2,
"primary_photo_url": "http://ap.rdcpix.com/73a6618882e9efe3715a6204435b3fcal-m3764613141s.jpg",
"photo_count": 15,
"flags": {
"is_new_listing": true,
"is_price_reduced": null,
"is_pending": null,
"is_foreclosure": null,
"is_contingent": null
},
"branding": [
"Compass RE Texas"
],
"url": "https://www.realtor.com/realestateandhomes-detail/7100-Woodhue-Ct_Austin_TX_78745_M87668-06006",
"address_line": "7100 Woodhue Ct",
"city": "Austin",
"state_code": "TX",
"postal_code": "78745",
"county": "Travis",
"latitude": 30.198668,
"longitude": -97.802563
}
],
"total": 7009,
"count": 42,
"filters_applied": {}
}
}What the Realtor.com API does
| Action | Description | Concrete use case | Key params |
|---|---|---|---|
| search | Search Realtor.com listings by location (for sale / for rent / recently sold), with structured filters: price, beds, baths, property type, sqft, lot size, year built, HOA, days-on-market and keywords. Paginate with offset. | Real-estate investors call search to search Realtor.com listings by location (for sale / for rent / recently sold), with structure…. | location, status, sort, limit, offset, ... |
| detail | Full property record by property_id: RealEstimate value (+ range), price history, tax history, schools (with ratings), photos, interior/exterior feature groups, HOA, status flags, monthly-payment estimate and the listing agent/broker. | Brokerage tools call detail to get full property record by property_id. | property_id |
| estimates | Multi-source home-value estimates (AVMs) for a property — Realtor.com surfaces several independent valuation models (Collateral Analytics, Quantarium, Cotality/CoreLogic), each with its own value and high/low range. Returns the full set plus the best estimate. The valuation surface for pricing a home. | Property dashboards call estimates to get multi-source home-value estimates (AVMs) for a property. | property_id |
| sold | Recently-sold homes by location (or map bounds), with the same structured filters as search — the comparable-sales surface for valuing a home. | Lead-generation teams call sold to get recently-sold homes by location (or map bounds), with the same structured filters as search. | location, sort, limit, offset, map_bounds, ... |
| market_trends | Local housing-market intelligence for a US city or ZIP — median listing price, median sold price, median price per square foot, median days-on-market and median rent. The market-overview surface for a neighborhood or metro. | Real-estate investors call market_trends to get local housing-market intelligence for a US city or ZIP. | location |
| comps | Comparable homes near a property — synthesized from recently-sold and active listings around the subject's coordinates, scored by distance, beds and sqft. | Brokerage tools call comps to get comparable homes near a property. | property_id, radius_miles, max_comps, include_active |
| autocomplete | Location autocomplete — suggest Realtor.com cities, ZIPs, neighborhoods, counties and schools for a free-text query. Resolve a fuzzy term before searching, or power a search box. | Property dashboards call autocomplete to get location autocomplete. | query |
Call search from your stack
curl -X POST https://api.reefapi.com/realtor/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"location":"Austin, TX"}'import requests
r = requests.post(
"https://api.reefapi.com/realtor/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"location": "Austin, TX"
},
)
print(r.json()["data"])const res = await fetch("https://api.reefapi.com/realtor/v1/search", {
method: "POST",
headers: {
"x-api-key": process.env.REEF_KEY,
"content-type": "application/json",
},
body: JSON.stringify({
"location": "Austin, TX"
}),
});
const { ok, data, meta, error } = await res.json();Ask your MCP-connected assistant: call reefapi.realtor.search with {"location":"Austin, TX"}.Who uses this API and why
- Real-estate investors call search then comps to find and value properties in a target market.
- Market dashboards use market_trends and estimates to track prices and inventory in an area.
- Lead-gen tools use detail and sold to enrich listings and identify recent transactions.
Questions developers ask before integrating
How do I turn a property_id into a Realtor.com URL?
The id is a 10-digit number and the URL carries it split in half with an M in front. property_id 8112218355 appears in the listing URL as _M81122-18355, 7054144423 as _M70541-44423, and 7871052065 as _M78710-52065. The rule held on all 25 rows of one Austin sold page checked on 2026-08-27. You do not have to build it yourself, because every search and sold row already includes the full url.
Why is last_sold_price_usd null?
Because the property is in a non-disclosure state, where sale prices are not public record. Measured on 2026-08-27: all 25 Austin, Texas sold rows returned null, while Miami FL, Sacramento CA, Seattle WA and Denver CO each returned a price on 10 of 10 rows. The same gap shows up in detail, where the price_history Sold event carries price_usd 0, and in market_trends, where median_sold_price_usd is simply absent for Texas but present for California and Florida. Nothing is being withheld by the API; the number does not exist upstream.
Is list_price_usd the rent or the sale price?
It depends on status. For for_sale and sold it is the asking price. For for_rent it is the monthly rent: one Austin rental returned list_price_usd 3200 alongside realestimate_usd 648000, which is the home's value, not an annual rent. Read status before you compare prices across rows, and never mix realestimate_usd into a rent series.
How does a Realtor.com record differ from a Zillow one?
The identifier and the estimate change name, and the enums change case. Realtor.com identifies a property by a 10-digit property_id, Zillow by a zpid. The valuation here is realestimate_usd from Realtor.com's RealEstimate, not a Zestimate, and the estimates action breaks it into three independent models. Realtor.com's status and property_type values are lowercase and match the words you filter with (single_family, condos, for_sale), whereas Zillow's response enums are uppercase and differ from its filter words. No MLS number is returned on either the card or the detail record.
Which value should I trust, realestimate_usd or the estimates action?
estimates gives you the three models separately, each with its own value, high, low and date, with one flagged is_best. For property 7211899596 on 2026-08-27 that was Cotality 192,500 (range 179,400 to 205,600), Quantarium 188,427 and Collateral Analytics 196,000. detail's realestimate_usd equals the best estimate, but its realestimate_range_usd of 188,427 to 196,000 is the spread between the three models' point values, not the best model's own confidence range. If you want a genuine uncertainty band, read estimate_low_usd and estimate_high_usd from estimates.
Why does autocomplete put an address in the name field?
For type school it does, and the school's actual name is in slug_id. Searching "Lincoln High" returned name "1750 Southwest Salmon Street" with slug_id "Lincoln-High-School-0758585001". A county row is odd in the other direction: name is just the state code ("TX") while slug_id holds "Travis-County_TX". Cities behave normally, with name "Austin, TX". geo_id is a UUID for cities and counties and null for schools.
What does comps actually compare against?
Recently sold homes inside a radius around the subject's coordinates, scored on distance, beds and sqft. Defaults are 2 miles and 12 comps, adjustable to 0.25-25 miles and up to 50 comps. Set include_active to true to mix in current listings. In a non-disclosure state each comp still comes back with last_sold_price_usd null, so a Texas comp set gives you addresses, beds, baths, sqft, distance_miles and the last list price, but no sold prices to average.
Is lot size in acres or square feet?
Square feet, in both directions. lot_sqft in the response and lot_min and lot_max in the filters are all square feet, so 43,560 is one acre and a measured lot_sqft of 47,393 is 1.09 acres. sqft is living area, a separate number: one row had sqft 4,039 inside that 47,393 sqft lot. Filtering with lot_max=43560 means one acre or less, not 43,560 acres.
What is the Realtor.com API?
Realtor.com API is a ReefAPI endpoint group for realtor.com It returns live JSON through POST requests under /realtor/v1.
Is the Realtor.com API free to try?
Yes. ReefAPI starts with 1,000 free credits, no card required. Realtor.com calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Realtor.com login or account?
No login to Realtor.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 Realtor.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 Realtor.com API use?
Realtor.com actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Realtor.com from an AI assistant or MCP client?
Yes. Connect ReefAPI once through MCP and your assistant can call realtor actions with the same key, credit pool and JSON envelope used by normal REST requests.