PropData■API
Aerial view of a suburban neighborhood with winding streets and clearly visible house lots

NATIONAL MLS DATA · RESO-STANDARD API

Every listing in America. One API.

Live MLS listing data — listings, photos, agents, and market intel — from 250+ boards, coast to coast, through a single standards‑based interface.

60M+ listings
250+ MLS boards
Live refresh as boards update
RESO Data Dictionary standard
01

What you get

One connection to the whole market — no per-board contracts, no brittle scrapes, no stitched-together datasets.

01·1

Live listings

Every board we carry, delivered as it changes — status, price, photos, open houses. Refreshed continuously, so what you show is what the market is.

CONTINUOUS REFRESH · COAST TO COAST
01·2

Property context

The full picture around a listing: parcel facts, schools, district boundaries, and neighborhood demographics — the layers that turn an address into a decision.

PARCELS · SCHOOLS · DEMOGRAPHICS
01·3

Market intel

Aggregated trends by city, county, and zip — price series, inventory, and days-on-market signals. Clean enough to feed AVMs, portals, and analytics products.

AVM-GRADE · MARKET-WIDE
02

Speak the standard

PropData is built on RESO — the Data Dictionary and Web API the real-estate industry already standardizes on. Your integration speaks the industry's native language from day one, over whichever surface fits the task.

02·1

One vocabulary

Every board speaks its own dialect — status codes, field names, property types. PropData normalizes all of it to the RESO Data Dictionary, so one integration works everywhere we have coverage, and your code never learns a local dialect.

DATA DICTIONARY 2.1 · STANDARD ENUMS
02·2

Query it like RESO

The full OData query surface: filter, select, order, expand, and page — the skills your team already has transfer directly. Geospatial filtering is built in, by radius, bounding box, or polygon, for map-driven products.

$FILTER · $EXPAND · GEO.INTERSECTS
02·3

Or just use REST

The same data over plain REST and JSON — camelCase fields, predictable resources, nothing to learn. Lighter for product work, friendlier for quick scripts. Use both, interchangeably, against the same catalog.

REST · JSON · INTERCHANGEABLE

Standards where you want them. Simplicity where you don't.

03

From parcel to portal

A contemporary detached house in a suburban neighborhood

Comprehensive, continuously refreshed MLS data is the raw material of prop‑tech. Teams use PropData to power IDX websites, national portals, iBuying models, tenant screening, and market analytics — without maintaining a single board relationship.

IDX-ready · media included · agent & office data · national footprint

Build on the whole market.

Evaluation keys to start, enterprise terms when you ship.

Get API access