Case Anomalies

List anomalies detected within a case with severity filtering and dismissed toggle. Dismiss individual anomalies after review.

Anomalies are open findings detected across the documents in a case. The primary finding kind is the dangling reference — a document points at an identifier (a contract number, a parent agreement) that resolves to no document in your workspace, signalling a likely missing document.

Findings are produced by the case-synthesis rebuild and carry a kind, the field and value that raised them, a severity, and a dismissed flag. Dismissed findings stay dismissed across rebuilds.

On the public API, findings surface through GET /v1/cases/:key as anomaly_count (the number of open, undismissed findings on the case) and through GET /v1/cases/:key/completeness, whose missing array lists each open finding with its kind, via_field, and value. Reviewing and dismissing individual findings is done in the platform — the Business Cases view — rather than through dedicated public endpoints.

Monitoring findings programmatically

curl -s "$URL/v1/cases/5c7fa78c-4d92-4613-9f42-9fe74458d8a9/completeness" \
  -H "Authorization: Bearer $API_KEY"

{
  "case_id": "5c7fa78c-4d92-4613-9f42-9fe74458d8a9",
  "document_count": 17,
  "open_findings": 2,
  "dismissed_findings": 1,
  "completeness": 0.894,
  "missing": [
    { "kind": "dangling_reference", "via_field": "parent_agreement_ref", "value": "00129370" }
  ]
}