Skip to main content

Get Results

Get per-field resolution results showing original values, resolved values, resolution step used, and confidence scores for each document.

Retrieve the per-field resolution results for a completed run. Each result shows the original extracted value alongside the resolved canonical value, the resolution strategy that produced the match, and a confidence score. Use this to audit how values were normalized and identify fields that may need manual review.

The resolution_step field indicates which strategy produced the resolved value: lookup (direct table match), transfer (registry transfer), compute (deterministic computation), or null if no resolution was applied.
GET/v1/resolutions/{id}/results

Response

Response fields

dataarrayArray of per-field resolution result objects.
data[].idstringResult UUID.
data[].resolution_run_idstringParent resolution run UUID.
data[].document_idstringDocument UUID this result belongs to.
data[].field_namestringField key that was resolved.
data[].original_valuestring | nullRaw extracted value before resolution.
data[].resolved_valuestring | nullCanonical value after resolution.
data[].resolution_stepstring | nullStrategy that produced the resolved value (e.g. lookup, transfer, compute).
data[].confidencenumber | nullConfidence score for the resolved value (0–1).
data[].created_atstringISO 8601 timestamp.

Response

{
  "data": [
    {
      "id": "c3d4e5f6-a7b8-9012-cdef-123456789012",
      "resolution_run_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "document_id": "d4e5f6a7-b8c9-0123-defa-234567890123",
      "field_name": "country",
      "original_value": "Deutschland",
      "resolved_value": "DE",
      "resolution_step": "lookup",
      "confidence": 0.98,
      "created_at": "2024-09-14T10:35:00.000Z"
    }
  ]
}

Use the resolution_step field to understand how each value was normalized: lookup indicates a direct reference table match, transfer means the value was carried from the field registry, and compute means a deterministic formula produced the result. Fields where resolved_value is null were not matched by any strategy and retain their raw extracted value -- consider adding those values to your lookup tables for future runs.

Errors

Error responses

401unauthorizedMissing or invalid API key.
404not_foundResolution run not found or does not belong to your organization.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

Related

Get Resolution