Actions69
- Additional Information Category Actions
- Case File Actions
- Client Fee Actions
- Collision Actions
- Contact Actions
- Deadline Actions
- Department Actions
- Document Actions
- Document Template Actions
- Expenditure Actions
- Expense Actions
- Folder Actions
- Invoice Actions
- Note Actions
- Resubmission Actions
- RVG Fee Actions
- Task Actions
- Third Party Cost Actions
- User Actions
Case File → Update
AI-generatedSummary
Updates a case file identified by its sequential number and reference year. Sends the required involved parties plus any supplied case details, staff assignments, file role, parent file, and additional fields in the request body.
Inputs
- Sequential Number (required) — The case file’s sequential number.
- Reference Year (required) — The case file’s reference year.
- File Name — Optional replacement file name.
- Alternative Reference — Optional alternative file reference.
- Clerk Name or ID — Optional clerk selection or ID; sent as a clerk ID object.
- Assistant Names or IDs — Optional assistant selections or IDs; sent as a list of assistant ID objects.
- Involved Parties (required) — One or more parties. Each requires a contact ID, main and sub-role, and can include a file reference, tax treatment, tax-deductible flag, contact persons, and sub-involved parties with roles and claim or insurance numbers.
- File Role — Optional file role: Main File or Sub File.
- Parent File Number — Parent file number, shown for Sub File role and sent as the parent file’s case number.
- Additional Fields — Optional additional information entries and typed field values, areas of law, department, dispute value, keywords, and reason.
- Request Options — Optional batching, SSL certificate validation, HTTP proxy, and request timeout settings.
Output shape
A list of items containing the API response for the case-file update.
The source pack provides only a signature-level view of the request implementation, so it does not establish the exact response fields or whether the response is transformed.