Realtor Real Estate Listings

Affiliate disclosure: Apify links in this README may include referral parameters. If you sign up through one of them, TrueFetch may receive a commission at no extra cost to you.

Realtor Real Estate Listings turns a United States location search into structured Realtor.com listing records that can move directly into review, comparison, and monitoring workflows.

• Search one United States city, ZIP code, neighborhood, region, or address per run with explicit result limits.
• Choose sale, rental, or sold listings and optionally narrow by property type and posting window.
• Receive a stable 40-field dataset covering identity, pricing, rooms, area, location, media, contacts, source links, and processing metadata.
• Public Store proof is an old deployment snapshot: 26 total users, 2 monthly active users, 2 bookmarks, and one 5.0 rating observed on July 21, 2026; current repository behavior is documented from the code and schemas instead.

Run Realtor Real Estate Listings on Apify to test a small, permissioned search before building a recurring workflow.

What does Realtor Real Estate Listings do?

Realtor Real Estate Listings is a single-source Apify Actor for collecting property listing records exposed through Realtor.com search flows in the United States. You provide country, location, and max_results; the Actor routes that search to the Realtor integration, applies supported optional filters, normalizes returned records, and saves each accepted item to the run's default dataset.

The Actor is designed for listing-level work rather than a precomputed market report. A result can include the source listing ID, MLS ID when available, price, rooms, area, address, coordinates, images, feature lists, contact information, and the original listing URL. Individual source fields can be absent because publishers, agents, and listing types expose different details. The normalized envelope remains consistent so downstream code does not need a separate shape for every transaction type.

This Actor is not affiliated with, endorsed by, or operated by Realtor.com, Move, Inc., or the National Association of REALTORS®. It does not grant a license to collect or reuse source content. Realtor.com's current terms state that scraping and automated collection require express written permission and prohibit use of content for machine learning or artificial intelligence. Run this Actor only when your organization has the required permission or another valid legal basis, and review the terms again before each production deployment.

How do I run Realtor Real Estate Listings?

Start with one deliberately small search. Open the Actor input page, select United States, enter a specific location, keep max_results at 1, and choose only the filters your use case actually needs. Optional inputs are genuinely optional: leaving property_type or posted_since blank avoids adding that restriction. When listing_type is omitted, the runtime uses sale listings.

The shared example throughout this README is a permissioned Austin, Texas sold-home check:

{
  "country": "United States",
  "location": "Austin, TX",
  "max_results": 1,
  "listing_type": "sold",
  "property_type": "house",
  "posted_since": "30 days"
}

Run it once, inspect the dataset item and source URL, confirm that your authorization covers both collection and intended reuse, and only then increase the result limit. A successful run may legitimately return fewer records than requested when the source has limited matching inventory, removes listings during collection, or does not expose a requested optional attribute.

What data does Realtor Real Estate Listings return?

Each dataset item uses the 40-field public dataset schema. Values are populated when the corresponding information is present in the source response; nullable or flexible fields must not be treated as guaranteed. Representative output looks like this:

{
  "platform": "realtor",
  "title": "Example home in Austin, TX",
  "listing_id": "example-listing-id",
  "mls_id": "example-mls-id",
  "listing_type": "sold",
  "property_type": "house",
  "price": {
    "value": 625000,
    "currency": "USD"
  },
  "rooms": {
    "bedrooms": 3,
    "bathrooms": 2
  },
  "area": {
    "value": 1840,
    "unit": "sqft"
  },
  "location": "Austin, TX",
  "address": {
    "city": "Austin",
    "state": "Texas"
  },
  "cover_image": "https://example.com/property.jpg",
  "source_url": "https://www.realtor.com/realestateandhomes-detail/example",
  "processed_at": "2026-07-21T12:00:00Z"
}

The complete schema groups fields into listing identity (platform, title, description, listing_id, mls_id, source_url, official_url), classification (listing_type, availability, market_type, property_type, subtype, category, business_type), commercial and physical facts (price, rooms, area, land, building, dates, posted_time, fees), place data (location, address, geo, country, nearby), media and details (cover_image, image_urls, media, open_houses, features, amenities, details), people and policies (contact, reviews, policies, units), and processing metadata (processor, processed_at).

What inputs can I configure?

Input	Required	Accepted values and behavior
country	Yes	United States only. It selects the Realtor route.
location	Yes	A source-recognized city, region, neighborhood, postal code, or address.
max_results	Yes	Maximum dataset items to request; actual output can be lower.
listing_type	No	for_sale, for_rent, or sold; omission falls back to sale.
property_type	No	residential, house, apartment, condo, townhouse, land, new_development, or ready_to_build.
posted_since	No	A supported recency window; omission leaves the date restriction unset.

Use exact enum values when calling the API. Do not invent price, bedroom, or geographic-radius inputs: those controls are not part of this Actor's public schema. Property and date availability can vary with the selected listing type and source inventory, so validate returned records instead of assuming every source filter produces a field on every item.

What platforms and markets does Realtor Real Estate Listings cover?

This Actor supports one platform, Realtor.com, and one country, the United States. It is intentionally narrower than Global Real Estate Listings. The explicit scope is useful when a pipeline must remain source-specific, when teams want source URLs that can be reviewed in one familiar interface, or when collection rules and permissions are managed separately by publisher.

Location resolution still depends on what the source recognizes. City-and-state forms such as Austin, TX are a safe starting pattern; ZIP codes and more specific places can work when present in Realtor.com's search geography. The Actor does not promise national completeness, MLS completeness, historical snapshots, appraisal values, transaction records, ownership records, or off-market inventory. Realtor.com's separate Economic Research data library provides aggregated market series and is not the same product as the listing-level output described here.

Why use Realtor Real Estate Listings?

The main value is a predictable boundary around a variable listing source. A one-run dataset can feed a manual review queue; repeated authorized runs can supply comparison tables or change-detection jobs; source identifiers and URLs let analysts retain provenance while the common field layout reduces mapping work.

Typical permissioned workflows include reviewing comparable active or sold listings, monitoring a defined portfolio market, enriching an internal property record with a current public listing reference, and checking how specific source records change over time. Treat output as observational data, not professional valuation, brokerage, legal, lending, or investment advice. Material decisions should be confirmed against the source and qualified professionals.

The Actor also separates collection from analysis. That matters because a normalized dataset is not automatically accurate, complete, current, or licensed for every downstream purpose. Your application should preserve source attribution, record the collection time, handle missing values, and reject uses that exceed your permission.

Who is Realtor Real Estate Listings for?

It can fit data teams, real estate analysts, authorized brokerages, property managers, researchers, and software teams that need structured Realtor.com listing references and already have permission for the collection and reuse they plan. Developers can invoke the same input through the Console, HTTP API, Apify clients, schedules, webhooks, or an MCP-enabled tool.

It is not appropriate for users who lack the source's express written permission where required, plan to train or ground AI systems on Realtor.com content, intend to republish protected photographs or descriptions, or need guaranteed MLS coverage. It is also a poor fit for unattended high-volume collection before a small run has been reviewed for legality, cost, field quality, and source stability.

How can I use Realtor Real Estate Listings through the API or MCP?

The stable Actor API name is truefetch~realtor-real-estate-listings. Send the same JSON input to the run endpoint, keep your Apify token in a secret manager, and read results from the run's default dataset. The synchronous dataset-items endpoint is convenient for small calls; asynchronous runs are safer for larger work because clients can poll status and handle failure explicitly. See the official Apify API page for current endpoint examples.

For MCP clients, add the Actor by ID and expose only the tool needed by the client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=actors&actors=W2lvRDegavvqPn0Pr"
    }
  }
}

The Actor's MCP page shows the current configuration flow. Whether invoked through API or MCP, the same input schema, source restrictions, event pricing, and output caveats apply. Never place an API token in a README, client-side bundle, prompt, or committed configuration.

How much does Realtor Real Estate Listings cost?

Pricing is pay per event. An Actor start costs $0.01000. Each result saved to the default dataset costs $0.01350 on FREE, $0.01305 on BRONZE, $0.01260 on SILVER, and $0.01215 on GOLD, PLATINUM, or DIAMOND. The shared one-result Austin scenario therefore has a maximum Actor-event charge of $0.02350 on FREE, excluding any separate Apify platform usage or subscription charges that may apply.

Charges follow emitted events, not the number requested in the input. A run that starts but returns zero saved results still incurs the start event. A run that saves fewer results than max_results incurs result events only for the items actually pushed. Check the Actor's current Pricing tab before production because public prices can change after this README is updated.

How does Realtor Real Estate Listings compare with alternatives?

Choose this Actor when a Realtor.com-only United States pipeline and its six public inputs match the job. Choose Global Real Estate Listings when the same project needs selectable platforms or multi-country routing. Choose a dedicated Zillow, Redfin, Zoopla, Domain, or Rightmove Actor when that publisher is the actual source of interest and its market coverage matches your authorization.

Realtor.com's official Residential Real Estate Data Library is a different alternative: it publishes aggregated housing-market files and metrics with its own attribution instructions, while this Actor produces individual listing-shaped records. If aggregate inventory and price trends answer the question, the official research files may be more suitable and lower risk. Do not collect listing-level content merely because it is technically possible.

What are the limits and troubleshooting steps?

Source pages and internal responses can change without notice, fields can disappear, listings can be removed mid-run, and location or filter combinations can return no inventory. The Actor does not guarantee completeness, freshness, uninterrupted availability, or identical results across runs. Avoid interpreting a missing result as proof that a property is unavailable.

Before troubleshooting mechanics, confirm authorization. Realtor.com's current Terms of Use say that, without express written permission, users may not scrape or automate collection, and they prohibit machine-learning and AI use of content. The Actor does not override those terms. Review the current terms at https://www.realtor.com/terms-of-service/, applicable laws, privacy obligations, intellectual-property rights, and any contractual restrictions. Stop collection when permission is absent or uncertain.

For an authorized run: first retry the exact shared one-result input; then simplify optional filters; confirm the country spelling and location; inspect run logs and dataset count; open returned source URLs manually; and record the run ID, sanitized input, timestamp, expected count, actual count, and error message before contacting support. Do not send API tokens or unnecessary personal data.

Frequently asked questions

Does the Actor require a location?

Yes. country, location, and max_results are required by the current input schema.

Can it search rentals and sold homes?

Yes. listing_type accepts for_sale, for_rent, and sold. Available inventory and fields still depend on the source.

Are all 40 fields always populated?

No. The schema is a normalized envelope. Source availability determines which optional values are present.

Does paying for the Actor grant data rights?

No. Payment covers Actor events. You remain responsible for source permission, lawful collection, and downstream use.

Can I use the data to train an AI model?

Realtor.com's current terms expressly prohibit machine-learning and artificial-intelligence uses of its content. Do not use this Actor for that purpose unless the source provides specific authorization that legally permits your exact use.

Related TrueFetch Actors

• Global Real Estate Listings — selectable sources and broader country routing.
• Zillow Real Estate Listings — Zillow-focused searches in the United States and Canada.
• Redfin Real Estate Listings — Redfin sale-listing searches in supported North American markets.
• Zoopla Real Estate Listings — Zoopla-focused United Kingdom property searches.

Select an Actor because its documented source, market, inputs, and permitted use fit your workflow—not because a larger catalog implies broader rights.

Support and last updated

For a reproducible Actor problem, use the Actor Issues tab and include a run ID, sanitized input, expected result, actual result, and timestamp. Security or permission concerns should not be posted with sensitive details in a public issue.

Documentation last verified July 21, 2026 against the current repository's Actor configuration, input schema, dataset schema, pricing configuration, and read-only runtime path. Public Store usage figures above are explicitly retained as an older deployed snapshot, not evidence that the Store deployment and local repository are identical.

Open Realtor Real Estate Listings and run the one-result check.