Tasks

Update a single Task

Changed on

Outlines the parameters and data fields used when updating a single Task

A Task can be assigned to up to 10 firm users, or to one Contact, but never both.

  • Send assignees to set the firm-user set. The list replaces the existing assignees rather than adding to them. The response order may differ from the order submitted.
  • Send assignee (with both id and type) to assign a single User or Contact. Sending it to a Task that currently has several assignees collapses the set down to that one assignee.
  • The two are mutually exclusive: sending both is rejected, and so is an empty assignees list.
  • Reading back: assignees lists the firm users the Task is assigned to, and assignee is one of them. assignees is [] in every other case, including a Contact assignee. An unassigned Task returns assignee as null and assignees as [].
patch/tasks/{id}.json

Request

  • Base URL
    https://app.clio.com/api/v4
  • URL
    https://app.clio.com/api/v4/tasks/{id}.json
  • Auth
    none declared

Path parameters

idinteger required

The unique identifier for the Task.

Query parameters

fieldsstring

The fields to be returned. See response samples for what fields are available. For more information see the fields section.

Headers

IF-MATCHstring

The server will update the requested resource and send back a 200 status, but only if value in the header matches the existing resource's ETag.

X-API-VERSIONstring

The API minor version. Default: latest version.

Request body

Response

Ok

Changes

    • info

      added the optional property //// to the response with the status

    • warning

      added the new FixedFee enum value to the //// response property for the response status