Zillow Real Estate Listings avatar

Zillow Real Estate Listings

Pricing

from $12.60 / 1,000 results

Go to Apify Store
Zillow Real Estate Listings

Zillow Real Estate Listings

Search Zillow listings in the United States and Canada. Collect sale, rent, and sold property data with prices, beds, baths, area, images, location details, agent data, and source URLs.

Pricing

from $12.60 / 1,000 results

Rating

5.0

(1)

Developer

TrueFetch

TrueFetch

Maintained by Community

Actor stats

3

Bookmarked

32

Total users

7

Monthly active users

15 hours ago

Last modified

Share

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

Zillow Real Estate Listings is a focused Zillow property data Actor for exporting normalized sale, rental, and sold listing records from supported locations in the United States and Canada.

  • Two country markets are exposed by the current input schema: the United States and Canada.
  • Six public inputs control country, location, result count, transaction type, property type, and listing age.
  • Forty normalized Dataset fields cover pricing, rooms, area, address, images, dates, contacts, and source provenance.
  • The older public Store snapshot checked on 2026-07-21 showed 31 total users, 6 monthly active users, 3 bookmarks, and one 5.0 rating; it is historical public proof, not evidence of current code behavior.

Run a one-result test · View API

At the current FREE-tier prices in local metadata, a run that starts and stores one result costs at most $0.02400: $0.01000 for Actor Start plus $0.01400 for one Result. Matching inventory and field availability depend on Zillow at run time.

What does Zillow Real Estate Listings do?

Zillow Real Estate Listings accepts a country, location, and result limit, searches the supported Zillow market, and returns property records in a stable 40-field Dataset. It supports the Actor's verified for_sale, for_rent, and sold transaction modes. The normalized result can contain price information, bedrooms and bathrooms, floor and land area, location and coordinates, listing dates, images, features, contact details, and the Zillow source URL.

This Actor is an independent data collection tool and is not affiliated with or endorsed by Zillow. It does not provide a licensed MLS feed, a Zestimate or appraisal service, title information, transaction authority, or professional real estate advice. Users must review Zillow's current Terms of Use at https://www.zillow.com/corporate/terms-of-use/ and confirm that their intended access, retention, and use are permitted. Zillow's terms updated 2025-10-28 include restrictions on automated queries; using this Actor does not grant additional data rights.

How do I run Zillow Real Estate Listings?

  1. Open the Actor input page.
  2. Select United States or Canada, then enter a location Zillow can interpret, such as a city, neighborhood, postal code, or address.
  3. Set max_results from 1 to 10,000. For a safe first check, use 1.
  4. Optionally select the transaction type, property type, or posted-date filter. Leave optional inputs empty when they are not needed.
  5. Start the Actor, review the run status, and export the default Dataset.

All examples use one Denver house-for-sale scenario:

{
"country": "United States",
"location": "Denver, CO",
"max_results": 1,
"listing_type": "for_sale",
"property_type": "house",
"posted_since": "7 days"
}

This input requests no more than one matching Zillow listing. It can return an empty Dataset if no current result satisfies the location and filters.

What data does Zillow Real Estate Listings return?

The Actor's effective Dataset schema defines 40 fields. Zillow does not expose every attribute on every listing, so unavailable values are returned as null instead of being inferred.

Field groupFieldsWhat the group represents
Listing presentationcover_image, image_urls, title, descriptionPrimary visual, image collection, headline, and cleaned listing text.
Identity and statuslisting_id, mls_id, listing_type, availability, market_typeZillow identifiers, transaction type, and source status context.
Classificationproperty_type, subtype, category, business_typeNormalized and source-specific property classifications.
Money and measurementsprice, rooms, area, landNested price, bedroom/bathroom, interior area, and lot information.
Geographylocation, address, geo, countryDisplay location, address, latitude/longitude, region, city, and postal code.
Building and timingbuilding, dates, posted_time, feesBuilding characteristics, listing dates, market days, and available fee data.
Media and attributesmedia, open_houses, features, amenities, detailsTours, floor plans, open-house times, features, amenities, and structured details.
Community contextreviews, policies, units, nearbyRatings, policies, unit information, schools, transit, and nearby amenities when exposed.
Contact and sourcecontact, platform, source_url, official_urlAgent or agency data, source label, Zillow URL, and any explicit official outbound URL.
Processing recordprocessor, processed_atActor reference and UTC processing timestamp.

An abbreviated illustrative item for the Denver scenario can look like this:

{
"cover_image": "https://images.example.com/denver-house.jpg",
"title": "Three-bedroom house in Denver",
"listing_id": "987654321",
"listing_type": "for_sale",
"property_type": "House",
"price": {"value": 575000, "text": "$575,000", "currency": "USD"},
"rooms": {"beds": 3, "baths": 2},
"area": {"floor": 1680, "floor_unit": "sqft"},
"location": "Denver, CO",
"geo": {"lat": 39.7392, "lng": -104.9903, "city": "Denver"},
"platform": "zillow",
"source_url": "https://www.zillow.com/homedetails/987654321",
"processor": "https://apify.com/truefetch/zillow-real-estate-listings",
"processed_at": "2026-07-21T12:00:00+00:00"
}

The URLs, identifier, price, and property are examples for schema clarity, not a live Zillow listing.

What inputs can I configure?

InputTypeRequiredVerified behavior
countrystringYesAccepts Canada or United States.
locationstringYesAccepts a Zillow-supported city, region, neighborhood, postal code, or address.
max_resultsintegerYesReturns at most 1–10,000 Zillow records for the run.
listing_typestringNoAccepts for_sale, for_rent, or sold; omission uses for_sale.
property_typestringNoNarrows results to a supported residential or land category.
posted_sincedate/relative stringNoRequests listings within a date or relative period when Zillow supports that filter.

Property-type compatibility also depends on transaction mode. for_sale supports residential, house, apartment, condo, townhouse, land, new_development, and auction. for_rent and sold support residential, house, apartment, condo, and townhouse. An incompatible combination is rejected or produces no selected source rather than being silently changed.

What platforms and markets does Zillow Real Estate Listings cover?

This Actor is intentionally single-platform: it searches Zillow only. The input schema and current route map expose the United States and Canada. Location semantics remain Zillow-dependent, and country availability does not mean every city, property type, transaction mode, or historical record is present.

Zillow Research uses distinct vocabulary for market aggregates such as the Zillow Home Value Index and Zillow Observed Rent Index. This Actor does not return those research indices; it returns listing-level records from the supported search surface. For aggregate market series, consult Zillow Research at https://www.zillow.com/research/data/ under its applicable terms. For listing records, retain country, platform, and source_url so downstream users can distinguish the source and verify context.

Why use Zillow Real Estate Listings?

Capability verified from the current ActorBenefit for a data workflow
Zillow-only scopeKeep a focused source-specific run instead of searching unrelated marketplaces.
Sale, rental, and sold modesUse one public schema for several Zillow transaction contexts.
Optional posted-date filteringBuild a recent-listing check when Zillow supports the requested window.
Forty normalized fieldsStore identity, price, space, media, contact, and provenance in a predictable model.
Nullable source-aware outputAvoid fabricated values when Zillow does not expose an attribute.

The trade-off is that a narrow source is easier to reason about but cannot provide independent marketplace corroboration. Use source URLs for verification and consider a multi-source Actor when comparisons across marketplaces are part of the research question.

Who is Zillow Real Estate Listings for?

The Actor fits developers and analysts building authorized property research, inventory review, lead qualification, location monitoring, or internal data enrichment. A brokerage analyst might sample recent sale listings for a Denver review queue; a product team might inspect how bedrooms, price, area, and coordinates arrive in one Dataset; a researcher might build a source-linked set of current listings for manual verification.

The Actor is not appropriate for users seeking permission to republish Zillow content, a complete MLS database, regulated appraisal evidence, a substitute for licensed professional advice, or any use prohibited by Zillow or applicable law. The user remains responsible for lawful access, data minimization, retention, and downstream use.

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

The public Actor slug is truefetch/zillow-real-estate-listings, and the current Store console resolves it to Actor ID bdFppjxrVjQpbiLmo. Use the official Actor API page for generated SDK and OpenAPI examples.

Run the same Denver scenario synchronously with HTTP:

curl -X POST "https://api.apify.com/v2/acts/truefetch~zillow-real-estate-listings/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"country":"United States","location":"Denver, CO","max_results":1,"listing_type":"for_sale","property_type":"house","posted_since":"7 days"}'

Apify's current MCP page selects the Actor by slug through the hosted server:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com/?tools=truefetch/zillow-real-estate-listings",
"headers": {"Authorization": "Bearer <APIFY_TOKEN>"}
}
}
}

After connecting, invoke the selected Actor with the same Denver JSON input. Keep the token secret and use a one-result test before raising limits.

How much does Zillow Real Estate Listings cost?

The current local metadata declares two billed events. Verify the live pricing tab because Store prices can change.

EventFREEBRONZESILVERGOLDPLATINUMDIAMONDUnit
Actor Start$0.01000$0.01000$0.01000$0.01000$0.01000$0.01000One event when the Actor starts.
Result$0.01400$0.01353$0.01307$0.01260$0.01260$0.01260One listing stored in the default Dataset.

At the FREE tier, one stored result costs $0.01000 + (1 × $0.01400) = $0.02400. If the run stores no result, it incurs the start event but no Result event. Raising max_results increases the possible number of billed Result events.

How does Zillow Real Estate Listings compare with alternatives?

OptionUse it whenImportant trade-off
Zillow Real Estate ListingsZillow is the intended source and a normalized export is neededSingle-source coverage and source-dependent nulls.
Global Real Estate ListingsThe same location should be checked across compatible marketplacesA broader run can return more results and cost more.
Manual Zillow browsingA person needs to inspect a few listings under permitted useRepetition and structured export are limited.
Licensed MLS or commercial feedContractual rights, defined completeness, or service levels are requiredSeparate licensing, fees, and data models apply.
Zillow Research datasetsAggregate indices and published market series are the goalThese are not listing-level results from this Actor.

Choose based on rights and research scope first. A convenient normalized schema does not replace source permission or a licensed data agreement.

What are the limits and troubleshooting steps?

Symptom or limitExplanation and next step
The Dataset is emptyTry max_results: 1 with fewer optional filters and a broad city or postal-code location.
The input is rejectedConfirm the country, integer result limit, transaction value, and property type match the public schema.
A property-type combination failsUse the transaction-specific compatibility listed above or omit property_type.
Fields are nullZillow did not expose those attributes for the listing. Keep fields nullable and verify the source page.
A sold or rental search differs from sale resultsEach transaction mode has different inventory and supported property types. Do not compare counts as equivalent populations.
A source page changes after collectionListing data is time-sensitive. Preserve processed_at and recheck source_url before relying on a value.

For a reproducible support request, provide the run URL, sanitized input, expected behavior, and one relevant source URL. Never include an API token or private personal data. Public Store and review numbers cited above are an older deployment snapshot and must not be used to infer the state of the current local implementation.

Frequently asked questions

Does the Actor support both the United States and Canada?

Yes. Those are the two countries in the effective input schema and route map.

Can I search rentals and sold homes as well as homes for sale?

Yes. Use for_rent, sold, or for_sale. Available inventory and compatible property types differ by mode.

What happens when I omit listing_type?

The current input validation uses for_sale. No other optional filter is invented when omitted.

Can I request new developments or auctions?

Yes for for_sale. Those property types are not accepted for the current rental or sold compatibility sets.

Does posted_since guarantee that every result was posted in the period?

No. It requests Zillow's supported date filtering; source behavior and listing timestamps remain authoritative.

Are Zestimate values guaranteed in every result?

No. The public Dataset has a flexible nested price object, but availability depends on the source listing. This Actor is not a Zestimate API.

Can the same property appear more than once over time?

Yes. Listings can change or be relisted. Use listing_id, source_url, transaction context, and processing time in downstream deduplication.

May I republish the returned images or descriptions?

The Actor does not grant those rights. Review Zillow's terms and obtain any permission required for your use.

Support and last updated

This README was verified on 2026-07-21 against the effective local schemas, read-only runtime evidence, current Apify API/MCP pages, Zillow's official research vocabulary, and Zillow's terms updated 2025-10-28. The Store page, API page, pricing tab, and Issues page are the formal Actor links. Online Store content is treated as an older deployed snapshot, not as current code truth.

For help, contact the TrueFetch community or direct support with a sanitized one-result reproduction.

Run a controlled one-result check · Review the API options