Skip to main content
PATCH
Update supplied task properties while preserving omitted values. Use a developer access key. See authentication, errors, and rate limits. Required scopes: tasks:write. Task access uses the owner’s current workspace role. Non-admin members can access tasks they created or are assigned to; inaccessible tasks return 404. See task visibility. Archived tasks return 404. linked_record_ids is only accepted by task creation, not this route.

Parameters

string
required
Task ID accessible to the key owner.
string
1–500 characters.
string
Up to 100,000 characters.
string
Workspace task-status slug.
string
One of no_priority, low, medium, high, urgent.
number | null
Unix milliseconds; null clears the start date.
number | null
Unix milliseconds; null clears the due date. Start must not be later than due date.
string | null
Accessible parent task ID; null clears the parent.
string[]
Up to 50 workspace auth-user IDs. Replaces the assignee list; [] clears it.
integer | null
Positive minutes; null clears the estimate.

Response

200 — Returns the resource under data. Example IDs and values are illustrative.
Set path-ID environment variables to values returned by your workspace before running the request. This request changes workspace data. A timeout does not prove that the write failed; inspect the result before retrying.