Realtor Listings API

Realtor Listings API is a realtor.com listings api that searches Realtor.com by location and returns 40 normalized, source-linked property fields for developers and analytics teams working with United States listings.

• 40 public Dataset fields cover listing identity, classification, price, dimensions, location, media, contacts, provenance, and processing time.
• 7 public inputs with four required fields make country, location, transaction, and result limits explicit.
• the United States coverage follows the verified fixed-route or country-routing map instead of claiming universal availability.
• Pay-per-event billing is $0.01000 per Actor Start plus $0.01350 for each Result stored on the FREE tier.

Run a one-result test · View API

Set max_results to 1 for the smallest useful test; if one listing is stored, the FREE-tier maximum is $0.02350, while a no-result search still incurs Actor Start.

What does Realtor Listings API do?

Realtor Listings API converts one explicit property search into source-attributed rows that share a stable 40-field Dataset shape. It resolves the requested location, applies only supported filters, collects accepted public advertisements, and normalizes their source values for API, MCP, and export workflows.

One record can include listing IDs, transaction and property classifications, nested price and room data, areas, address and coordinates, images, features, dates, agent or agency details, the source platform, and a URL back to the advertisement. Missing details remain empty; the Actor does not estimate a price, infer a person, or fill a field from a different listing.

This is an independent public-listing search interface. It is not an MLS feed, valuation model, due-diligence service, official partner API, or guarantee that every source exposes the same inventory. Realtor.com is the official source reference used here: Realtor.com's official sitemap distinguishes homes for sale, rentals, new construction, foreclosures, and recently sold homes.

How do I run Realtor Listings API?

Run Realtor Listings API by providing max_results, country, location, and listing_type, then start with a one-result request.

1. Open the Actor input.
2. Use the working Austin, TX scenario and reduce max_results to 1.
3. Leave optional fields empty unless this edition documents that the source route supports them.
4. Start the run and inspect the terminal returned-property count.
5. Open the default Dataset and verify platform, location, price, and source_url before scaling.

{
  "max_results": 1,
  "country": "United States",
  "location": "Austin, TX",
  "listing_type": "for_sale"
}

max_results is a ceiling on accepted rows, not a guaranteed count. A valid run can return zero rows when no public listing matches, the place cannot be resolved, or a supplied filter is incompatible with the route.

What data does Realtor Listings API return?

Realtor Listings API returns one normalized Dataset row for each accepted property advertisement, using exactly 40 top-level fields.

Group	Fields
Identity, media, and classification	cover_image, image_urls, title, description, listing_id, mls_id, listing_type, availability, market_type, property_type, subtype, category, business_type
Price and size	price, rooms, area, land
Place and timing	location, address, geo, country, building, dates, posted_time
Listing detail	fees, media, open_houses, features, amenities, details, reviews, policies, units, nearby
Contact and provenance	contact, platform, source_url, official_url
Processing	processor, processed_at

The following JSON is abbreviated and illustrative; a real result follows the full 40-field schema and can contain additional nested values or nulls:

{
  "title": "Illustrative Austin, TX property listing",
  "listing_id": "source-12345",
  "listing_type": "for_sale",
  "property_type": "apartment",
  "price": {
    "value": 750000,
    "text": "750,000",
    "currency": "USD"
  },
  "rooms": {
    "beds": 2,
    "baths": 2
  },
  "location": "Austin, TX",
  "country": "United States",
  "platform": "realtor",
  "source_url": "https://example.com/property/source-12345",
  "processed_at": "2026-08-10T12:00:00.000Z"
}

source_url is the primary verification path, while platform, processor, and processed_at preserve provenance. JSON keeps nested objects intact; CSV and Excel are convenient for review; the Dataset API supports downstream jobs that need paginated items.

What inputs can I configure?

Realtor Listings API exposes 7 public inputs in the shared family order. max_results, country, location, and listing_type are required in every edition; property_type, posted_since, and platforms remain present and optional even when a fixed route requires them to be left empty.

Parameter	Type	Required	Description	Example
max_results	integer	Yes	Maximum number of property listings to return from Realtor.com	4
country	string (1 schema option)	Yes	Fixed market for Realtor.com: United States.	United States
location	string	Yes	City, region, neighborhood, postal code, or address to search on Realtor.com	Miami, FL
listing_type	string (3 schema options)	Yes	Transaction types supported by Realtor.com: for_sale, for_rent, and sold.	for_sale
property_type	string (8 schema options)	No	Optional Realtor.com property-type filter: residential, house, apartment, condo, townhouse, land, new_development, and ready_to_build. Leave empty for no property-type restriction.	optional
posted_since	string	No	Optional listing-age filter supported by the fixed Realtor.com route. Accepts YYYY-MM-DD or a relative value such as 7 days.	optional
platforms	array (1 schema option)	No	Compatibility selector retained across every property-family edition. This edition always uses Realtor.com; leave empty or select Realtor.com.	optional

The effective console prefill is:

{
  "max_results": 4,
  "country": "United States",
  "location": "Miami, FL",
  "listing_type": "for_sale"
}

The platforms field is intentionally retained with the singleton schema value Realtor.com. Runtime identity fixes this edition to Realtor.com; the field is not deleted merely to differentiate the product.

property_type and posted_since affect requests only when explicitly supplied with a value supported by this route.

What platforms and markets does Realtor Listings API cover?

Realtor Listings API covers Realtor.com in the United States, subject to the source map and the transaction modes documented for this edition.

• Platform: Realtor.com.
• Markets: the United States. The fixed Realtor.com route accepts United States locations.
• Transactions: for_sale, for_rent, and sold.
• Property type: residential, house, apartment, condo, townhouse, land, new_development, and ready_to_build.
• Posted date: supported by the Realtor.com route.
• Output language: source text is preserved where available; schema keys remain stable English identifiers.

Coverage describes the route the Actor can request, not a promise that every neighborhood has current inventory. Source ranking, advertiser participation, field population, and listing freshness remain external conditions.

Why use Realtor Listings API?

Use Realtor Listings API when a stable, source-linked API row is more useful than repeating a manual search or maintaining a source-specific parser.

Capability	Practical benefit
40-field normalized Dataset	Build one validation and export layer for identity, price, location, media, contacts, and provenance.
Explicit country and location	Make the requested market reviewable in logs and saved inputs.
Bounded max_results	Start with one row and increase collection only after inspecting quality.
Result-event billing	Relate output cost to rows actually stored in the default Dataset.
API and MCP access	Reuse the same Actor ID in code, agents, Make.com, n8n, or scheduled workflows.

The main trade-off is source dependence. Source inventory, ranking, and optional fields can change independently of the normalized API contract. The normalized envelope reduces integration work, but it cannot manufacture unavailable fields or contractual data rights.

Who is Realtor Listings API for?

Realtor Listings API is for developers, property-data teams, market researchers, and operations analysts who can work with nullable, source-attributed public advertisements.

• Data engineers can land JSON rows in a warehouse and validate source coverage before expanding a schedule.
• Market analysts can compare visible prices, rooms, area, and location for Austin, TX without treating the sample as the whole market.
• Product teams can prototype source-linked search experiences while keeping verification URLs in the record.
• Operations teams can create a bounded review queue from max_results, listing_type, and explicit location inputs.
• Quality teams can measure field fill rates and source changes against the named 40-field contract.

The reverse persona is equally important: Choose a permissioned listing feed when your application requires licensed redistribution or service-level guarantees. Do not use this Actor as the sole basis for housing eligibility, lending, valuation, investment, legal, or safety decisions.

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

Call Realtor Listings API with real Actor ID W2lvRDegavvqPn0Pr or the name form truefetch/realtor-listings-api; both refer to this public Actor.

curl -X POST "https://api.apify.com/v2/acts/W2lvRDegavvqPn0Pr/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"max_results": 1, "country": "United States", "location": "Austin, TX", "listing_type": "for_sale"}'

For MCP, connect the official Apify MCP server, select Actor W2lvRDegavvqPn0Pr, and submit the same one-result JSON input. Name max_results, country, location, and listing_type in the tool call rather than referring to a distant example. After completion, read the run's default Dataset and retain source_url for review.

The live API page provides generated SDK and OpenAPI examples. In Make.com or n8n, use W2lvRDegavvqPn0Pr in the run step, wait for a terminal run state, then fetch items with defaultDatasetId.

How much does Realtor Listings API cost?

Realtor Listings API costs $0.01350 per Result on the FREE tier, and the smallest one-result test costs at most $0.02350 including the $0.01000 Actor Start.

Plan tier	Price per Result
FREE	$0.01350
BRONZE	$0.01215
SILVER	$0.01080
GOLD	$0.01013
PLATINUM	$0.01013
DIAMOND	$0.01013

The billing unit is one property listing stored in the default Dataset. The exact smallest calculation is $0.01000 Actor Start + 1 × $0.01350 Result = $0.02350. A valid search with no stored rows still pays Actor Start but has no Result event.

Prices can change, so confirm the live pricing page before scheduling or increasing max_results.

How does Realtor Listings API compare with alternatives?

Realtor Listings API is best when a bounded API request and normalized source-linked rows are the priority; other paths fit different rights and reliability needs.

• Manual browsing is efficient for a handful of listings that one person will inspect immediately, but not for repeated structured comparison.
• The source's own website is best for interactive maps, saved searches, alerts, and consumer browsing. Realtor.com is the official source reference used here: Realtor.com's official sitemap distinguishes homes for sale, rentals, new construction, foreclosures, and recently sold homes.
• Separate official integrations are better when authenticated features, licensed redistribution, complete inventory, or service levels are mandatory.
• Valuation and analytics services are better for modeled prices, forecasts, or due-diligence outputs; this Actor returns advertisements, not an appraisal.

Source inventory, ranking, and optional fields can change independently of the normalized API contract. Choose another path if nulls are unacceptable, the use requires a license this Actor cannot grant, or a source outage must never interrupt the workflow.

What are the limits and troubleshooting steps?

The main limits are source-dependent inventory, filter compatibility, location resolution, nullable fields, and public-page availability.

• Zero rows → no match or unresolved location → rerun Austin, TX with max_results=1, verify the country and spelling, and remove one optional filter at a time.
• Filter is skipped → route lacks that capability → follow this edition's schema-supported listing, property-type, and posted-date choices.
• Fewer rows than requested → accepted inventory ended first → treat max_results as a ceiling and inspect the run log.
• Null values → source did not expose reliable detail → keep null-safe downstream types and verify important facts at source_url.
• Intermittent failure → source response or controls changed → retry the smallest scenario once, then report a reproducible run instead of repeatedly increasing retries.

Open the Issues page with the run ID, sanitized one-result input, expected behavior, actual behavior, and UTC timestamp. Never post an API token, private permission document, or personal data in a public issue.

Frequently asked questions

Realtor Listings API answers the most common questions about credentials, location inputs, nullable fields, schedules, result ceilings, and billing.

How do I use a realtor.com listings api without partner access?

Use W2lvRDegavvqPn0Pr with the one-result JSON input and an Apify token; no separate source credential is an input to this Actor. This describes the Actor's interface, not permission or an official partnership with the source.

Can I get realtor.com property listings by location?

Yes. Set the supported country, enter a source-valid location, choose a supported listing type, and keep max_results=1 until the returned platform, location, and source_url are correct.

Is there a free real estate listings API?

There is no zero-cost promise in this Actor's pricing. Apify account credits may cover testing, but the FREE pricing tier still defines a $0.01000 Actor Start and $0.01350 per stored Result.

Can I schedule runs to monitor property listings over time?

Yes. Use Apify Schedules with the same explicit input and compare listing_id, price, availability, and processed_at across Datasets. The Actor does not maintain history or send change alerts by itself.

Why do some fields remain null?

The source advertisement may omit them or a detail page may be unavailable. The 40-field schema is stable, but populated values vary by source, advertiser, market, and listing type.

Does max_results guarantee the requested count?

No. It limits accepted output; it does not create matching inventory. Zero or partial results can be correct outcomes for a narrowly filtered or unavailable search.

Is Realtor Listings API an official Realtor.com API?

No. It is an independent TrueFetch Actor that normalizes public listing search data. It does not provide affiliation, endorsement, partner credentials, licensed feed rights, or permission for a particular reuse.

Related TrueFetch Actors

These three TrueFetch Actors are the closest alternatives to Realtor Listings API, each for a distinct source or coverage decision.

• Real Estate Listings API — narrows the workflow to its source-specific search contract.
• Zillow API — covers an adjacent market with the same 40-field Dataset shape.
• Redfin API — provides the closest alternative route for cross-source comparison.

Support

Get product details from the Store page, generated endpoints from the API page, and current prices from the pricing page. Report reproducible defects on the Issues page with a sanitized input and run ID; ask general questions in the TrueFetch community.

Run a bounded one-result search · Review the API contract

Last Updated: August 10, 2026