Realtor.com API

Realtor.com does not offer a public API for listings data. Realtor.com's own API is lead delivery for agents. Listing feeds normally come through MLS membership and IDX or broker data agreements, which are open to licensed agents and brokers and the vendors they work with. The Scavio Realtor.com API is a REST API that returns public Realtor.com data as JSON for anyone with a key: listing search, property detail, location autocomplete, market statistics, agent search and agent profiles, 6 endpoints at 1 credit each.

Yes. Search with listing_status sold returns sold listings with sold_price and sold_date, and sold_within_days limits them to recent sales. In US sold-price non-disclosure states (Texas, Utah, Wyoming, Alaska, Idaho, Kansas, Louisiana, Mississippi, Montana, New Mexico, North Dakota and parts of Missouri) sale prices are not public record, so sold_price comes back null while the sold date is still returned. In Travis County, Texas, 0 of 200 sold land rows had a sold price, but 183 still carried the last list price and every row its sold date. Arizona, in our captured example, carries full sold prices.

Up to 200 listings per search call (page_size 1-200, default 50), and every call costs 1 credit whatever the page size. Realtor.com serves the first 10,000 results of a search, so page x page_size may not exceed 10,000. For a larger area, slice the search by price band, property type, county or ZIP and run one search per slice.

Yes. Combine listing_status sold, property_types land (or farm), sold_within_days, min_price and max_price, and lot_sqft_min (1 acre is 43,560 sq ft). Each row carries the sold price and date, lot size, address and coordinates, the MLS id and the agent when present. Sort with lot_size_high or sold_newest.

Yes. Pass keywords, up to 10 terms, and search keeps only listings whose description matches, for example workshop, live/work or detached garage. It works together with every other filter, so a keyword watch across several cities is one call per city.

Yes, on the property endpoint: three home value estimates with low and high ranges, their history and forecast, the full price history of list, price-change and sale events, and tax history with assessed and market values. Estimates, tax history and schools can be empty for land and brand-new construction, as in our captured new-build example.

Yes. The agents endpoint finds agents by city, ZIP code or name with rating, review count, recommendation count, active listings, homes sold in the last year, broker and office. The agent endpoint returns one profile with phones, website, license, MLS memberships, served areas and every review with responsiveness, market expertise, negotiation and professionalism ratings and the agent's reply.

Every Realtor.com endpoint costs 1 credit per call, and a search call returns up to 200 listings. On the Growth plan billed yearly ($2 per 1,000 credits) that is $0.002 per call, so 1,000 full search pages of 200 listings cost about $2. A request for a property, market or agent that does not exist returns a 404 and costs 1 credit; temporary failures are not billed. New accounts get 50 free credits with no card, and paid plans start at $30 per month for 7,000 credits.

Realtor.com has no free public listings API, but Scavio gives 50 free credits on signup, no card: 50 calls, up to 10,000 listings or sold comps at 200 rows per call. Every Realtor.com endpoint costs 1 credit, so the free credits also cover property detail, market statistics and agent lookups.

Yes. listing_status takes for_sale (the default, which includes pending and contingent listings as the site does), pending for only pending or contingent, for_rent for rentals with monthly rent as the price, and sold. exclude_pending drops pending and contingent rows from a for_sale search.

Scavio returns publicly available Realtor.com data: what anyone can see on a public Realtor.com page. It does not return homeowner contact details or anything behind a login. Whether your specific use is permitted depends on your jurisdiction, your use case and Realtor.com's terms, and you remain responsible for how you use the data. This is not legal advice; talk to your own counsel for your situation.

Every request reads Realtor.com live at the moment you call it, so new listings, price cuts and status changes show up as soon as Realtor.com shows them. Nothing is served from a nightly snapshot. To track changes over time, store the responses on a schedule and compare.

It covers what people usually build a Realtor.com scraper for, without one to run or maintain: you send a POST with a location and filters and get structured JSON back, with the same field names on every call. Searches, sold data, property pages, market stats and agent profiles are all covered, at 1 credit per call.

Yes. Instead of a location, pass latitude, longitude and radius_miles (0.1 to 50 miles) for a radius search, or agent_id to list one agent's listings. Each search row's agent block carries the agent_id the agent endpoint takes.