Update Subtask
PUT /tasks/{task_id}/subtasks/{subtask_id}
Patch a subtask. Omitted fields are left alone.
Two exceptions worth knowing. An explicit null on due_date,
assignee_id or task_type CLEARS that field, which is different from
omitting it. And records: [] clears every record link, while omitting
records leaves them unchanged.
expected_updated_at makes the update conditional: if the stored row has
moved on, the write is refused instead of overwriting someone else’s edit.
Authorizations
Parameters
Path Parameters
Parent task id (UUID).
Parent task id (UUID).
Subtask id (UUID).
Subtask id (UUID).
Header Parameters
Request Body required
Patch a subtask. Omitted fields are left alone.
records is the exception: an EMPTY list clears every record link, while
omitting it leaves the links unchanged.
object
object
Responses
200
Successful Response
object
An open envelope for one record, one dashboard or one job receipt.
Open because most of these reads are COMPUTED shapes - an engagement summary, a next-best-step, an intelligence status - that grow with the product, and dropping a field from an advisory read makes it say “nothing to report” rather than “we did not tell you”.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error