Sign in
project

Resolve Addresses Batch

Resolve a pasted handful of addresses in one batch for the paste review list.

One typed outcome per input row in input order (matched / ambiguous / not_in_dataset / empty_input), county-bounded like the single resolve. Candidate labels for every row are hydrated in a single read, then re-split per row. A read failure surfaces as 503 rather than the raw error (which can carry a sandbox URI).

post/api/v1/project/address/resolve-many

Request body

queriesstring[] required
county_fipsstring required
geocoder_policy'internal_only' | 'external_fallback'

Whether a pre-project address lookup can use the external geocoder.

Response

Successful Response

Changes

Changed in 3 of the 30 revisions of this API.34

  • bb508e9351743See the full diff
    • ▲

      the request property became required

      request-property-became-required

    • ▲

      request property list-of-types was narrowed by removing types null from media type application/json

      request-property-list-of-types-narrowed

    • ▲

      added the pattern ^\d{5}$ to the request property

      request-property-pattern-added

  • 95495ef535bc3See the full diff
    • ○

      added the new optional request property

      new-optional-request-property

    • ○

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

      response-optional-property-added

    • ○

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

      response-optional-property-added

    This revision also has 18 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • ab171f3fcfbe1See the full diff
    • ○

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

      response-optional-property-added

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog