Skip to main content
PATCH
/
api
/
datachecks
/
testsuggestions
/
v1
/
accepted
BatchAcceptTestSuggestions
curl --request PATCH \
  --url https://developer.synq.io/api/datachecks/testsuggestions/v1/accepted \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "ids": [
    "<string>"
  ],
  "recurrenceRule": "<string>",
  "annotations": [
    {
      "name": "<string>",
      "values": [
        "<string>"
      ]
    }
  ],
  "saveFailures": true
}
'
{
  "identifiers": [
    {
      "airflowDag": {
        "integrationId": "<string>",
        "dagId": "<string>"
      }
    }
  ]
}

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
ids
string[]
recurrenceRule
string

Recurrence rule for the execution schedule of the SqlTest.

annotations
Annotation · object[]

Annotations for the given test.These help filter the tests for later operations like listing by API, selection in UI, analytics, etc.

saveFailures
boolean

Boolean flag to to toggle saving of failure runs.

Response

200 - application/json

Success

identifiers
(airflow_dag · object | airflow_task · object | bigquery_table · object | clickhouse_table · object | custom · object | databricks_table · object | dataproduct · object | dbt_cloud_node · object | dbt_core_node · object | monitor · object | mysql_table · object | postgres_table · object | redshift_table · object | snowflake_table · object | sql_mesh_audit · object | sql_mesh_model · object | synq_path · object | trino_table · object)[]

Identifiers of created tests.

Identifier is a unique reference to an entity in SYNQ system. Entity identifiers are designed to closely mimic identifiers used by data platforms and tools. To construct an identifier, you need to know the kind of the entity and the ids that you would normally use to identify it in the data platform or tool. For example, to identify a table in BigQuery, you would need to know the project, dataset, and table names.