Autotrace
Autotrace with the Property Data API allows you to connect people and property data. This API call uses the regular property search endpoint with minor differences, notably the auto_trace
parameter and a specific view for property records. This will allow you to directly pull property records, along with owner contact information, with just one API call.
Endpoint
POST https://api.datafiniti.co/v4/properties/search
Input
Users can run Autotrace searches without extra query modifications. It's recommended to test different search parameters before running Autotrace as it will only return property data for records with people.title:owner
. The parameter should reflect the following structure:
query
- This selects which records should be matched. It's the same format as our search endpoint.num_records
- The number of records matching the query you want to be updated. If this parameter is not specified, all matching records will be updated.download
- Set this to "true" OR "false" to download the records to a file.format
- Specify either "json" or "csv" for your file format.auto_trace
- Set this to "true" OR "false" for whether or not to autotrace the property records matched by yourquery
.only_traceable
- Boolean "true" OR "false" for whether the records return must have people data in the dataset.
autotrace credits
Please note that autotrace API requests will require available property data credits and people data credits. Using an autotrace enabled search will charge 1 property data credit and 1 people data credit per
num_found
or set bynum_records
.
Your json and csv output will mimic the same response as a property data search API call, with one exception. Any data found in the property record's people
field will be appended with the matching people record from the people database.
Example API call parameters:
{
"query": "country:US AND province:FL",
"num_records": 1,
"download":false,
"format":"json",
"auto_trace":true,
"only_traceable":true
}
Custom views with autotrace
Autotrace allow you to pull people data subfields that you can create custom views from. To find out more about people data field you can view our schema here. For this example we will create a new view for the previous API property search API call:
Example API with view:
{
"query": "country:US AND province:FL",
"num_records": 1,
"download":false,
"format":"json",
"auto_trace":true,
"only_traceable":true,
"view": [
{"name": "address"},
{"name": "city"},
{"name": "province"},
{"name": "postalCode"},
{"name": "city"},
{"name": "mostRecentBrokerAgent"},
{"name": "mostRecentBrokerCompany"},
{"name": "mostRecentBrokerDateSeen"},
{"name": "mostRecentBrokerEmails"},
{"name": "mostRecentBrokerPhones"},
{"name": "transactions"},
]
}
custom views
You can customize your view with as many or as little subfield as you would like. For more information you can read more about Views.
People data & views
Please note that you can NOT flatten
people
data sub-fields. People data that is appended via autotrace is already flattened for your convenience.
Output
{
"query": "country:US AND province:FL",
"num_records": 1,
"download":false,
"format":"json",
"auto_trace":true,
"only_traceable":true,
"view": [
{"name": "address"},
{"name": "city"},
{"name": "province"},
{"name": "postalCode"},
{"name": "city"},
{"name": "mostRecentBrokerAgent"},
{"name": "mostRecentBrokerCompany"},
{"name": "mostRecentBrokerDateSeen"},
{"name": "mostRecentBrokerEmails"},
{"name": "mostRecentBrokerPhones"},
{"name": "transactions"},
{"name": "people", "flatten":false, "sub_fields":[
{"name": "firstName"},
{"name": "lastName"},
{"name": "phoneNumberHighScoreMobile"},
{"name": "phoneNumberHighScoreLand"},
{"name": "emails"},
{"name": "dateUpdated"}
]
}
]
}
Example output - simplified view of people
{
"num_found": 777,
"total_cost": 1,
"people_cost": 1,
"property_cost": 1,
"business_cost": 0,
"product_cost": 0,
"records": [
{
"absenteeOwner": [
{
"absent": true,
"firstDateSeen": "2024-04-11T16:57:22.592Z",
"lastDateSeen": "2024-04-11T16:57:22.592Z"
}
],
"address": "213 Grand Key Loop E",
"city": "Destin",
"congressionalDistrictHouse": 99,
"country": "US",
"county": "Okaloosa",
"countyFIPS": 12091,
"currentOwnerType": "INDIVIDUAL",
"dateAdded": "2019-10-07T15:46:41Z",
"dateUpdated": "2024-07-01T16:57:00Z",
"fees": [
{
"amountMax": 1343,
"amountMin": 1343,
"currency": "USD",
"dateSeen": [
"2020-08-17T20:01:00.000Z",
"2020-06-10T09:49:00.000Z",
"2020-05-23T18:02:00.000Z",
"2020-09-22T14:28:00.000Z",
"2020-09-18T03:22:00.000Z",
"2020-09-28T02:16:00.000Z"
],
"type": "HOA"
},
{
"amountMax": 507,
"amountMin": 507,
"currency": "USD",
"dateSeen": [
"2022-03-15T16:18:00.000Z",
"2022-04-07T10:10:00.000Z"
],
"type": "HOA"
}
],
"floorSizeValue": 2769,
"floorSizeUnit": "sq ft",
"geoLocation": "POINT (-86.41966248 30.3867321)",
"hvacTypes": [
"Ceiling Fan(s)",
"Electric",
"Central",
"Central Air"
],
"instrumentNumber": "3546791",
"latitude": "30.3867321",
"legalDescription": "VILLAGES OF CRYSTAL BEACH LOT 50",
"legalRange": "22",
"listingName": "213 Grand Key Loop E, Destin, FL 32541",
"longitude": "-86.41966248",
"lotSizeValue": 0.03,
"lotSizeUnit": "acs",
"mostRecentBrokerAgent": "Whitney Cooley",
"mostRecentBrokerCompany": "Scenic Sotheby's International Realty",
"mostRecentBrokerPhones": [
"850-368-5782"
],
"mostRecentBrokerDateSeen": "2024-06-27T05:40:23.118Z",
"mostRecentPriceAmount": 1195000,
"mostRecentPriceDomain": "www.xome.com",
"mostRecentPriceSourceURL": "https://www.redfin.com/FL/Destin/213-Grand-Key-Loop-E-32541/home/139914810",
"mostRecentPriceFirstDateSeen": "2024-06-27T05:40:23.500Z",
"mostRecentEstimatedPriceAmount": 1303725,
"mostRecentEstimatedPriceDomain": "www.redfin.com",
"mostRecentEstimatedPriceFirstDateSeen": "2024-05-23T05:48:06.793Z",
"mostRecentStatus": "For Sale",
"mostRecentStatusDate": "2024-05-13T18:07:35.443Z",
"mostRecentStatusFirstDateSeen": "2024-03-23T11:15:30.825Z",
"mostRecentVacancy": false,
"mostRecentVacancyFirstDateSeen": "2024-04-11T16:57:22.592Z",
"mostRecentAbsenteeOwner": true,
"mostRecentAbsenteeOwnerFirstDateSeen": "2024-04-11T16:57:22.592Z",
"mlsNumber": "945244",
"neighborhoods": [
"Villages Of Crystal Beach",
"VILLAGES OF CRYSTAL BEACH",
"Destin",
"Florida"
],
"numBathroom": 4,
"numBedroom": 5,
"numFloor": 3,
"numUnit": 1,
"parking": [
"Garage Attached",
"Deeded"
],
"parkingTypes": [
"Attached Garage"
],
"postalCode": "32541",
"prices": [
{
"amountMax": 440000,
"amountMin": 440000,
"availability": "false",
"currency": "USD",
"dateSeen": [
"2020-08-21T21:11:11.089Z",
"2020-08-21T20:19:44.214Z"
],
"firstDateSeen": "2020-08-21T20:19:44.214Z",
"lastDateSeen": "2020-08-21T21:11:11.089Z",
"domains": [
"www.redfin.com"
],
"isSale": "false",
"isSold": "true",
"pricePerSquareFoot": 155
},
{
"amountMax": 10000,
"amountMin": 10000,
"availability": "false",
"currency": "USD",
"dateSeen": [
"2020-07-16T22:25:07.787Z"
],
"firstDateSeen": "2020-07-16T22:25:07.787Z",
"lastDateSeen": "2020-07-16T22:25:07.787Z",
"domains": [
"www.coldwellbanker.com"
],
"pricePerSquareFoot": 235
}
],
"propertyTaxes": [
{
"amount": 6152,
"currency": "USD",
"dateSeen": [
"2018-01-01T00:00:00.000Z"
]
},
{
"amount": 5511,
"currency": "USD",
"dateSeen": [
"2015-01-01T00:00:00.000Z"
]
}
],
"propertyType": "Single Family Dwelling",
"province": "FL",
"subdivision": "Villages Of Crystal Beach",
"taxID": "00-2S-22-1125-0000-0500",
"transactions": [
{
"saleDate": "2022-05-02T00:00:00.000Z",
"price": 1300000,
"sellerFirstName": "Weston",
"sellerLastName": "Hanoka",
"buyerFirstName": "Rice",
"buyerLastName": "Ryan",
"lenderName": "Fbc Mortgage LLC",
"loanAmount": 1040000,
"mortgageTerm": 360,
"parcelNumber": "00-2S-22-1125-0000-0500"
}
],
"vacancy": [
{
"vacant": false,
"firstDateSeen": "2024-04-11T16:57:22.592Z",
"lastDateSeen": "2024-04-11T16:57:22.592Z"
}
],
"yearBuilt": 2007,
"people": [
{
"address": "213 Grand Key Loop E",
"city": "Destin",
"country": "US",
"dateAdded": "2024-04-11T16:57:22Z",
"dateUpdated": "2024-04-11T16:57:22Z",
"emails": [
"[email protected]"
],
"firstName": "Andrew",
"keys": [
"andrew/smith/-153511615",
"andrew/smith/2139898621",
"andrew/smith/1200706648",
"andrew/smith/1229122397",
"andrew/smith/1997759056",
"andrew/smith/737746307",
"andrew/smith/978658",
"andrew/smith/us/fl/destin/213grandkeyloope",
"andrew/smith/1281514859",
"andrew/smith/-922148274",
"andrew/smith/-862181766",
"andrew/smith/-11372050",
"andrew/smith/-1413524364",
"andrew/smith/-950564023"
],
"lastName": "Smith",
"phoneNumberHighScoreMobile": "+1 724-831-9260",
"phoneNumberHighScoreLand": "+1 412-321-2404",
"phoneNumbers": [
{
"number": "+1 724-831-9260",
"carrier": "CELLCO PARTNERSHIP DBA VERIZON WIRELESS - PA",
"type": "Mobile",
"tested": false,
"reachableStatus": true,
"bdscore": 100,
"lastDateSeen": "2024-04-11T16:57:22.592Z"
},
{
"number": "+1 724-776-0352",
"carrier": "CONSOLIDATED COMMUNICATIONS OF PENNSYLVANIA CO",
"type": "Land Line",
"tested": true,
"reachableStatus": true,
"bdscore": 80,
"lastDateSeen": "2024-04-11T16:57:22.592Z"
},
{
"number": "+1 412-635-9088",
"carrier": "ONVOY- LLC - PA",
"type": "Land Line",
"tested": false,
"reachableStatus": true,
"bdscore": 85,
"lastDateSeen": "2024-04-11T16:57:22.592Z"
},
{
"number": "+1 724-880-6958",
"carrier": "CELLCO PARTNERSHIP DBA VERIZON WIRELESS - PA",
"type": "Mobile",
"tested": true,
"reachableStatus": true,
"bdscore": 75,
"lastDateSeen": "2024-04-11T16:57:22.592Z"
},
{
"number": "+1 412-321-2404",
"carrier": "VERIZON PENNSYLVANIA- INC.",
"type": "Land Line",
"tested": false,
"reachableStatus": true,
"bdscore": 95,
"lastDateSeen": "2024-04-11T16:57:22.592Z"
},
{
"number": "+1 724-766-7870",
"carrier": "MCIMETRO ACCESS TRANSMISSION SERVICES LLC - PA",
"type": "Land Line",
"tested": true,
"reachableStatus": true,
"bdscore": 90,
"lastDateSeen": "2024-04-11T16:57:22.592Z"
}
],
"postalCode": "32541-3525",
"province": "FL",
"sourceURLs": [
"https://datafiniti.co/bd-datafiniti"
],
"tcpa": false,
"phoneNumberHighScoreMobileScore": 100,
"phoneNumberHighScoreLandScore": 95
}
],
"id": "AW2m5roYcWockGYkocZQ"
}
]
}
Autotrace matches
Depending on your property search query, you may receive less autotrace values back than the
num_found
. This is expected, as not all property owners are found on an autotrace search. We estimate anywhere from 50%-80% of property records will have matching people records.In these cases, your
num_records
will act as an upper limit on how many records autotrace will match.
Common Errors
Autotrace with Views
Please note that there a mandatory fields that must be called when using a custom view.
- people.keys
- transactions.buyerFirstName
- transactions.buyerLastName
- transactions.saleDate
Common error messages include:
[ "auto_trace view must contain people.keys", "auto_trace view must contain transactions.buyerFirstName ", "auto_trace view must contain transactions.buyerLastName", "auto_trace view must contain transactions.saleDate" ]
Example use cases
Updated 16 days ago