RealEstateAPI Documentation
Property data APIs for PropTech and business applications. Query the nationwide public-record file, live MLS listings, lender-grade valuations, parcel boundaries, and owner contact data — all over JSON endpoints that take one API key and a POST body.
Getting started
Every endpoint is a POST to https://api.realestateapi.com authenticated with an x-api-key header. Get a key from the portal, then make your first call — the shortest useful path is Property Detail against an address you know.
Most integrations end up following the same two-step shape: use Property Search to find the properties you care about, then Property Detail to enrich the ones you keep. Searching is cheap when you use count and ids_only; enrichment is what spends credits. Paging and result modes covers how to keep that bill down.
Guides
Paging & result modes
Page through results, and use count, ids_only, and summary to spend fewer credits.
Resources
Property Detail
Pull the full county and public-record profile for a single address, APN, or property ID.
Property Search
Build lists across 150+ filters, take counts before you spend credits, and page through results.
Property Boundaries
Fetch parcel geometry as GeoJSON by address, lat/lng, APN+FIPS, or an enclosing polygon.
Datasets
The endpoints group into six datasets. Plans grant access per dataset, so which ones you can call depends on your subscription.
| Dataset | What it covers | Start here |
|---|---|---|
| Property data | 160M+ nationwide parcels — ownership, tax, mortgage, lot, building | Property Detail |
| MLS | Live and historical listings, agent and office data, media | MLS Search |
| Valuations | Lender-grade AVM and tunable comparable sales | Lender Grade AVM |
| Boundaries | Parcel geometry as GeoJSON, plus map pins | Property Boundaries |
| People | Owner contact details, demographics, corporate ownership | SkipTrace |
| Pipelines | Saved searches, daily change files, CSV exports | Saved Searches |