Data Freshness

Use this endpoint when you want to define a new Data Freshness policy for an asset.

A Data Freshness policy lets you enforce SLAs on when data should arrive (and optionally volume/record-count–type checks), and configure alerting so business and operations teams are notified when data is late or missing.

Typical use cases:

• Set an SLA like “this table must be updated every hour”

• Alert if expected files don’t arrive in a landing bucket

• Track freshness of critical fact/dimension tables for dashboards

Endpoint

POST /catalog-server/api/rules/data-cadence

Path / Query Parameters

This endpoint does not define path or query params; only headers and a JSON body are required.

Sample Request

curl -X POST "{HOST}/catalog-server/api/rules/data-cadence" \
 -H "accessKey: <YOUR_ACCESS_KEY>" \
 -H "secretKey: <YOUR_SECRET_KEY>" \
 -H "Content-Type: application/json" \
 -H "Accept: application/json" \
 -d '{
    "rule": {
      "name": "MY_EMPLOYEES-fresh-and-vol-policy-1202692",
      "description": "Monitor daily freshness and volume for MY_EMPLOYEES",
      "type": "DATA_CADENCE",
      "enabled": true,
      "thresholdLevel": {
      	"type": "ABSOLUTE",
      	"config": {
        	"direction": "ABOVE",
        	"success": 100,
        	"warning": 70
      	}
    	},
      "notificationChannels": {
        "alertsEnabled": true,
        "configuredNotificationGroupIds": [4522],
        "notifyOn": [],
        "notifyOnSuccess": false,
        "reNotifyFactor": 0,
        "severity": "CRITICAL"
      },
      "tags": []
    },
    "details": {
      "backingAsset": {
        "tableAssetId": 1202692
      },
      "configuration": {
        "cadence": "DAILY",
        "expectedTime": "09:00",
        "timeZone": "UTC"
      }
    }
  }'

This example mirrors the structure shown in the OpenAPI examples for Data Freshness rules (with rule and details objects containing things like name, type: DATA_CADENCE, thresholdLevel, notificationChannels, backingAsset, etc.).