What Criteria filters for a recent eviction? (Team plan)

PropertyRadar API Support
1

Setup: Team plan. Pulling North Orange County (County FIPS 06059) segments with POST /v1/properties using free counts (Purchase=0). Most criteria work great. One question and one clarification.

Question: what is the correct Criteria to filter recent evictions?

inProbateProperty works exactly as expected and returns a count:

curl -s -X POST 'https://api.propertyradar.com/v1/properties?Purchase=0&Limit=1' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{"Criteria":[{"name":"County","value":["06059"]},{"name":"inProbateProperty","value":["1"]}]}'
# -> 200 {"results":[],"totalCost":0,"resultCount":0,"quantityFreeRemaining":13597,"totalResultCount":316}

But hasRecentEviction returns HTTP 200 with an empty envelope and no count fields at all (it is not a 400 “Unexpected Criterion”, and not an upgrade error):

curl -s -X POST 'https://api.propertyradar.com/v1/properties?Purchase=0&Limit=1' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{"Criteria":[{"name":"County","value":["06059"]},{"name":"hasRecentEviction","value":["1"]}]}'
# -> 200 {"results":[]}

For reference, a truly unknown field name returns a clean 400:

# {"name":"fooBarBaz","value":["1"]}  ->  400 {"error":"Unexpected Criterion: fooBarBaz #1"}

What is the correct Criteria field name and value format to filter for properties with a recent eviction? Or is eviction only available as a Response field, not a filterable Criterion?

Clarification (no action needed, just confirming your note)

You mentioned the “cannot be used by this user” errors come from putting Response fields into Criteria. That matches what we see:

# {"name":"isRecentSale","value":["1"]}   -> "The param: isRecentSale cannot be used by this user" (feature not in plan)
# {"name":"isFreeAndClear","value":["1"]} -> "The param: isFreeAndClear cannot be used by this user"
# {"name":"SaleDate","value":["from: 2024-07-01"]} -> "The feature [Trustee Sale Tracking] is not included..."

We are already working around these (recent sales via LastTransferRecDate “from:”, equity via EquityPercent), and we do not need Trustee Sale Tracking. So the only open item is the eviction filter above.

Thanks!

2

Hello!

The error occurs because hasRecentEviction is not available as a standalone search criterion. Instead, use the In Distress criteria described in our documentation. This allows you to filter by that signal flag, along with other distress-related indicators.

Similarly, isRecentSale is a result field rather than a searchable criterion. To filter for recently sold properties, you can instead use the Purchase Date criteria.

isFreeAndClear is also a result field and cannot be used directly as a criterion. To find properties that are likely free and clear, use the Equity criteria and filter for an estimated equity percentage of 100%.

The Sale Date field is a special case because it is part of our Trustee Sale Tracking data. It represents the scheduled auction date for a property, not the date the property was purchased or transferred.

Access to this field requires the Trustee Sale Tracking add-on, which is licensed by county. Without that add-on, you can use the Original Sale Date field instead. Please note that Original Sale Date is not updated with subsequent trustee-sale activity unless Trustee Sale Tracking is enabled:

For more information about the differences between criteria and result fields, as well as the data available through the API, please review our documentation:

Please let us know if you have any additional questions!