The PropertiesAPI blog
Turn property data into something useful. Build a research dashboard, enrich a spreadsheet, compare rental listings, and choose the API that fits your project.
Start here
Choose a real estate API for your actual workflow. Compare property lookups, listing feeds, records, estimates, field coverage, freshness, and billing.
Read the guideDevelopers and product teams
Choose a real estate API for your actual workflow. Compare property lookups, listing feeds, records, estimates, field coverage, freshness, and billing.
Developers and product teams
A free tier is an evaluation budget. Use it to test identity, missing fields, freshness, error billing and cache behavior on your own properties before you choose a real estate data API.
Developers and data teams
Turn a property list into a monthly lookup estimate: distinct homes, revisits, cache reuse and failures, then compare plan and prepaid costs with a small Python worksheet.
Developers and product teams
What an MLS API is, how listing feed access is granted through each MLS, and when a known-property Zillow lookup fits better. A sourced decision matrix for developers.
Developers and product teams
A dated, task-based comparison. RentCast offers records, its own rent and value estimates, listing search and market data; PropertiesAPI returns a known Zillow property page as JSON.
Developers and product teams
Compare a public-records property database with known-property Zillow lookups: ownership, deeds, assessments and valuations versus listing status, Zillow estimates and photos.
Developers
Build a local dashboard for a property shortlist using an API snapshot. Compare returned addresses, listing prices, estimates, errors, and collection times.
Rental research teams
What the rent Zestimate means, how it differs from the asking rent, and a Python report that compares the two for a list of rental properties.
Data teams
Turn an address spreadsheet into property data with a downloadable Python script. Keep prices, Zillow estimates, collection times, and every failed row.
Developers
Check a list of Zillow homes on a schedule, compare each new collection with the last one you stored, and send price or status changes to a Telegram chat without duplicate alerts.
AI agent builders
A worked research session with the PropertiesAPI MCP server: connect Claude, compare a shortlist of Zillow homes, handle an ambiguous address and check your remaining credits.
Investors and research teams
Build a comparison worksheet for a subject home and the comparable properties you chose: sale status, dates, size, price meaning and a column for your inclusion decision.
Rental investors and analysts
A Python gross rental yield calculator for a property shortlist that labels every input: your assumed price and rent, or the source's asking price and rent Zestimate, with expenses excluded.
Home buyers and analysts
A rent-vs-buy worksheet that keeps listing data, such as asking price, tax and HOA fee, apart from the financing, insurance and maintenance assumptions only you can supply.
Developers
Map the properties you already chose with Python, GeoJSON and Leaflet. Use returned coordinates, label every popup, keep missing locations visible and the API key on the server.
Developers and product teams
An import template and merge policy for adding property data to CRM records you already have: separate api columns, identity checks, conflict flags and no silent overwrites.
Data teams
Generate a printable property research report from a saved snapshot: source links, collection times, missing fields and analyst notes kept apart from the data, with no copied listing photos.
Developers
Build a server-backed address form with success, review and unavailable states. Keep the API key on the server, confirm ambiguous matches, and cap how many paid lookups visitors can start.
Developers
Was the Zillow API discontinued? What replaced the retired free API, which official Zillow data programs remain, and how to choose access for your app.
Developers
Build safer Zillow address lookups with unit numbers, identity checks, and explicit handling for ambiguous property matches.
Developers
Learn when to use a Zillow property ID, URL, or address, and how to preserve property identity across API requests and exports.
Data teams
Process multiple Zillow properties with the batch API, preserve row identity, and retry individual failures without losing successful results.
Data teams
A Postgres schema and Python importer for property snapshots: current rows, an append-only observation history keyed by collection time, and failed inputs kept for review.
Data teams
Search the description text of properties you already saved for features like a pool or a home office, quote the evidence for every match, and treat each hit as a lead for manual review.
Data teams
Deduplicate property address spreadsheets by confirmed property identity. Keep every original row, alias, warning and collection time, and leave unresolved inputs alone.
Data teams
Build a training table from timestamped property observations, split it by time, and audit every feature for information from after the prediction date. Check permitted use first.
Agents and inside-sales teams
Sort inbound real estate leads by current Zillow listing status in one Claude session: strip the CRM export, set the rules, run one MCP batch and review unclear rows.
Developers
Why is a Zestimate not available? What a missing Zestimate means, and how to keep null distinct from zero, asking price, and rent Zestimate.
Data teams
Interpret listing and sale events from Zillow price history without confusing them with a home-value time series or complete transaction record.
Developers
Handle Zillow listing photo URLs, empty galleries, changing images, and display permissions without treating API access as an image license.
Investors and research teams
Compare a sale listing's asking price with Zillow's Zestimate, handle missing values and non-sale statuses, and review each gap with a checklist instead of labelling homes as deals.
Data teams
Turn the taxHistory array into a clear table of tax paid, assessed value and yearly changes, and avoid treating an assessment as a market price or a complete tax record.
Developers
A status-by-status guide to price, lastSoldPrice, dateSold and the last Sold event, with code that keeps asking prices, rents and sale prices in separate columns and handles undisclosed sales.
Developers and product teams
When a lookup returns an apartment building, some fields describe the building and some describe one unit. An annotated field guide, with code to classify and key records safely.
Data teams
A field-by-field checklist for researching a known home that is not listed: what the estimates, sale history, facts and leftover listing details can tell you, and what they cannot.
Data teams
The API returns the current Zestimate, not its full history. Record timestamped observations, chart the changes you actually saw, and keep them apart from listing events.
Developers
Handle Zillow API validation, authentication, ambiguous addresses, quotas, and transient failures with a bounded retry policy.
Developers
Distinguish request time from collection time, read cache metadata, and set honest freshness rules for Zillow property data.
Developers
Test property identity, missing fields, batch failures, secret handling, and freshness before shipping a Zillow data integration.
Developers and product teams
Measure identity resolution and required-field availability on your own property sample, with a reproducible audit script, a written method, and limits on what the result can claim.
Developers
A benchmark harness that separates live lookups, cache hits, failures and client timeouts, reports percentiles only from your own runs, and publishes the method with the numbers.