Skip to main content
POST
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

array
required
Array of coordinate objects to look up (max 250).
string[]
Field IDs to include in results. Can include both property and people fields. Omit or pass an empty array for the default set.
string
Which contacts to include on matched properties.Options: owners, owners_and_family, renters, residents, noneUse 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.

Unmatched Result

Match Failure Codes

These codes are shared across all enrichment endpoints.

Totals

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.