Skip to main content
PATCH
/
tasks
Update Task
curl --request PATCH \
  --url https://api.lemlist.com/api/tasks \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": "opp_AbkAqfvTJtdR7mdZ5"
}
'
{
  "_id": "opp_muTZMDjKf7vtanEk9",
  "type": "manual",
  "title": "Check him out",
  "priority": 2,
  "dueDate": "2025-10-31T07:58:00.000Z",
  "userId": "usr_gmHgNGRcGPSTJrDbT",
  "content": "Really glad we started using lemlist"
}
This endpoint uses the Task object.

​
Updatable Fields

All fields are optional except id:
  • Assignment: Change the assigned team member with assignedTo
  • Schedule: Update the dueDate
  • Details: Modify title or message content
  • Priority: Set priority level (0=low, 1=medium, 2=high, ""=none)
  • Status: Mark as complete with done: true
Examples: 
{
    "id": "opp_abc123",
    "done": true
}

Authorizations

​
Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Body

application/json
​
id
string
required

The unique identifier of the task to update

​
assignedTo
string

The ID of the team member to assign the task to (userId)

​
dueDate
string<date-time>

Updated due date in ISO 8601 format

​
title
string

Updated task title

​
message
string

Updated task message/description

​
priority
enum<string>

Priority level of the task

Available options:
,
0,
1,
2
​
done
boolean

Mark task as completed

Response

Success

A manual action assigned to a user to complete.

​
_id
string

Unique task identifier

​
type
string

Task type

​
leadId
string

Associated lead ID

​
campaignId
string

Campaign ID

​
userId
string

Assigned user ID

​
status
enum<string>

Task status

Available options:
pending,
completed,
ignored
​
dueDate
string<date-time>

Due date timestamp

​
createdAt
string<date-time>

Creation timestamp

​
completedAt
string<date-time>

Completion timestamp