Less Than Field Check API

This page documents how to create and manage a Less Than Field check via the REST API. The check uses the standard Quality Checks endpoints: set rule to lessThanField, list the target field under fields, and name the compared field under properties. All endpoints share the base URL of your deployment (for example, https://your-instance.qualytics.io/api) and require a Bearer token.

Tip

For complete API documentation, including request and response schemas, visit the API docs.

Permissions

All endpoints require the Member role plus a team permission on the check's datastore: Reporter to read, Author to create or update an Active check, archive, or delete, and Drafter to create or update a Draft. See Permissions for the full matrix.

The `properties` object

Less Than Field carries its rule-specific configuration under properties:

Field	Required	Type	Description
`field_name`	Yes	`string`	The other field on the same row to compare against.
`inclusive`	Yes	`boolean`	`true` makes the comparison `<=`; `false` makes it `<`. The platform rejects a payload that omits it.
`numeric_comparator`	No	`object`	Optional tolerance applied when comparing Integral and Fractional fields: `{"epsilon": <number>, "as_absolute": <boolean>}`. `as_absolute` defaults to `true`, which treats `epsilon` as an absolute amount; `false` treats it as a fraction of the compared value.
`duration_comparator`	No	`object`	Optional tolerance applied when comparing Date and Timestamp fields: `{"millis": <integer>}`. The duration is expressed in milliseconds, so five seconds is `{"millis": 5000}`.

Both fields must carry the same type, and that type must be one of Date, Timestamp, Integral, or Fractional. A payload whose properties.field_name names a field of a different type than the one in fields is rejected with 422.

Create

Endpoint: POST /api/quality-checks

Permission: Member role + Author team permission on the container's datastore (Drafter when status is "Draft").

Create a Less Than Field check (every accepted field)

curl -X POST "https://your-instance.qualytics.io/api/quality-checks" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
      "description": "Start date must be earlier than the end date.",
      "rule": "lessThanField",
      "fields": ["start_date"],
      "container_id": 145,
      "coverage": 1,
      "filter": null,
      "properties": {"field_name": "end_date", "inclusive": true},
      "tags": ["contracts", "integrity"],
      "additional_metadata": {"jira": "DATA-8901"},
      "anomaly_message_field": null,
      "template_id": null,
      "status": "Active",
      "owner_id": 7,
      "default_anomaly_assignee_id": 12
  }'

Field notes

Field	Required	Notes
`description`	Yes	Free-text description shown in the UI.
`rule`	Yes	Must be `"lessThanField"`.
`fields`	Yes	Array with exactly one entry: the target field, which forms the left side of the comparison.
`container_id`	Yes	ID of the container (table or file) the check runs against.
`coverage`	No	Fractional value between `0` and `1` that defines the minimum fraction of evaluated rows that must pass. Defaults to `1`, which requires every row to pass.
`filter`	No	SQL `WHERE` expression. Applied before the evaluation, so only filtered rows are evaluated. Send `null` for no filter.
`properties`	Yes	Object naming the compared field and any comparators. See above.
`tags`	No	List of tag names applied to the check for filtering and organization.
`additional_metadata`	No	Free-form key-value pairs (typically links to catalog entries, tickets, governance records).
`anomaly_message_field`	No	Name of a source-record field whose value should be used as the Record Anomaly message instead of the default template-generated one. When the named column is null, missing, or empty for a violating row, the standard Record template is used instead. Shape Anomalies always use the fixed template. Send `null` to use the default Record template.
`template_id`	No	ID of a Check Template to associate the check with. `null` if not using a template.
`status`	No	`"Active"` (default) or `"Draft"`. Draft checks are not evaluated by Scans.
`owner_id`	No	ID of the user who owns the check. Defaults to the user creating the check when omitted.
`default_anomaly_assignee_id`	No	ID of the user automatically assigned to anomalies produced by the check.

Read

Endpoint: GET /api/quality-checks/{id}

Permission: Member role + Reporter team permission on the check's datastore.

Retrieve a check by ID

curl -X GET "https://your-instance.qualytics.io/api/quality-checks/101" \
  -H "Authorization: Bearer YOUR_TOKEN"

Update

Endpoint: PUT /api/quality-checks/{id}

Permission: Member role + Author team permission on the check's datastore (Drafter when the check stays Draft).

The PUT endpoint requires description; include the check's current description (or a new one) along with the fields you want to change. Send the whole properties object: partial property updates are not merged.

Point the check at a different compared field

curl -X PUT "https://your-instance.qualytics.io/api/quality-checks/101" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "description": "Start date must be earlier than the renewal date.",
    "properties": {"field_name": "renewal_date", "inclusive": true}
  }'

A PUT can update most fields on an existing Less Than Field check. Three values stay immutable: the rule type, the container the check is attached to, and the associated Check Template. If any of these needs to change, delete the check and create a new one.

Editable vs Immutable on PUT

Editable

description
coverage
filter
properties.field_name (the compared field)
properties.inclusive
the comparator objects under properties
tags
additional_metadata
anomaly_message_field
fields (must remain a single field)
status
owner_id
default_anomaly_assignee_id

Immutable

rule
container_id
template_id

Delete

Endpoint: DELETE /api/quality-checks/{id}

Permission: Member role + Author team permission on the check's datastore.

Three query parameters control what happens, mirroring the two-stage flow in the UI:

Parameter	Default	Description
`archive`	`true`	When `true`, the check is archived and can be restored later. When `false`, the check is permanently deleted.
`status`	`Discarded`	The archive resolution: `Discarded` (no longer relevant) or `Invalid` (wrong and suppressed from future AI generation). Only used when `archive=true`.
`delete_anomalies`	`true`	Whether to permanently delete the anomalies the check produced. A permanent delete (`archive=false`) always removes them.

Archive a check, keeping its anomalies

curl -X DELETE "https://your-instance.qualytics.io/api/quality-checks/101?archive=true&status=Discarded&delete_anomalies=false" \
  -H "Authorization: Bearer YOUR_TOKEN"

Delete a check permanently

curl -X DELETE "https://your-instance.qualytics.io/api/quality-checks/101?archive=false" \
  -H "Authorization: Bearer YOUR_TOKEN"

Error responses

Status	Description
`400 Bad Request`	A business-logic conflict prevents the operation (for example, changing properties while the check is archived, or switching an archived check between `Discarded` and `Invalid`).
`401 Unauthorized`	Missing or invalid API token.
`403 Forbidden`	The caller lacks the required team permission on the check's datastore.
`404 Not Found`	The check ID does not exist, or an entry in `fields` names a field that is not on the container.
`422 Unprocessable Entity`	The payload fails schema validation (for example, `description` missing on `PUT`, or `properties.field_name` is missing or references a column that does not exist on the container).