# Create Data Monitor

Create a new data monitor.

Data monitor is a concept for asynchronous processing of data curation and data validation.

Data monitors should be unique by a pair:  + .

Data monitor can be created only for DATA_MIRROR storage, having  set to true.

Available execution types:
  * TRIGGER - causes reevaluation of data whenever CDQ Business Partner model of your data has changed
              or whenever linked reference data has changed
  * JOB - reevaluates data every specified period of time.

Note: creation of data monitor starts background process that is invoked for all
Business Partners from data monitor scope.


Endpoint: POST /v2/storages/{storageId}/datamonitors
Version: 5
Security: apiKey

## Path parameters:

  - `storageId` (string, required)
    Unique identifier of the Storage.
    Example: "72d6900fce6b326088f5d9d91049e3e6"

## Request fields (application/json):

  - `type` (object, required)
    Type of the Data Monitor.

  - `type.technicalKey` (string, required)
    Technical key of a data monitor.
    Enum: "AUGMENTATION", "DATA_QUALITY_PROFILING", "SCREENING", "DUPLICATE"

  - `dataSources` (array, required)
    List of Data Sources.

  - `dataSources.id` (string, required)
    Unique identifier for a Data Source of the Storage.
    Example: "648824a691d8d2503d65103e"

  - `enabled` (boolean)
    The toggle used to enable or disable the Data Monitor.
    Example: true

  - `configuration` (object)
    Configuration which is used during processing Business Partners.

  - `configuration.id` (string, required)
    Uniquely identifies a configuration.
    Example: "c074b9f3-abf0-4f8e-9a20-74deb6cfa2a4"

  - `executions` (array, required)
    Available executions of data monitor.

  - `executions.type` (object, required)
    Type of the Data Monitor Execution.

  - `executions.type.technicalKey` (string, required)
    Technical key of the Data Monitor Execution Type.
    Enum: "TRIGGER"

  - `executions.frequency` (string)
    List of Data Monitor Frequency parapeters.
    Enum: "BI_WEEKLY", "MONTHLY", "QUARTERLY"

  - `validitySpan` (object)
    Period after which Business Partner is evaluated again.

  - `validitySpan.technicalKey` (string)
    Validity span period.
    Enum: "HALF_YEAR", "QUARTER", "YEAR"

  - `featuresOn` (array)
    Features to be activated for Data Monitor.
    Enum: "BUILD_REPORT"

  - `scopes` (array)
    Scope to be enabled for monitor.

  - `scopes.technicalKey` (string)
    Data Monitor scope of selected products.

Augmentation Data Monitor may be one of:
* AUGMENTED_BUSINESS_PARTNERS - enables Business Partner Augmentation
* RAW_UPDATES - enables Raw Updates
* OVERLAP - enables Overlap

By default, when empty in Augmentation Data Monitor, below are enabled:
* AUGMENTED_BUSINESS_PARTNERS
* RAW_UPDATES
    Example: "RAW_UPDATES"

## Response 200 fields (application/json):

  - `id` (string)
    Unique alpha-numeric number of the Data Monitor.
    Example: "bfdfd6f7-562f-4d4a-921f-e68cba60d5cf"

  - `type` (object)
    Type of the Data Monitor.

  - `type.name` (string)
    Display name of the Data Monitor Type.
    Example: "Augmentation"

  - `type.technicalKey` (string)
    Technical key of a data monitor.
    Example: "AUGMENTATION"

  - `dataSources` (array)
    List of Data Sources.

  - `dataSources.id` (string)
    Unique identifier for a Data Source of the Storage.
    Example: "648824a691d8d2503d65103e"

  - `dataSources.name` (string)
    Name of a data source of a storage.
    Example: "Internal customers"

  - `enabled` (boolean)
    The toggle used to enable or disable the Data Monitor.
    Example: true

  - `disabledAt` (string)
    Date in ISO-8601 format when data monitor was disabled.
    Example: "2025-09-09T13:03:09Z"

  - `configuration` (object)
    Configuration which is used during processing Business Partners.

  - `configuration.id` (string)
    Uniquely identifies a configuration.
    Example: "c074b9f3-abf0-4f8e-9a20-74deb6cfa2a4"

  - `executions` (array)
    Available executions of data monitor.

  - `executions.type` (object, required)
    Type of the Data Monitor Execution.

  - `executions.type.technicalKey` (string, required)
    Technical key of the Data Monitor Execution Type.
    Example: "TRIGGER"

  - `executions.frequency` (string)
    It is the interval at which updates are performed.
    Example: "BI_WEEKLY"

  - `validitySpan` (object)
    Period after which Business Partner is evaluated again.

  - `validitySpan.technicalKey` (string)
    Validity span period.
    Example: "YEAR"

  - `scopes` (array)
    Scope of data monitor.

  - `scopes.technicalKey` (string)
    Data Monitor scope of selected products.

Augmentation Data Monitor may be one of:
* AUGMENTED_BUSINESS_PARTNERS - enables Business Partner Augmentation
* RAW_UPDATES - enables Raw Updates
* OVERLAP - enables Overlap

By default, when empty in Augmentation Data Monitor, below are enabled:
* AUGMENTED_BUSINESS_PARTNERS
* RAW_UPDATES
    Example: "RAW_UPDATES"

  - `createdAt` (string)
    Date of creation (ISO 8601-compliant).
    Example: "2025-09-09T13:03:09Z"

  - `createdBy` (string)
    Creator of a resource.
    Example: "76248934691294444"

  - `modifiedAt` (string)
    Date of modification (ISO 8601-compliant).
    Example: "2025-09-09T13:03:09Z"

  - `modifiedBy` (string)
    User or Client UUID which modified the resource.
    Example: "76248934691294444"

  - `featuresOn` (array)
    Features to be activated for Data Monitor.
    Example: ["BUILD_REPORT"]