Changelog

Endpoints affected: v1/SkipTrace, v1/SkipTraceBatch , v1/SkipTraceBatchAwait

Release Date: 03.20.2025

🎉 What's New:

• Improved Match Accuracy

  We’ve enhanced our matching algorithms for skip trace lookups, resulting in more accurate and relevant contact information for provided addresses or persons.

• Response Enrichment

  • Responses schema now includes additional data, such as up to 3 email addresses where available, doNotCall indicator on phone numbers, and a more accurate isConnected indicator driven by phone usage metrics.

  • Response schema now include additional metadata, such as last_seen dates to indicate when demographics or contact details were last updated.

  • The addressHistory array now returns with the person’s previous address instead of an empty array.

  • More accurate and tighter age and dob ranges for demographics profiles.

• Performance Enhancements

  • Reduced average response time to around 200ms.

  • Improved resilience under high load conditions.

👩‍💻 Deprecations / Changes:

• addressHistory field is now an array of objects where data is available instead of an empty array.

• doNotCall field for phone numbers is now a boolean instead of an empty string.

• lastSeen dates are now filled with the last update date for the given data point instead of empty strings.

👾 Bug Fixes:

• Fixed occasional timeout issues with large batch requests on v1/SkipTraceBatchAwait.

If you have the Lender Grade AVM add-on, you are eligible to request access to this new endpoint that will let you fetch up to 100 highly accurate valuations per API call.

This should improve user performance times when fetching the Lender Grade AVMs for a large set of Property Search results for example.

Check out the documentation and email us at support@realestateapi.com if you want to add the Bulk Lender Grade AVM API:

https://developer.realestateapi.com/reference/bulk-lender-grade-avm-api

Use the input param “listing_property_type”, which can accept the following values:

https://developer.realestateapi.com/reference/listing-property-type

The following query would get all Rental listings in Richmond, VA

{
    listing_property_type: "RENTAL",
    city: "Richmond",
    state: "VA"
}

The following query would get all Commercial for Sale listings in Richmond, VA

{
    listing_property_type: "COMMERCIAL",
    city: "Richmond",
    state: "VA"
}

To get multiple listing property types (e.g. the multiple types of Commercial) in one query, use the following compound query syntax:

{
    city: "Richmond",
    state: "VA",
    "and": [
        "or": [
            { listing_property_type: "COMMERCIAL" },
            { listing_property_type: "COMMERCIAL_FOR_LEASE"},
            { listing_property_type: "BUSINESS_OPPORTUNITY"},
        ]
    ]
}

• some users when filtering for taxLien: true and other conditions in compound queries - needed the “taxLien” field in the response schema to prevent having to make hundreds of extra API calls to Property Detail to get it

• added in the “comps” response objects the following response fields:

  • taxAmount

  • taxAssessedValue

• also addressed a typo on the field “estimateedMortgageBalance”

  • has been corrected to “estimatedMortgageBalance”

We had an update in late October that affected the “propertyInfo.address.label” field.

Addresses for units were showing up with formatting like:

103 Main St 10, Pepperell, MA 01463

After this update, addresses have been reverted back to the prior-to-October-update format:

103 Main St Apt 10, Pepperell, MA 01463

The effects:

• Property Detail matching should now be easier, especially if you were making requests with the descriptor and getting 404 Not Founds

• No longer need to grab propertyInfo.address.unitType and concatenate into the “label” string between the street address and address number

“apnUnformatted” - added this in addition to existing “apn” in case anyone needs the version with special characters, padding, or spaces

“fips” - the state+county code represented as one value in the fips code which was added to the comps response

New Property Search API filter - “last_sale_arms_length”

Primarily intended to be used with the “last_sale_date_min” / “last_sale_date_max” filters

Arms length transactions ensure that you eliminate any intra-family or other types of transfers, some of which have $0 last sale prices.

{
    last_sale_date_min: "2024-09-01",
    last_sale_date_max: "2024-12-20",
    last_sale_arms_length: true
}

In the Property Search response, there’s also a new response field - “lastSaleArmsLength“

Note: in the Property Detail response, we’ve already had the “lastSale.armsLength” field in the response and armsLength [bool] is also a field on any of the .saleHistory entries