Skip to main content

Get Case

Retrieve a case by its UUID, including linked documents, AI-generated narrative summary, label, status, and anomaly count. One call to assess case health.

GET /v1/cases/:key retrieves the full detail of one case: the documents grouped into it by document linking, an AI-generated narrative summary of how they relate, and the count of open anomalies. The key path parameter is the case UUID (the stable id returned by the list endpoint).

Call this endpoint after listing cases to drill into a specific case. The typical workflow is to list cases with filters, then fetch detail for cases that need review. The response includes the full document list and anomaly count, so you can assess case health in a single call.

The response includes documents (array of document objects with id, filename, document_type, and created_at), a narrative string (or null if narration has not been triggered), and anomaly_count. The links object provides convenience URLs for the case itself and its documents list.

Pair with GET /v1/cases/:key/edges to inspect the field-level linking evidence (which field and value connect each pair of documents). If anomaly_count is non-zero, the open findings behind it are visible in the platform’s Business Cases view.

The narrative field is produced by the case-synthesis rebuild (it narrates each case as part of the build). It is null until the first synthesis run covering this case completes.
GET/v1/cases/:key

Path parameters

key*stringCase UUID (the stable resource id).

Request

curl https://api.talonic.com/v1/cases/5c7fa78c-4d92-4613-9f42-9fe74458d8a9 \
  -H "Authorization: Bearer $TALONIC_API_KEY"

Response

Response fields

idstringCase UUID — the stable resource id.
case_keystringStable content-derived case key (hex), distinct from the resource id.
labelstring | nullHuman-readable display name for the case.
narrativestring | nullAI-generated narration summarizing the case.
documentsarrayDocuments belonging to the case.
documents[].idstringDocument UUID.
documents[].filenamestringDocument filename.
documents[].document_typestring | nullInferred document type.
documents[].created_atstring | nullISO 8601 document creation timestamp.
documents[].pinnedbooleanWhether the document is pinned to the case.
anomaly_countintegerNumber of open findings on this case.
created_atstring | nullISO 8601 timestamp of the first document in the case.
links.selfstringURL of this case.
links.documentsstringURL to list documents in this case.
links.anomaliesstringURL of the case anomalies (risk surface) endpoint.
links.evidencestringURL of the case evidence endpoint.

Response

{
  "id": "5c7fa78c-4d92-4613-9f42-9fe74458d8a9",
  "case_key": "8c1ca050535e3ea3",
  "label": "Acme Corp Q4 Invoices",
  "narrative": "Five invoices from Acme Corp spanning Q4 2024 share a common vendor ID and billing address. Total value is $72,450 with two anomalies flagged for review.",
  "documents": [
    {
      "id": "doc_uuid_1",
      "filename": "invoice_oct.pdf",
      "document_type": "Invoice",
      "created_at": "2024-10-01T08:30:00.000Z",
      "pinned": false
    },
    {
      "id": "doc_uuid_2",
      "filename": "invoice_nov.pdf",
      "document_type": "Invoice",
      "created_at": "2024-11-05T09:15:00.000Z",
      "pinned": true
    }
  ],
  "anomaly_count": 2,
  "created_at": "2024-10-01T08:30:00.000Z",
  "links": {
    "self": "/v1/cases/5c7fa78c-4d92-4613-9f42-9fe74458d8a9",
    "documents": "/v1/cases/5c7fa78c-4d92-4613-9f42-9fe74458d8a9/documents",
    "anomalies": "/v1/cases/5c7fa78c-4d92-4613-9f42-9fe74458d8a9/anomalies",
    "evidence": "/v1/cases/5c7fa78c-4d92-4613-9f42-9fe74458d8a9/evidence"
  }
}

Errors

Error responses

400bad_requestInvalid case id. Must be a UUID.
401unauthorizedMissing or invalid API key.
404not_foundNo case with this key exists for your organization.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

Frequently asked questions

What is the case narrative?+
The narrative is an AI-generated summary produced by Claude during the case-synthesis rebuild. It describes the relationships, patterns, and key facts across the documents in the case.
Why is the narrative field null?+
Narration is produced as part of the synthesis rebuild. The field stays null until the first rebuild covering this case completes (triggered from the platform, or automatically when ingestion runs with the build-cases toggle on).
What does anomaly_count measure?+
The number of open findings on the case, such as dangling references to documents that appear to be missing. Use GET /v1/cases/:key/anomalies for the detailed list behind the count.

Related

List Cases
Case Operations
Case Evidence