October 24th, 2025
New Functionality
For the matched person on the SkipTrace call, we are now sorting the list of phone numbers based on phone usage & last seen data that is part of this dataset
This should improve call metrics for teams calling on only the first 1-2 numbers
the “isConnected” field on the phone objects was always fixed and now updates along with the same phone usage data
there were also a few cases where phones were duplicated - this has been addressed and the phoneList is now deduped
October 13th, 2025
New Functionality
Some comps are drastically differently priced in some areas solely on the type of material that is used to build the house. To account for this, we now support using the “same_construction_type” [bool] filter on the input
{
"id": "252442669",
"max_radius_miles": 5,
"max_results": 10,
"same_construction_type": true
}When the subject property propertyInfo.construction is “null”, then the filter is ignored and the comps can have any construction type value
if the subject property does have a propertyInfo.construction field, then all comps will have the same value for that field
The construction field is not returned on the comps response object, but is for in the .subject object. If you want to verify, use the property ID of a comp and do the Property Detail lookup
October 6th, 2025
New Functionality
The following query would only return records that have owner1FirstName and owner1LastName’s that are not null
{
"exists": {
"owner1_first_name": true,
"owner1_last_name": true
}The following fields are now allowed in the “exists”:
owner1_first_name
owner1_last_name
owner1_full_name
owner2_first_name
owner2_last_name
owner2_full_name
September 18th, 2025
Modified Response Schema
New Functionality
propertyInfo.buildingCondition on Property Detail response — Possible values: POOR, FAIR, GOOD, EXCELLENT, UNSOUND, AVERAGE.
Coverage on 70M+ buildings
can also search on Property Search by “building_condition” with one of the aforementioned values
September 17th, 2025
Documentation
Previously, the swagger docs found here only had the request fields & types
Now supports response fields and types, updated on every push from our codebase so it’s dynamic and you won’t have to wait for release notes/documentation updates:
September 16th, 2025
stronger matching mechanism to help with edge cases
September 15th, 2025
Bug Fix
Loan Type Codes: https://developer.realestateapi.com/reference/loan-type-codes#/
CPI & RFA removed (deprecated)
4, 7, G, K, Q, P, T, U, W, X now functional as Property Search params (bug fix)
Applies to loan_type_code_first, loan_type_code_second, loan_type_code_third
September 3rd, 2025
Made some backend architectural changes that should drastically improve performance per request, performance across many requests, and more error resiliency
August 31st, 2025
Bug Fix
Fixed bug where searches with the “city” param included were not working properly - everything fully functional as of 8/31/25
August 25th, 2025
Similar to changes made to MLS Search earlier in August 2025. Getting towards a more standardized address scheme across the MLS data, which proved to be a little bit of a different challenge than the county address data standardization