List Resolutions

List resolution runs that apply Data Policies to extracted values with GET /v1/resolutions: filter by status or source_run_id, newest first, up to 100 runs.

Resolution means applying Data Policies — versioned normalization rulesets — to the field values produced by a completed job run. A resolution run standardizes raw extracted values so that values like country names, units, or vendor identifiers are mapped to canonical forms against your reference data. The source run's extracted grid is read-only input: resolution never re-runs OCR or extraction, and its output lives in its own result rows.

A resolution run maps raw extracted values (e.g. "Deutschland") to canonical forms (e.g. "DE") through the normalization configured on the schema: reference-data lookups, deterministic computations, value transforms and modifiers, format constraints, and dialect shaping. At creation, the run freezes that configuration into a policy_snapshot (and, when the schema has a dialect wired, a dialect_snapshot), so each run is reproducible and independent — you can resolve the same job again later under a changed configuration without disturbing earlier results.

This endpoint lists the resolution runs in your workspace, newest first, returning up to 100 runs in one response with no pagination cursor. Two optional filters narrow the list server-side: status restricts to runs in one lifecycle state (pending, processing, completed, or failed), and source_run_id returns only the resolutions created from a specific job run — the natural query when you want to know whether a job has already been resolved.

Each run in the list carries the same shape as [GET /v1/resolutions/{id}](get-resolution): identifiers, status, the frozen policy_snapshot and dialect_snapshot, an error_message for failed runs, and a links object pointing at the run itself, its results, and the source job run. Because snapshots embed the full per-field configuration, list responses can be large — filter by source_run_id where you can rather than paginating the whole workspace client-side.

Response

curl -s "https://api.talonic.com/v1/resolutions?status=completed&source_run_id=b2c3d4e5-f6a7-8901-bcde-f12345678901" \
  -H "Authorization: Bearer tlnc_your_api_key"

{
  "data": [
    {
      "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "source_run_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
      "status": "completed",
      "policy_snapshot": {
        "name": "Resolution 42Docs Jul 14",
        "sanity_check": false,
        "fields": [
          {
            "field_name": "country",
            "display_name": "Country",
            "data_type": "string",
            "reference_table": "iso-countries",
            "modifiers": null,
            "format": null,
            "suppress_output": false,
            "output_name": null
          }
        ]
      },
      "dialect_snapshot": null,
      "error_message": null,
      "created_at": "2026-07-14T10:32:00.000Z",
      "updated_at": "2026-07-14T10:35:42.000Z",
      "links": {
        "self": "/v1/resolutions/a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "results": "/v1/resolutions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/results",
        "source_run": "/v1/jobs/b2c3d4e5-f6a7-8901-bcde-f12345678901"
      }
    }
  ]
}

Errors