Case Linkage
Create an investigation case from a batch of Frontier transactions.
Create a case from Frontier transactions
Creates a ThinkLP investigation case and links a batch of Frontier point-of-sale transactions to it as snapshots.
The API resolves each transaction's employee to a canonical Person and attaches that Person to the case as an involved person. When a Contact has no canonical Person, the API provisions one. When an employee cannot be resolved, the request fails.
The API also provisions each line item as a canonical Item and attaches it as a case item. It aggregates line items case-insensitively by SKU.
The whole operation is transactional. Any failure rolls back the case and every link. A write that the platform rejects returns 400 INVALID_CASE_PAYLOAD, and the message names the platform status code and the rejected fields. A duplicate transaction id returns 409 ALREADY_LINKED instead.
Create a case from Frontier transactions › Request Body
Case header for the investigation case to create. These fields map to the Theft Case API. See that reference for the authoritative and complete field list. This endpoint derives the case's involved persons and case items from the transactions' employees and line items. It ignores any value you supply here for those collections.
Frontier transactions to snapshot and link. Must contain at least one entry.
Create a case from Frontier transactions › Responses
Case created and transactions linked.
caseIdSalesforce Id of the created investigation case.
caseUrlAbsolute URL to the created case record.
linkedTransactionCountNumber of transactions snapshotted and linked.
linkedInvolvedPersonCountDistinct employees resolved to Persons and attached as involved persons.
skippedEmployeeCountRetained for wire compatibility, and always 0. An employee that cannot be resolved to a Person fails the request instead.
linkedCaseItemCountDistinct line-item SKUs provisioned as Items and attached as case items.