Skip to main content
GET
Owner Search

Authorizations

Authorization
string
header
required

Provide your API key directly in the header.

Query Parameters

state
string
required

Two-letter state abbreviation (for example, CA).

lastName
string

Owner surname or company name. Required unless nameContains is provided. Matching is case-insensitive. If both lastName and nameContains are supplied, both must match the same recorded owner name.

firstName
string

Optional given-name prefix, used with lastName to narrow the owner match.

nameContains
string

Match every supplied word in the same recorded owner name; word order does not matter. This is word matching, not an arbitrary substring search. Can be used without lastName. Supported only on v3 data reads; otherwise returns 400.

fuzzy
boolean
default:false

Set true to allow one edit with the first two characters matching exactly. Use a single-token lastName for fuzzy surname matching, or nameContains for multiword fuzzy queries. firstName remains a prefix match. Supported only on v3 data reads; otherwise returns 400.

limit
integer
default:10

Maximum results per page. Defaults to 10; values above 100 are capped at 100. On v3 reads, offset + the applied limit must be at most 200 or the request returns 400.

Required range: 1 <= x <= 100
offset
integer
default:0

Number of matched records to skip. Defaults to 0. On v3 reads, offset + the applied limit must be at most 200. Refine the name query rather than paging beyond this window; cursor pagination is not supported.

Required range: x >= 0
includeExplicitNulls
boolean
default:false

Set true to include missing public nested property fields as explicit nulls. Requires an account enabled for the nested v3 response shape and a v3 data read; otherwise returns 400. Without this flag, fields with unknown values may be omitted.

Response

Matching properties found. Each successful request consumes one token, independent of the number of properties returned.

properties
object[]
required

Matching current-owner parcels. Accounts enabled for the v3 response shape receive nested property records on v3 reads; other accounts receive the v2-compatible flat shape. See the v3 Property Data Schema for nested fields.

metadata
object
required