Skip to main content
POST
Start 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

Query Parameters

force
boolean
default:false

When true, start a new run even if a run is already in flight for this company scanning the same configuration — i.e. skip the duplicate check and always mint a fresh run. Any value other than true (including omission) is treated as false.

This does not raise the limit of 3 runs in flight per company: a ?force=true request past that limit still gets a 429.

Unlike force on import, this needs no additional permission and destroys nothing — the only cost of forcing is a redundant scan.

Body

application/json

OPTIONAL. Omit the body entirely to scan the company's live configuration — that is the documented way to ask for a live scan, and no query flag is needed for it.

When a body IS sent it must be a COMPLETE configuration document matching the schema below, and the run scans that candidate configuration instead; nothing is persisted. A delta/patch body is rejected with a 400, and so is a body that cannot be read as JSON.

Structured FMV1 configuration body. This is both the body the import endpoint accepts and the body the export endpoint returns, so export → (edit) → import is a lossless round-trip. Each property is an array of config rows; the import runs them through the full validate → compare → apply pipeline.

The per-element schemas below are the canonical FMV1 configuration model and the single source of truth for this payload.

fields
object[]
required

Field definitions, keyed by entity + reference id.

pages
object[]
required

Page definitions.

cards
object[]
required

Card definitions.

cardPageRelationships
object[]
required

Placements of cards onto pages.

optionSetTypes
object[]
required

Option-set type declarations.

objectTypes
object[]
required

Custom-object type declarations.

optionSets
object[]
required

Option sets and their options.

objects
object[]
required

Custom-object sub-field definitions, joined to object types.

objectPrimitives
object[]
required

Object-primitive sub-field definitions (Address / Date / Currency).

fieldLocations
object[]
required

Field placements (the layout) onto cards.

ratingWorkflows
object[]
required

Rating workflow definitions.

entityInvariants
object[]
required

Per-entity invariant conditions enforced on every write.

formLogicRules
object[]

Forms-logic rules (quote-flow auto-add rules). Optional — existing payloads predate the "Forms" tab; absent ⇒ no rules.

smartTags
object[]

Smart tags — the named values resolved into generated documents. Optional: existing payloads predate the slice, and absent ⇒ no smart tags, which is also how a company that has not yet moved to this format is recognised.

Omitted from an export when the company has none, rather than emitted as an empty array.

exportSurfaces
object[]

Declared export columns — the tenant-facing column set of each export surface (the seven entity exports plus the bordereau). Optional: existing payloads predate the slice, and absent ⇒ no declared columns, which is also how a surface that still offers every configured field is recognised.

Activation is per surface: a surface with at least one row here resolves its whole tenant column set through those rows, in the order they appear; a surface with none behaves exactly as it did before this section existed.

Omitted from an export when the company has declared none, rather than emitted as an empty array.

Response

The run to poll. outcome: "enqueued" means a new scan was started; outcome: "duplicate" means runId is a run already in flight scanning this same configuration and no second scan was started.

The run to poll after starting a data-validation run. outcome is a policy verdict delivered as a successful 200, not an error: duplicate means a run scanning this same configuration was already in flight, so runId is that run and no second scan was started.

runId
string<uuid>
required

The run to poll via GET /api/v1/companies/{companyId}/configuration/data-validation-runs/{runId}

outcome
enum<string>
required

enqueued when a new scan was started; duplicate when a run already in flight was scanning this same configuration (pass ?force=true to start a new run anyway)

Available options:
enqueued,
duplicate