Delete a drift calculator
The response's `values` field is empty — no structured data is returned.
The response's values field is empty — no structured data is returned.
Authorization
SymetryMLAuth HMAC-SHA256 signature-based authentication: requests are signed with
your secret key and sent with the Customer-ID, Sym-date,
Authorization, Content-MD5 and sym-version headers.
See SymetryML REST API Security
for the signature algorithm and a complete example.
In: header
Path Parameters
User/Customer identifier
Drift calculator identifier
Response Body
application/json
application/json
curl -X DELETE "https://example.com/c1/driftCalculator/dc1"{ "statusCode": 200, "statusString": "cleanup done", "values": {}}{ "statusCode": 500, "statusString": "Generic Exception [java.lang.NullPointerException: Cannot invoke \"com.sml.drift.DriftCalculatorAPI.cleanUp()\" because \"dd\" is null]", "values": {}}Score projects against a fitted drift calculator POST
The request body is a `DriftCalculatorCalculateContext`. The response's `KSVDMap` field returns one result entry per project passed in `projects`, in the same order, each keyed by `datadrift_pca_result`, `datadrift_pca_threshold`, `datadrift_mahalanobis_result`, and `datadrift_mahalanobis_threshold`.
Fit a drift calculator against reference projects POST
The request body is a `StringList` of reference project names. The response's `values.dcfitresult` field is a `DriftCalculatorFitResult`: - **`scoreThresholdValues`**: one 4-element array per reference project, ordered `[pcaScore, pcaThreshold, mahalanobisScore, mahalanobisThreshold]`. The two thresholds are identical across all entries (they describe the fitted calculator, not the individual project). - **`featuresUse`**: only populated when a feature subset is in play; omitted otherwise.