POST /v1/dataQuality/testCases
Create a Test Case
Create a new test case instance applied to a specific table or column
POST
POST /v1/dataQuality/testCases
Create a Test Case
Create a new test case by linking a test definition to a specific table or column with concrete parameter values.Body Parameters
string
required
Name of the test case. Must be unique within the target entity scope.
string
required
Fully qualified name of the test definition to use (e.g.,
columnValueMaxToBeBetween).string
required
Fully qualified name of the test suite this test case belongs to.
string
required
Entity link to the target table or column. Format:
<#E::table::tableFQN> for table-level or <#E::table::tableFQN::columns::colName> for column-level.array
Array of parameter name/value pairs as defined by the test definition.
string
Description of the test case in Markdown format.
array
Array of owner references (users or teams) to assign.
POST /v1/dataQuality/testCases
Returns
Returns the created test case object with all specified properties and system-generated fields.Response
string
Unique identifier for the test case (UUID format).
string
Test case name.
string
Fully qualified name in format
table.column.testCaseName or table.testCaseName.string
Description of the test case.
object
Reference to the test definition.
object
Reference to the test suite.
string
Entity link to the target table or column.
array
Parameter values for this test case.
array
List of owners assigned to the test case.
number
Version number for the entity (starts at 0.1).
Create or Update (PUT)
UsePUT /v1/dataQuality/testCases instead of POST to perform an upsert. If a test case with the same fullyQualifiedName already exists, it will be updated; otherwise, a new test case is created. The request body is the same as POST.
PUT will not return a 409 conflict error if the entity already exists — it will update the existing entity instead. However, for certain fields (such as description, tags, owners, and custom properties), PUT preserves an already-populated value instead of overwriting it with an empty or omitted one — the exact behavior depends on the field and the calling user or bot’s permissions, not a blanket rule. See Entity Update Behavior for the full preserve/merge rules. Use PATCH to intentionally replace an existing value.