Begin closing workflow for a referral
First step of the two-step close workflow. Transitions a referral from SIGNED or IN_LITIGATION to CLOSING. Only closingStatus is required. Optional reason is written to the status_updates row’s message. Optional closureReason is written to the formal closure-reason column on the case (required at the service layer when closingStatus is no_longer_pursuing). Settlement financials are optional but recommended for won_settled. Only the referent firm may call this endpoint. The second step — finalization — is POST /referrals/{id}/close. Tier: FULL.
Authorizations
Public API key (format cxp_<tier>_<body>, tier = ro|std|full). Scoped to a single firm. The firm must have public_api in allowedIntegrations.
Path Parameters
Referral UUID
Body
ClosingStatus enum value (e.g. won_settled, lost, no_longer_pursuing)
"won_settled"
Optional free-text note. Written to the status_updates row generated by the transition. CR/LF characters are stripped server-side.
1 - 5000"Settlement reached and client approved disbursement."
Optional formal closure reason. Written to the case record's closureReason column. Required at the service layer when closingStatus is no_longer_pursuing. CR/LF characters are stripped server-side.
1 - 5000"Mediated settlement; both parties signed release."
Total settlement amount in USD
Client fee agreement percentage as a decimal (0–1)
0 <= x <= 1Attorney fees in USD
Estimated date funds will be distributed (ISO date)