Get Realtor.com data with one API

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.

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.

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.

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.

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.

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.

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.

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.

Realtor.com API is a ReefAPI endpoint group for realtor.com It returns live JSON through POST requests under /realtor/v1.

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.

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.

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

Realtor.com actions currently cost 1-3 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

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.