Realtor.com recently sold homes

GET https://api.api.sh/realtor/v1/sold
1 credit / call real estate try it in the playground →

Recently sold homes in a city, ZIP code, neighborhood, county or address: sold price and date, list price, last sale, beds, baths, square feet, lot, year built, type, description, address, coordinates, county, MLS, listing agents and brokers and photos, newest sale first by default. Takes the same filters as the home search. total is the number of matches; pass next_page back as page (null on the last page; up to 50 pages of limit).

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
locationrequired string City, ZIP code, neighborhood, county or address. Example: Austin, TX
sold_within_days integer Only homes sold in the last N days. Example: 365
min_price integer Minimum sold price.
max_price integer Maximum sold price.
beds integer Minimum bedrooms.
max_beds integer Maximum bedrooms.
baths integer Minimum bathrooms.
max_baths integer Maximum bathrooms.
min_sqft integer Minimum square feet.
max_sqft integer Maximum square feet.
min_lot integer Minimum lot size (square feet).
max_lot integer Maximum lot size (square feet).
min_year_built integer Earliest year built.
max_year_built integer Latest year built.
property_type string Comma-separated property types (single_family, condos, townhomes, multi_family, mobile, land, farm, duplex_triplex, apartment, coop).
radius integer Search radius in miles around the location.
sort sold_newest | sold_oldest | price_asc | price_desc | sqft_desc | lot_desc Order (default sold_newest).
limit integer Homes per page (default 20, max 200). Default: 20
page integer Results page. Pass next_page back here. Default: 1
photos boolean Include every photo of each home.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/realtor/v1/sold?location=Austin%2C+TX" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.