MAmaia-analytics
project

Resolve Addresses Batch For Project

Changed on

Project-scoped batch resolve for both in-project surfaces — the import dialog (Door 2) and chat paste.

The county scope is the project's canonical county_fips (derived server-side, never client-supplied), so a paste can't resolve outside the project's county; a project with no county scope is a 404. Resolution runs against the project's sandbox — internal misses and address candidates that name another street fall through to the forward geocoder (it resolves points against a project) instead of classifying as not_in_dataset like the pre-project batch must.

post/api/v1/project/{project_id}/address/resolve-many

Request

  • Base URL
    https://api.maia-analytics.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.maia-analytics.com/api/v1/project/{project_id}/address/resolve-many
  • Auth
    HTTP bearer

Request body

queriesstring[] required

Response

Successful Response

Changes

  • 95495ef535bcRevision changes
    • info

      added the optional property //// to the response with the status

    • info

      added the optional property // to the response with the status

  • ab171f3fcfbeRevision changes
    • info

      added the optional property //// to the response with the status