Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Enrich by Geocode

Look up properties by geographic coordinates (reverse geocoding). Each item in the data array provides a latitude and longitude pair, and the API returns the property at that location.
Each request accepts up to 250 items in the data array. The response returns every submitted item with a matched flag indicating whether a property was found.
The previous endpoint path /v1/enrichment/latlng still works as an alias but is deprecated. Please update your code to use /v1/enrichment/reverse-geocode.

Body Parameters

body dataarrayrequired
Array of coordinate objects to look up (max 250).
Coordinate object properties
body latitudenumberrequired
Property latitude (e.g., 30.2598).
body longitudenumberrequired
Property longitude (e.g., -97.7544).
body fieldsstring[]
Field IDs to include in results. Can include both property and people fields. Omit or pass an empty array for the default set.
body contact_audiencestring
Which contacts to include on matched properties.
Options: owners, owners_and_family, renters, residents, none
Use none or omit this parameter to return property data without contacts or people data credit charges. Any other value includes a contacts array.

Response Fields

The response contains a data array and a totals object. There is no pagination — all submitted items are returned in a single response.

Matched Result

When matched is true, the result contains all always-included property fields plus any requested fields.
FieldTypeDescription
inputobjectEcho of the original input object
matchedbooleantrue
dm_property_idstringDealMachine internal property ID
full_addressstringComplete formatted address
address, city, state, zipstringParsed address components
latitude, longitudenumberProperty coordinates
contactsarrayContacts matching contact_audience. Omitted when the audience is none or not set.
requested fieldsvariesAny fields specified in fields

Unmatched Result

FieldTypeDescription
inputobjectEcho of the original input object
matchedbooleanfalse
match_failureobjectStructured failure with code and reason
match_failure.codestringMachine-readable failure code (see Match Failure Codes below)
match_failure.reasonstringHuman-readable explanation of why no match was found

Match Failure Codes

These codes are shared across all enrichment endpoints.
CodeDescription
not_foundNo matching record exists for the provided input
invalid_inputThe input could not be processed (e.g., invalid address, invalid email, invalid phone number). The reason field provides specifics.

Totals

FieldTypeDescription
submittedintegerNumber of items in the request data array
matchedintegerNumber of items that matched a property
unmatchedintegerNumber of items that did not match

Credits

This endpoint consumes 1 property data credit per matched property. A non-none contact_audience adds people data credits for included contacts. Use none for zero people data credits. Only matched results consume credits. Credits are deduplicated within your billing period, so accessing the same entity again is free.
Every response includes a credits object with a full breakdown of what was charged. See Credits for details.

Notes

  • Both latitude and longitude are required for each item.
  • The API matches the nearest property parcel to the provided coordinates. For best results, use coordinates that fall within the property boundary.
  • Items are matched independently — one failed match does not affect others.
  • The input object is always echoed back so you can correlate results with your input data.
  • When contact_audience is set to an audience other than none, each matched result includes a contacts array with the same structure and match behavior as Search Properties.
  • The old /v1/enrichment/latlng path is still supported as a deprecated alias.
Request example
curl -X POST "https://api.v2.dealmachine.com/v1/enrichment/reverse-geocode" \ -H "Authorization: Bearer dm_sk_live_xxx" \ -H "Content-Type: application/json" \ -d '{ "data": [ { "latitude": 30.2598, "longitude": -97.7544 }, { "latitude": 30.2271, "longitude": -97.7437 } ], "fields": ["estimated_value", "estimated_equity_percentage", "num_bedrooms", "full_name", "phones"], "contact_audience": "owners" }'
Response example
{ "data": [ { "input": { "latitude": 30.2598, "longitude": -97.7544 }, "matched": true, "dm_property_id": "prop_a1b2c3", "full_address": "1200 Barton Springs Rd, Austin, TX 78704", "address": "1200 Barton Springs Rd", "city": "Austin", "state": "TX", "zip": "78704", "latitude": 30.2598, "longitude": -97.7544, "estimated_value": 575000, "contacts": [ { "dm_person_id": "per_x1y2z3", "full_name": "John Smith", "phones": [{ "number": "5125551234", "type": "wireless", "do_not_call": false }] } ] }, { "input": { "latitude": 30.2271, "longitude": -97.7437 }, "matched": false, "match_failure": { "code": "not_found", "reason": "No property found at the provided coordinates" } } ], "totals": { "submitted": 2, "matched": 1, "unmatched": 1 }, "credits": { "used": 1, "properties": 1, "people": 0, "deduplicated": 0 } }