Update a task
Updates a task. This includes marking it as done. Assignees you pass will be updated, see their individual endpoints for more details on how this is done. To update labels, see the description of the endpoint.
Path parameters
The Task ID
Request body
The bucket id. Will only be populated when the task is accessed via a view with buckets. Can be used to move a task between buckets. In that case, the new bucket must be in the same view as the old one.
Comment count of this task. Only present when fetching tasks with the expand parameter set to comment_count.
If this task has a cover image, the field will return the id of the attachment that is the cover image.
A timestamp when this task was created. You cannot change this value.
A timestamp when this task was deleted. Soft-deleted tasks are kept for 30 days before they are removed permanently. omitzero keeps the field out of the JSON of regular tasks — it only ever appears on soft-deleted ones (the later trash listing).
The task description.
Whether a task is done or not.
The time when a task was marked as done. This field is system-controlled and cannot be set via API.
The time when the task is due.
When this task ends.
The task color in hex
The unique, numeric id of this task.
The task identifier, based on the project identifier and the task's index
The task index, calculated per project
True if a task is a favorite task. Favorite tasks show up in a separate "Important" project. This value depends on the user making the call to the api.
Determines how far a task is left from being done
The position of the task - any task project can be sorted as usual by this parameter. When accessing tasks via views with buckets, this is primarily used to sort them based on a range. Positions are always saved per view. They will automatically be set if you request the tasks through a view endpoint, otherwise they will always be 0. To update them, take a look at the Task Position endpoint.
The task priority. Can be anything you want, it is possible to sort by this later.
The project this task belongs to.
An amount in seconds this task repeats itself. If this is set, when marking the task as done, it will mark itself as "undone" and then increase all remindes and the due date by its amount.
When this task starts.
Time entry count of this task. Only present when fetching tasks with the expand parameter set to time_entries_count.
The task text. This is what you'll see in the project.
A timestamp when this task was last updated. You cannot change this value.
Response
The updated task object.
The bucket id. Will only be populated when the task is accessed via a view with buckets. Can be used to move a task between buckets. In that case, the new bucket must be in the same view as the old one.
Comment count of this task. Only present when fetching tasks with the expand parameter set to comment_count.
If this task has a cover image, the field will return the id of the attachment that is the cover image.
A timestamp when this task was created. You cannot change this value.
A timestamp when this task was deleted. Soft-deleted tasks are kept for 30 days before they are removed permanently. omitzero keeps the field out of the JSON of regular tasks — it only ever appears on soft-deleted ones (the later trash listing).
The task description.
Whether a task is done or not.
The time when a task was marked as done. This field is system-controlled and cannot be set via API.
The time when the task is due.
When this task ends.
The task color in hex
The unique, numeric id of this task.
The task identifier, based on the project identifier and the task's index
The task index, calculated per project
True if a task is a favorite task. Favorite tasks show up in a separate "Important" project. This value depends on the user making the call to the api.
Determines how far a task is left from being done
The position of the task - any task project can be sorted as usual by this parameter. When accessing tasks via views with buckets, this is primarily used to sort them based on a range. Positions are always saved per view. They will automatically be set if you request the tasks through a view endpoint, otherwise they will always be 0. To update them, take a look at the Task Position endpoint.
The task priority. Can be anything you want, it is possible to sort by this later.
The project this task belongs to.
An amount in seconds this task repeats itself. If this is set, when marking the task as done, it will mark itself as "undone" and then increase all remindes and the due date by its amount.
When this task starts.
Time entry count of this task. Only present when fetching tasks with the expand parameter set to time_entries_count.
The task text. This is what you'll see in the project.
A timestamp when this task was last updated. You cannot change this value.