Housing market research
Pull every listing in a city search with price, beds, baths and size, then compare price per square foot across neighborhoods and home types.
- 1search-listings
- Market table
Search listings, property details with beds, baths, size and photos, and real estate agents by ZIP code: every live Realtor.com endpoint returns typed JSON in the same response envelope. Public data only.
Pick the data you need. The live endpoints take a Realtor.com URL or a ZIP code and give you clean JSON back for 1 credit per successful call. Cards without a GET path are on our final API list and show the input they take.
GET/api/v2/realtor-search-listings/Listings from a Realtor.com search URL, a page at a time: price, status, beds, baths, size and last price change.
GET/api/v2/realtor-property/Property records from a search or detail URL: list price, beds, baths, sqft, year built, address and photos.
GET/api/v2/realtor-agent-by-zipcode/Real estate agents for a ZIP code: listing and sold counts, phones, office, areas served and reviews.
INkeywordsPublic email addresses on Realtor.com pages that match a keyword, with the page title, description and URL.
INkeywordsPublic phone numbers on Realtor.com pages that match a keyword, with the country and dial code.
Pick an endpoint, fill in the input and press Run. Without a key you see the catalog sample and nothing is billed. With your API key it runs a real call from your browser.
Every successful call costs 1 credit, whether the page holds one profile or a page of comments. Failed calls cost nothing. A free tier lets you try it first.
On Pro, 1,000 calls at 1 credit cost $1.58. Scale brings that to $1.20, so 250,000 Realtor.com calls a month is $299.
See all plans →| Plan | Price / mo | Credits / mo | Per 1,000 calls |
|---|---|---|---|
| Free | $0 | Free tier | — |
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |
Built to be easy to start with, even if you've never scraped a website. Here's how to get Realtor.com data in a few minutes:
urls, or one ZIP code in zipcodes, per call.realtor-property, set mode to BUY, RENT or SELL for search URLs.next_cursor; pass it back as cursor for the next page.X-API-Key header, or ask your AI agent over MCP.Two ways in. Use whichever matches what you already have.
You already have the links to the pages you want.
realtor.com/realestateandhomes-search/Austin_TXrealtor.com/realestateandhomes-search/Las-Vegas_NVStart from a place, an area or a ZIP code.
90210// GET /api/v2/realtor-search-listings/ { "urls": "https://www.realtor.com/realestateandhomes-search/Austin_TX", "deep_details": "false" }
// GET /api/v2/realtor-property/ { "urls": "https://www.realtor.com/realestateandhomes-search/Las-Vegas_NV", "mode": "BUY", "include_floorplans": "true" }
// GET /api/v2/realtor-agent-by-zipcode/ { "zipcodes": "90210", "sort_by": "RELEVANT_AGENTS", "max_retries": "3" }
| Send this | Parameter | And you can get |
|---|---|---|
| Realtor.com search URL | urls | Listings with price, status, beds, baths, size and price changes |
| Search or detail URL | urls · mode | Property records with address, coordinates, year built and photos |
| ZIP code | zipcodes · sort_by | Agents with phones, office, listing and sold counts and reviews |
Optional on list endpoints: cursor (pass back next_cursor for the next page). Auth is one header: X-API-Key. Send parameters in the query string (GET) or as a JSON body (POST).
The one thing to know: each data type has its own shape. Field names stay the same on every call, so code and agents read them directly. Samples below come from the live catalog.
// GET /api/v2/realtor-search-listings/?urls=https://www.realtor.com/realestateandhomes-search/Austin_TX // one item of data.listings · catalog sample { "__typename": "Home", "propertyId": "1234567890", "listingId": "9876543210", "lastUpdateDate": "2026-11-30T10:00:00Z", "lastPriceChangeDate": null, "lastPriceChangeAmount": null, "status": "for_sale", "href": "https://www.realtor.com/realestateandhomes-detail/1234-main-st...", "tags": [ "new_listing" ], "description": { "baths": 2, "beds": 3, "sqft": 1850, "type": "single_family", "yearBuilt": 2010 }, "location": { "address": { "city": "Austin", "state_code": "TX" } }, "price": 525000, "scraped_at": "2026-12-01T12:00:00.000Z", "input_url": "https://www.realtor.com/realestateandhomes-search/Austin_TX" }
// GET /api/v2/realtor-property/?urls=https://www.realtor.com/realestateandhomes-search/Las-Vegas_ // one item of data.properties · catalog sample { "url": "1234-main-st_las-vegas_nv_89101_M12345-67890", "status": "for_sale", "id": "1234567890", "listPrice": 450000, "baths": 3, "baths_full": 2, "baths_full_calc": 2, "beds": 4, "sqft": 2150, "stories": 2, "sub_type": null, "text": "Beautiful family home...", "type": "single_family", "year_built": 2015, "coordinates": { "latitude": 36.1699, "longitude": -115.1398 }, "address": { "street": "1234 Main St", "locality": "Las Vegas", "region": "NV", "postalCode": "89101" }, "photos": [], "scraped_at": "2026-12-01T12:00:00.000Z", "input_url": "https://www.realtor.com/realestateandhomes-search/Las-Vegas_NV" }
// GET /api/v2/realtor-agent-by-zipcode/?zipcodes=90210 // one item of data.agents · catalog sample { "agent_name": "Jane Doe, agent", "website": "https://www.realtor.com/realestateandhomes-agent/Jane-Doe", "email": null, "listing_count": 12, "sold_count": 47, "office_phone": "+1-310-555-0100", "mobile_phones": "+1-310-555-0101", "areas_serviced": "Beverly Hills, West Hollywood", "zip_codes_serviced": null, "office_company_name": "Beverly Hills Realty", "company_website": "https://www.beverlyhillsrealty.example", "review_count": 23, "agent_photo": "https://ar.rdcpix.com/xxx.jpg", "scraped_at": "2026-12-01T12:00:00.000Z", "input_zipcode": "90210" }
Every response is {"success": true, "data": {…}}: your input echoed back, the result under its own key (profile, posts, comments…) and next_cursor for the next page.
Public Realtor.com data powers housing market research, price change tracking, property data enrichment and real estate lead generation. Here are five common jobs, and the Realtor.com scraper endpoints each one chains together.
Pull every listing in a city search with price, beds, baths and size, then compare price per square foot across neighborhoods and home types.
Run the same search on a schedule and read lastPriceChangeAmount and lastPriceChangeDate. Catch price cuts the day they appear.
List the agents serving a ZIP code with office, phones, listing and sold counts, then sort by sales or reviews to build an outreach list.
Search an area, then pull full property records with year built, stories, coordinates, address and photos for your own database or valuation model.
Run property searches in RENT mode to see what rentals list at in an area, next to what homes sell for in BUY mode.
Realtor.com Scraper fetches clean, structured Realtor.com data at low cost: built for market research, price tracking, agent lead lists and AI agents.
Each request reads Realtor.com at call time, and records say when in scraped_at.
Same field names on every call: price, beds, baths and sqft as numbers, coordinates as latitude and longitude.
Every endpoint returns next_cursor; run up to 3 requests in parallel per key.
Set the location and filters on Realtor.com; the search URL carries them to the API.
The Scrapier MCP server reaches every endpoint from Claude Code, Cursor, Windsurf and VS Code with one command.
Plain REST: Python, Node.js, cURL, n8n, Make, Zapier or Google Sheets.
Sort agents by relevance, ratings and reviews, most sales or most recent activity.
When Realtor.com changes its pages, Scrapier updates the scraper; your field names stay the same.
1 credit per call, however many homes or agents the page holds. Failed calls are never billed.
Realtor.com has no public API for listing or agent data. Scrapier reads public Realtor.com search results, property pages and agent listings with one API key, at a price you know before the call runs.
Any non-2xx response is free, so retries cost nothing.
At 1 credit a call, the price of every Realtor.com endpoint.
Search, property details and agents all cost the same.
The same key and JSON envelope cover Zillow, Idealista, Airbnb, Google Maps and more.
| Feature | Scrapier Realtor.com Scraper | Official API | DIY scraper |
|---|---|---|---|
| Whose data | Any public listing or agent | No public API | Any public listing |
| Setup | One API key | No public API | Proxies, browsers, parsers |
| Maintenance | Handled by Scrapier | No public API | Breaks on layout changes |
| Cost | From $1.20 per 1,000 calls | No public API | Servers, proxies and engineering time |
| AI agents | MCP server included | No public API | Build your own |
No. Each endpoint returns one data type. To get listings and the agents who work the same area, call realtor-search-listings then realtor-agent-by-zipcode, or let an AI agent chain the calls over MCP.
No. Realtor.com does not offer a public API for its listing or agent data. Scrapier reads the public Realtor.com pages and returns typed JSON with one API key and one header.
realtor-search-listings returns compact rows from a search URL: price, status, beds, baths, size and last price change. realtor-property takes a search or detail URL and returns fuller records with address, coordinates, year built, stories and photos.
Send one ZIP code in zipcodes to realtor-agent-by-zipcode. Each agent comes with name, office and company, phones, areas served, listing and sold counts and review count. Sort with sort_by, for example MOST_SALES or RATINGS_REVIEWS.
As many as Realtor.com shows publicly. All three endpoints return a page at a time with next_cursor; pass it back as cursor for the next page. Each page is one call at 1 credit.
When Realtor.com doesn't show a value, the field is null, so you can tell "not shown" from zero. An agent's email or a listing's last price change, for example, can be null.
It depends on what you collect, where you are and how you use it, so this is not legal advice. Scrapier returns publicly visible data only. Agent names and phone numbers are personal data under GDPR or CCPA, so follow marketing rules when you contact them.
Yes. Any tool that can make an HTTP request works: n8n, Make, Zapier, Google Sheets, Airbyte or your own code. Send your key in the X-API-Key header and read the JSON response.
Yes. Run claude mcp add -t http scrapier https://mcp.scrapier.io/mcp with your key in an X-API-Key header. The agent finds the right Realtor.com endpoint with search_endpoints and calls it with run_scrape, in Claude Code, Cursor or Windsurf.
Check the status code first: 401 means the X-API-Key header is missing, 403 an invalid key, 402 no credits left, 429 too many requests (wait Retry-After seconds). If it's still wrong, report it with the request and the response.
Every live Realtor.com endpoint costs 1 credit per successful call, however many homes or agents the page holds. Failed calls are free. Plans: Hobby $29 for 15,000 credits, Pro $79 for 50,000, Scale $299 for 250,000, Enterprise custom. A free tier lets you try it first.
Run up to 3 requests in parallel per API key. If you go faster, the API answers 429 with a Retry-After header: wait that many seconds and retry. 429 and 5xx responses are never billed. These endpoints can run long, so set a client timeout of 210 seconds or more.
Use the requests library: requests.get("https://proxy.scrapier.io/api/v2/realtor-agent-by-zipcode/", headers={"X-API-Key": key}, params={"zipcodes": "90210"}, timeout=210). The response is JSON, so read r.json()["data"]["agents"] directly; there is no HTML to parse or proxy to run.
Free API key. No sales call, no proxy setup, and failed calls are free.