Execute Resolution

Execute a pending resolution run to start normalization. The call returns immediately with running status; poll the run to detect completion or failure.

Execute a resolution run to start applying the Data Policy to a pending run. The endpoint returns immediately with the updated run status (typically running) rather than waiting for processing to finish. Poll the get resolution endpoint to track progress and detect completion.

Response

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "source_run_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
  "status": "running",
  "documents_processed": null,
  "created_at": "2024-09-14T10:32:00.000Z",
  "completed_at": null,
  "links": {
    "self": "/v1/resolutions/a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "results": "/v1/resolutions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/results"
  }
}

The standard workflow is POST /v1/resolutions to create, then POST /v1/resolutions/{id}/execute to start processing. The endpoint returns immediately with status: "running" -- poll GET /v1/resolutions/{id} to detect completion. Deterministic policy rules complete in seconds; runs whose policy invokes LLM-assisted matching for ambiguous values take 1-5 minutes depending on the number of unresolved fields.

Errors