Skip to main content
PATCH
/
inbox
/
{contactId}
/
drafts
/
{draftId}
Update Draft
curl --request PATCH \
  --url https://api.lemlist.com/api/inbox/{contactId}/drafts/{draftId} \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "subject": "Updated subject",
  "content": "<p>Updated content for the draft.</p>"
}
'
{
  "draft": {
    "_id": "drf_abc123def456789",
    "channel": "email",
    "subject": "Updated subject",
    "cc": [],
    "content": "<p>Updated content for the draft.</p>",
    "attachments": [],
    "source": "api",
    "createdAt": "2025-01-15T10:30:00.000Z",
    "updatedAt": "2025-01-15T11:00:00.000Z"
  }
}
The draftOwner query parameter is required and identifies the draft owner. It accepts either:
  • A userId (e.g., usr_abc123def456789) — used directly
  • A login email (e.g., john@acme.com) — resolved to userId via email lookup
This follows the same pattern as contactOwner in the Lead API. Team membership is verified in both cases.
Validations:
  • If content is provided, it must not be empty and has a max size of 30KB (30,000 characters)
  • content and subject are sanitized for security
  • updatedAt is set automatically

Authorizations

​
Authorization
string
header
required

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

Path Parameters

​
contactId
string
required

Contact ID

​
draftId
string
required

Draft ID

Query Parameters

​
draftOwner
string
required

Draft owner identifier. Accepts either a userId (e.g., usr_abc123def456789) or a login email (e.g., john@acme.com).

Body

application/json
​
subject
string

Draft subject

​
cc
string[]

CC email addresses

​
content
string

Draft content (max 30KB)

​
attachments
object[]

File attachments

​
replyToActivityId
string

Activity ID to reply to

Response

Success

​
draft
object