Skip to main content

List Resolutions

List resolution runs that apply Data Policies — versioned normalization rulesets — to extracted document values, mapping them to canonical forms. Cursor pagination.

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.

A resolution run maps raw extracted values (e.g. "Deutschland") to canonical forms (e.g. "DE") through the rules in the applied policy: reference-data lookups, value transforms, deterministic computations, and LLM-assisted matching for ambiguous values. Each run applies the Data Policy and dialect configuration active at run time, and each run is independent, so you can resolve the same job with different configurations.

Resolution here always means applying Data Policies to values. It is unrelated to the internal registry process (sometimes also called "resolution" or binding) that maps raw extracted field names to canonical field registry entries — that happens automatically during extraction and is not part of this API.

Use this endpoint to list all resolution runs in your workspace. Results support cursor-based pagination and are sorted by creation date, newest first by default.

GET/v1/resolutions

Query parameters

limitintegerMaximum number of items to return (1-100). Default: 20
cursorstringOpaque pagination cursor from a previous response.
orderstringSort order by creation date (asc | desc). Default: desc

Response

Response fields

dataarrayArray of resolution run objects.
data[].idstringResolution run UUID.
data[].source_run_idstringUUID of the originating job run.
data[].statusstringRun status: pending, running, completed, or failed.
data[].documents_processedinteger | nullNumber of documents processed so far, or null before processing starts.
data[].created_atstringISO 8601 creation timestamp.
data[].completed_atstring | nullISO 8601 completion timestamp, or null while the run is in progress.
data[].linksobjectRelated resource URLs (self, results).
pagination.totalintegerTotal number of resolution runs matching the query.
pagination.limitintegerRequested page size.
pagination.has_morebooleanWhether more pages exist.
pagination.next_cursorstring | nullCursor for the next page, or null if no more results.

curl

Response

{
  "data": [
    {
      "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "source_run_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
      "status": "completed",
      "documents_processed": 42,
      "created_at": "2024-09-14T10:32:00.000Z",
      "completed_at": "2024-09-14T10:35:42.000Z",
      "links": {
        "self": "/v1/resolutions/a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "results": "/v1/resolutions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/results"
      }
    }
  ],
  "pagination": {
    "total": 7,
    "limit": 10,
    "has_more": false,
    "next_cursor": null
  }
}
The list endpoint does not filter by status or source run. To find the resolutions derived from a specific job, paginate the list and match on source_run_id client-side.

Errors

Error responses

401unauthorizedMissing or invalid API key.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.