--- title: "Get DQ evaluation results in bulk" method: POST path: "/data-quality/v1/results/dq-evaluation/bulk" tags: ["Data Quality Monitor Processing"] --- # Get DQ evaluation results in bulk `POST /data-quality/v1/results/dq-evaluation/bulk` ## Request - Base URL: `https://your-environment.ataccama.one/api` - URL: `https://your-environment.ataccama.one/api/data-quality/v1/results/dq-evaluation/bulk` - Auth: HTTP bearer - TypeScript: (a function with typed inputs; its response is checked against the schema) Retrieve the DQ evaluation results of multiple DQ monitors in a single request. Use this endpoint for dashboards or reports spanning multiple data assets. Each request can include up to 100 catalog item and DQ monitor pairs. The bulk endpoint always returns results from the latest completed processing for each monitor, and returns a simplified result structure containing only `overallQuality` and `dimensionResults` for each monitor. It does not include `dqAttributeResults` or `overallDqFindings`. To get attribute-level, rule-level, and alert finding details, use [Get DQ evaluation results](#tag/data-quality-monitor-processing/GET/data-quality/v1/catalog-items/{catalogItemUrn}/dq-monitors/{dqMonitorUrn}/processings/{workflowUrn}/results/dq-evaluation) for each monitor individually. The `dimensionResults` array in the bulk response uses the `dimensionUrn` field instead of the nested `dimension` object returned by [Get DQ evaluation results](#tag/data-quality-monitor-processing/GET/data-quality/v1/catalog-items/{catalogItemUrn}/dq-monitors/{dqMonitorUrn}/processings/{workflowUrn}/results/dq-evaluation). The response contains a `data` array of result objects. A requested pair with no completed processing is omitted from `data`, so the response can contain fewer items than the request. ## Request body - object: Request payload for bulk DQ evaluation results. - `filter` CatalogItemDqMonitorPair[], required - `catalogItemUrn` string, uri, required: A URN identifying a catalog item resource in the Catalog API. Format: urn:ata:{tenant}:catalog:catalog-item:{uuid} Example: urn:ata:acme-corp:catalog:catalog-item:123e4567-e89b-12d3-a456-426614174000. - `dqMonitorUrn` string, uri, required: A URN identifying the DQ monitor resource in the Data Quality API. Format: urn:ata:{tenant}:data-quality:dq-monitor:{uuid} Example: urn:ata:acme-corp:data-quality:dq-monitor:123e4567-e89b-12d3-a456-426614174000. ## Response `200` Bulk DQ evaluation results. - object - `data` DqEvaluationResultsBulkItem[], required - `catalogItemUrn` string, uri, required: A URN identifying a catalog item resource in the Catalog API. Format: urn:ata:{tenant}:catalog:catalog-item:{uuid} Example: urn:ata:acme-corp:catalog:catalog-item:123e4567-e89b-12d3-a456-426614174000. - `dqMonitorUrn` string, uri, required: A URN identifying the DQ monitor resource in the Data Quality API. Format: urn:ata:{tenant}:data-quality:dq-monitor:{uuid} Example: urn:ata:acme-corp:data-quality:dq-monitor:123e4567-e89b-12d3-a456-426614174000. - `workflowUrn` string, uri, required: A URN identifying a processing workflow. Format: urn:ata:{tenant}:processing:workflow:{uuid} Example: urn:ata:acme-corp:processing:workflow:123e4567-e89b-12d3-a456-426614174000. - `processingStartedAt` string, date-time: Timestamp when the processing started. - `processingFinishedAt` string, date-time: Timestamp when the processing finished. - `overallQuality` OverallQuality: Passed and failed record counts of a DQ evaluation. To calculate the quality percentage, divide `passedCount` by the sum of the two counts. - `passedCount` integer: Number of records that passed the DQ evaluation. - `failedCount` integer: Number of records that failed the DQ evaluation. - `dimensionResults` DqDimensionProcessingResultNoEnrichment[]: Quality breakdown by dimension, with passed and failed counts and the number of rule instances contributing to each dimension. - `dimensionUrn` string, uri, required: A URN identifying the DQ dimension resource in the Data Quality API. Format: urn:ata:{tenant}:data-quality:dq-dimension:{uuid} Example: urn:ata:acme-corp:data-quality:dq-dimension:123e4567-e89b-12d3-a456-426614174000. - `passedCount` integer: Number of records that passed the DQ evaluation in this dimension. - `failedCount` integer: Number of records that failed the DQ evaluation in this dimension. - `ruleInstanceCount` integer: Number of rule instances contributing to this dimension. - `dataSlice` ProcessingResultsDataSlice: The data slice a processing ran on, as recorded when it ran. It does not change when the monitor's slice is edited or removed later. The record describes what was run, not how the monitor is defined. Every date condition is recorded as `BETWEEN` with its two resolved bounds in `resolvedValues`; `values` holds the relative period for `LAST_DAY`, `LAST_MONTH`, `LAST_QUARTER`, and `LAST_YEAR`, and is empty for `DATE_RANGE`. All other operators are recorded as configured. The property is absent when the processing used neither a saved slice nor an override. - `label` string: Display name of the slice the run used. - `overridden` boolean, required: `true` when the processing was started with a `dataSliceOverride` instead of the monitor's saved slice. An override with no predicates appears as `overridden: true` with an empty `predicates` list: the run deliberately read all rows. - `predicates` object[], required: The conditions the run applied, all of which held. Empty only for an override with no predicates. - `attributeName` string, required: Name of the attribute the condition applied to. - `operator` string, required: @ExtensibleEnum The comparison the run applied. `BETWEEN` is a resolved date range. Treat any value you do not recognize as an opaque label. - `values` string[], required: The values as authored. One for a comparison, several for a list, none for a null check. For `BETWEEN`, the relative period such as `LAST_DAY`, or none for a `DATE_RANGE`. - `resolvedValues` string[], required: The values the run actually used. Equal to `values` for a static condition; for `BETWEEN`, the two resolved bounds. ## Other responses - `400`: Bad request. The request parameters or body are invalid. - `403`: Forbidden. You do not have permission to access the requested resource. --- [API](https://skmtc.dev/ataccama/apis/ataccama-one-agentic-data-trust-platform-public-api.md) - [All operations](https://skmtc.dev/ataccama/apis/ataccama-one-agentic-data-trust-platform-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/ataccama/apis/ataccama-one-agentic-data-trust-platform-public-api/revisions/46f16e0487f8?raw)