Tasks
The Tasks API provides CRUD access to project tasks, plus ancillary actions for status, assignment, tags, archive/activate, clone, comments and timers.New to the API? Start with Getting started (base URL, response envelope, errors, pagination) and Authentication (API keys). Those conventions apply to every endpoint below and are not repeated here.
Identifier note: tasks are addressed by their numerictask_idand always belong to a project (task_projectid).task_statusis ataskstatus_idandtask_priorityis ataskpriority_id.
Scope: starting/stopping individual timers, recurring settings, task dependencies, per-user
notes, attachments/cover image, kanban position, bulk actions and pinning are managed in-app
and are not part of this API. Checklists on a task are handled by the
Checklists API (resource_type=task). Timers are read-only here, plus a
stop-all command.
The task object
List / search tasks
{ data, meta, message } (200).
Get a task
200), message “Task retrieved successfully.”
Create a task
201), message “Task created successfully.”
Update a task
200), message “Task updated successfully.”
Delete a task
{ "data": { "id": 120 }, "message": "Task deleted successfully." }.
Change status
200), message “Task status updated successfully.”
Set assigned team members
200), message “Task assignees updated successfully.”
Set tags
Archive / activate
active_state between archived and active.
Clone a task
201), message “Task cloned successfully.”
Timers
Timers are read-only via the API, plus a stop-all command.List timers
[{ id, user: {id,name}, started, stopped, time, status, billing_status }].
Stop all running timers
{ "data": { "id": 120 }, "message": "..." }.