APN Autocomplete

Resolve a full or partial Assessor's Parcel Number (APN) to candidate parcels. APNs are only unique within a single county. Each county assessor numbers its parcels independently, so the very same APN value can (and often does) belong to completely different properties in other counties or states. Because of that the endpoint returns *every* matching parcel, each tagged with its county, state, and zip (when available) so you can pick the right one, see the two same-APN matches (Florida and Texas) in the example response below. FREE: zero credits charged. A pre-flight resolver, like Address Autocomplete but keyed on APN. When to use it - APN typeahead: power a parcel-search box where the user types an APN and picks the correct parcel from the returned matches. - Disambiguate a raw APN: turn an APN pulled from a county record into a confirmed county / state / zip, which you can then use to scope a property search. APN format: the leading # is optional and is stripped automatically; other formatting (dashes, spaces) is passed through as-is. Rate limit 30 requests per minute per account. Exceeding it returns 429 Too Many Requests, back off and retry. The throttle is a fair-use guard so no single account monopolizes the parcel-resolution capacity. What you get back An array of up to 10 best-match parcels. Each record contains: - Parcel: apn (Assessor's Parcel Number). - Location: county, state, and zip (present when known). Use the most specific available to scope a search: ZIP if present, otherwise county + state. - Geographic identifiers: state_fips, county_fips, and fips (combined 5-digit code). These are public US-government identifiers, useful for cross-referencing county records. - Geometry: latitude, longitude for mapping. If no matches, results is an empty array. Related endpoints: TraceAI Assist · List Saved Templates · Create a Saved Template