Realtor.com and Apartments.com data from one API
For-sale and rental are separate markets with separate portals, and a rent-versus-buy answer needs both sides measured the same week. One key covers them, with Realtor's estimates and market trends on the sale side.
Realtor.com's data programmes are partner and MLS-gated; Apartments.com publishes none. Neither is available to a developer who simply wants to read the public listings.
Coverage
What the two engines give you
- Realtor.com
- search, detail, estimates, sold, market_trends, comps, autocomplete
- Apartments.com
- search, property/detail, locations
- Sale side
- for-sale, sold, comps and trends
- Rental side
- rental inventory at building level
Worked example
Rent versus buy in one metro
The sale side gives the price and the trend; the rental side gives the yield.
- 1
POST /realtor/v1/searchfor-sale inventory in the metro
- 2
POST /realtor/v1/market_trendswhere that market has been moving
- 3
POST /apartments/v1/locationsresolve the metro on the rental side
- 4
POST /apartments/v1/searchrental asking prices for the same area
Asking prices and rents for one metro, measured in the same week.
Before you join them
Where the two sources genuinely differ
| realtor | apartments | |
|---|---|---|
| Unit | a property | a building, often with many units and a rent range |
| History | sold and comps | no sold history — rentals do not transact publicly |
| Estimates | estimates endpoint | none |
| Depth | 7 actions | 3 actions |