Skip to main content
GET
Get Data Validation Run

Authorizations

Authorization
string
header
required

User-principal OAuth 2.0 Bearer authentication. Send a user-scoped Auth0 access token (audience = the app API audience) as Authorization: Bearer <jwt>. The request resolves to the user's identity and is authorized by their Role on the {companyId} in the path — the same role-based permissions the web app enforces. This is the path the MCP connector uses to act on a user's behalf; endpoints that accept it list both BearerAuth and ApiKeyAuth.

Path Parameters

companyId
string<uuid>
required

Company identifier

runId
string<uuid>
required

The run identifier returned by POST /configuration/data-validation-runs. Runs are scoped to their company: a run id belonging to another company returns 404, exactly as an id that exists nowhere does.

Response

The run's current status and running counts

A data-validation run's current status and running counts. Fixed size: there is no per-record findings list, and deliberately no total or percentage — the four classification counts are independent, overlapping buckets and do not sum to recordsScanned.

runId
string<uuid>
required

The run identifier

status
enum<string>
required

queued while the run waits for a worker (a normal state, not a stall), running mid-scan, then the terminal succeeded or failed

Available options:
queued,
running,
succeeded,
failed
recordsScanned
integer
required

How many stored records the scan has classified so far

recordsAdhering
integer
required

Records that would persist cleanly under the scanned configuration — no undeclared keys and no violations

recordsWithExtraKeys
integer
required

Records holding keys the scanned configuration no longer declares (suspect, not necessarily fatal)

recordsWithAdvisories
integer
required

Records with one or more advisory findings and no breaking violations. This bucket may overlap recordsWithExtraKeys.

recordsBreaking
integer
required

Records holding a value that would FAIL a write under the scanned configuration

error
string | null
required

Why the scan stopped; null unless status is failed

createdAt
string<date-time>
required

When the run was started

updatedAt
string<date-time>
required

When the run's counts or status last changed

finishedAt
string<date-time> | null
required

When the run reached a terminal status; null until then