Realtor Sold Property API - Sale Dates and Available Prices

Search sold-property records by location, with documented price, room, property-type, size and minSoldDate inputs. Austin, TX with sort=newest was live-tested and returned status=true, message, a flat data array and resultsPerPage, totalResultCount, totalPages and currentPage. Observed rows include property_id, listing_id, status=sold, location.address, last_sold_date, nullable last_sold_price, list_price, list_date, description and photos. Keep list_price distinct from recorded last_sold_price, and do not interpret an absent sale price as zero. newest reflects listing ordering and did not necessarily mean the most recent sale date. pageSize=8 returned 30 rows; verify actual page contents and totals. The sale-date filter and other optional filters remain unverified, and this search is not a comprehensive historical transaction feed or a certified appraisal.

API Features

Observed Austin sold records The tested Austin query returned sold listings with property identities and Texas addresses.

Separate sale and listing measures last_sold_price and last_sold_date are different fields from list_price and list_date; sale prices can be null.

Sale-date interpretation For chronological sale research, inspect and sort available last_sold_date values locally rather than relying on newest.

Preliminary comparable inputs Documented room, size and property-type inputs can support evaluation of a shortlist, subject to filter validation.

Live API Demo

GET /api/project/realtor/property-search-sold

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/realtor/property-search-sold?key=<API_KEY>&location=Austin%2C+TX&sort=newest&page=1'

curl -X GET 'https://api.opendata-api.com/api/project/realtor/property-search-sold?key=<API_KEY>&location=Austin%2C+TX&sort=newest&page=1'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Prepare a preliminary sold-home comparison set while excluding missing sale prices from price calculations.
Export records sorted locally by available last_sold_date for a housing-research worksheet.
Audit differences between asking prices and recorded sale prices without treating the two as equivalent.
Track observed sold listings in selected markets without claiming complete sales-history coverage.

Frequently asked questions

Does sort=newest put the most recently sold homes first?

Not necessarily. The observed order did not always follow last_sold_date from newest to oldest. Inspect available sale dates and sort your collected sample locally when sale chronology matters.

How do list_price and last_sold_price differ?

list_price is an asking price; last_sold_price is an available recorded sale price. They are not interchangeable. A null sale price means unavailable, not a zero-price transaction.

Can this search produce a formal property appraisal?

It is not an appraisal service. Transaction completeness is not guaranteed, sale prices can be missing and filters need validation. Use it for preliminary human research, not as a substitute for qualified appraisal or licensed transaction data.

Related operations

Guides

View Subscription Plans →

Search Sold Homes and Available Sale Records