Tasks
Update task
Update any task field, including archiving and accepting drafts.
PATCH
Only the fields you send are changed, and
{} does nothing.
An explicit null clears these fields: description, additional_context, assigned_to, assigned_agent, assigned_team_id, complete_by, matter_id. So {"assigned_to": null} unassigns the task. For every other field a null is ignored rather than applied — send a real value (an empty array to empty tags or linked_items).
State changes are fields rather than separate endpoints:
Archiving and drafting are orthogonal to
status: an archived task keeps the status it had.
People, agents and teams can be referenced by id or by name: a person by user id, email address or name, or me for your API key’s user; an agent by its id, name or shortcut; a team by id or name. A reference that matches more than one record is rejected with a 400 that lists the candidates, so pass the id to disambiguate. me added 2026-10-25.
In the response, assigned_agent.id is the agent’s record id and assigned_agent.counsel_id is the agent id List agents returns; either is accepted in assigned_agent. counsel_id added 2026-09-05.
Body parameters
Replaces the whole link list. Each item takes
type, id, and optionally role and context, as in Link items. A link the task already has keeps its role and context unless the item sends them. To change one link, use Update link.Replaces the set of people involved in the task. Each entry is a user id, email address, name, or
me for the caller.