Skip to main content
POST
POST /v1/dataQuality/testSuites

Create a Test Suite

Create a new test suite. Logical test suites group test cases across multiple tables. Executable test suites are tied to a specific table.

Body Parameters

string
required
Name of the test suite. Must be unique.
string
Human-readable display name for the test suite.
string
Description of the test suite in Markdown format.
boolean
required
Set to true for an executable test suite (tied to a table), false for a logical test suite (user-defined grouping).
array
Array of owner references (users or teams) to assign.
POST /v1/dataQuality/testSuites

Returns

Returns the created test suite object with all specified properties and system-generated fields.

Response

string
Unique identifier for the test suite (UUID format).
string
Test suite name.
string
Fully qualified name of the test suite.
string
Human-readable display name.
string
Description of the test suite.
boolean
Whether this is an executable (true) or logical (false) test suite.
array
List of owners assigned to the test suite.
number
Version number for the entity (starts at 0.1).

Create or Update (PUT)

Use PUT /v1/dataQuality/testSuites instead of POST to perform an upsert. If a test suite with the same name already exists, it will be updated; otherwise, a new test suite 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.

Error Handling