Skip to main content
PATCH
Update a task
Update an existing task, updating only the provided fields and leaving the rest of the task’s data unchanged. To move a task to a different entity, provide a new entity.id. Omit entity entirely to keep the task on its current entity. This endpoint does not change completedAt — use Mark a task as done or Mark a task as to do to change completion state.

Authorizations

Authorization
string
header
required

API key for authentication

Path Parameters

taskId
string
required

The ID of the task to update.

Required string length: 40

Body

application/json
title
string

The title of the task.

Maximum string length: 255
Example:

"Follow up with John Doe"

dueAt
string<date>

The due date of the task, in YYYY-MM-DD format.

Required string length: 10
Example:

"2025-07-17"

dueTime
string | null

The due time of the task, in HH:mm format.

Required string length: 5
Example:

"15:00"

description
string | null

The description of the task, in markdown format.

Maximum string length: 10000
Example:

"Discuss the Q3 proposal."

recurrenceFrequency
enum<string> | null

The recurrence frequency of the task. One of: weekday, weekly, biweekly, monthly, quarterly, yearly. Null if non-recurring.

Available options:
weekday,
weekly,
biweekly,
monthly,
quarterly,
yearly,
null
assignedUsers
object[]

Users to assign to this task. Accepts user IDs or emails, not both. If omitted, the task is assigned to the current user (the API key owner).

Maximum array length: 50
isPublic
boolean

Whether the task is visible to all workspace members (true) or only to its assigned users (false).

Example:

true

entity
object

The entity to move the task to. Omit to keep the current entity. You can link people, companies and deals.

Example:

Response

The task updated in the workspace.

data
object
required

A task created by a user.

Example:
deprecations
string[]
Example: