Skip to main content
PUT
Update Task

Headers

Authorization
string
required

Bearer [access_token]

Content-Type
string
required

application/json

Path Parameters

taskId
integer<int64>
required

ID of the task or appointment to update.

Required range: x >= 1

Body

application/json

Partial update payload. Only non-null fields are applied.

content
string

Description of the task

Example:

"Send an email to my lead"

startAt
string

When this task/appointment should start. ISO8601 format in specified timezone, e.g., '2026-03-01T15:00:00-08:00'

Example:

"2026-03-01T15:00:00-08:00"

endAt
string

When this task/appointment should end. ISO8601 format in specified timezone, e.g., '2026-03-01T16:00:00-08:00'. For regular tasks, this represents the deadline

Example:

"2026-03-01T16:00:00-08:00"

timeZoneCode
string

Timezone code for this task/appointment

Example:

"America/Los_Angeles"

address
string

Address/location for appointment type tasks

Example:

"123 Main St, Los Angeles, CA"

assignedRoleId
integer<int32>

Lead role the task is assigned to, custom roles included. Takes priority over assignedRole. Must be a role somebody holds on this lead, the same list the Assign To dropdown shows; 400 otherwise. Omit it to keep using assignedRole.

Example:

10

ownerUserId
integer<int64>

Lofty user ID owning the appointment. Must be a member of the caller's team. Omit it and the caller owns the appointment, as before. Ignored for plain tasks.

Example:

844775556213479

participants
object

Extra attendees of the appointment. Ignored for plain tasks.

Response

Task updated. Response body is a simple message envelope.

Generic message response

message
string

Result message

Example:

"Operation successful"