Attach a person to a Theft Case

post

https://{instance}.my.salesforce.com/services/apexrest/ThinkSDK/thinklp/api/v1/theft-cases/{caseId}/involved-persons

Provide exactly one of these three identifiers:

personId — links an existing canonical Person.
employeeId — resolves an employee Contact to a canonical Person, and provisions one when absent.
inline attributes (displayName and personType).

A request that supplies more than one identifier, or none, returns 400 BAD_REQUEST. Inline attributes require an org whose mapping configuration has a write target for them. When the org has no write target, the API rejects the attach with 400 INVARIANT_VIOLATION and names the unmapped property. The API does not persist a junction that has no identity. The new junction carries the case-side fields: personRole, chargesFiled, actionTaken, isIdentityConfirmed, apprehensionDateTime, notes, and the civil-recovery flags.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

caseId

string

required

Salesforce Investigation record Id of the parent theft case

Body Params

personId

string | null

Canonical Person record Id. Mutually exclusive with employeeId and with inline displayName/personType.

employeeId

string | null

Employee Contact Id, resolved server-side to a canonical Person (found or provisioned) and cleared before the response. Mutually exclusive with personId and with inline displayName/personType.

displayName

string | null

Inline person display name. Mutually exclusive with personId and employeeId.

personType

string | null

Inline person type. Mutually exclusive with personId and employeeId.

personRole

string | null

Case-side role of this person. Required on write.

chargesFiled

string | null

actionTaken

string | null

isIdentityConfirmed

boolean | null

apprehensionDateTime

date-time | null

notes

string | null

Case-side context notes for the new junction.

readyForCivilRecovery

boolean | null

Responses

201Created — new junction body returned.

403Field-level security denial. The running user lacks CRUD or FLS on a required field, or a mapping names a field that does not exist. The message names the column. The response body carries no separate field list.

404Resource not found — the supplied id does not resolve to a Theft record type

500Server error, or an org configuration problem. The code field names the reason: RECORD_TYPE_MISSING — the Theft record type is missing on Investigation__c. INTERNAL_SERVER_ERROR — any other unexpected failure.