Skip to main content

Received Referrals Endpoints

Base URL: https://api.casexchange.com/api/public/v1 These endpoints provide a receiver-centric view of referrals sent to your firm, with flexible ID resolution (UUID, reference number, or CMS ID).

GET /received-referrals

Returns a paginated list of referrals received by your firm. Lean response shape includes only summary fields. Tier: read_only Query parameters:
Response 200

GET /received-referrals/

Returns full detail for a single received referral. The {id} parameter accepts a UUID, reference number, or CMS ID — the server resolves whichever format you provide. PII masking: When the referral status is sent, client PII fields (clientFirstName, clientLastName, clientEmail, clientPhone, clientDateOfBirth) along with description, notes, incidentDate, and leadAttorneyName are masked and returned as null. PII is revealed once the receiver moves the referral to under_evaluation or any later status. Tier: read_only
You can also look up by reference number or CMS ID:
Response 200 — status is under_evaluation (PII visible)
Response 200 — status is sent (PII masked) When the referral has not yet been evaluated, PII fields are returned as null:

GET /received-referrals//available-statuses

Returns the current status and the available next status transitions for a received referral. Each transition indicates whether a reason or closing status is required. Use this before presenting status-change options in your UI or before calling a status-update endpoint. Tier: read_only
Response 200
A referral in in_litigation status might show a closing transition that requires a closing status:

PATCH /received-referrals/

Partially updates fields on a received referral. Only the fields you include in the request body are changed; omitted fields remain unchanged. At least one field must be provided. Tier: standard Updatable fields:
Response 200 The response returns the full updated referral detail: