Skip to main content
POST
Look up properties by street address. Each item in the data array can use either a single full_address string or structured components (street, unit, city, state, zip). You can also break down the street into street_number and street_name instead of using a single street field.
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.

Body Parameters

array
required
Array of address 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, noneWhen set to an audience other than none, each matched result includes a contacts array. Omit the parameter or set it to none to return property data only with zero people credits.
Use contact_audience: "none" when you only need the enriched property. Request owners or another audience only when you need those people records.

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 Warnings

When the API can still match an item but had to rewrite the input to do so, the response item includes a match_warning alongside matched (whether the match succeeded or not). Treat it as a signal to fix your client — the match worked this time but may not on a similar input.

Match Failure Codes

These codes are shared across all enrichment endpoints.

Totals

Credits

This endpoint consumes 1 property data credit per matched property. When contact_audience is set to an audience other than none, included contacts consume people credits. contact_audience: "none" consumes zero people credits. Only matched results consume credits. Credits are deduplicated within your billing period. Every response includes a credits object with a full breakdown of what was charged. See Credits for details.

Notes

  • Each item must include either full_address, street, or the combination of street_number + street_name, along with city + state. Including unit and zip with structured fields is optional but improves match accuracy.
  • 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.