Skip to content
Docs

Update Reply DraftBeta

Replace the draft text. Sends nothing.

PATCH/api/v1/inbox/threads/{reply_id}/draft

Path Parameters#

reply_idstringpathrequired
The thread (reply) ID.

Body Parameters#

draftReplystringbodyrequired
The new draft text (plain text or HTML), up to 100,000 characters.

Only works while the draft is completed and has not been sent or dismissed.

Response#

dataobject
Show Draft
idstring
Thread (reply) ID.
draftReplystring
Draft text.
draftReplyStatusstring
pending, completed, failed or regenerating.
draftReplyActionstring
null while awaiting a decision, otherwise sending, sent, dismissed or answered (the thread was replied to by hand).
draftReplyErrorstring
A short message when generation failed.
draftReplySentMessageIdstring
SMTP message ID once the draft was sent.
fromEmailstring
The lead who replied.
subjectstring
Subject of the reply.

Errors#

StatusDescription
403Key does not have write scope
404Thread not found
409The draft is not ready, or was already sent, dismissed or answered (detail.code: draft_not_ready, draft_already_sent, draft_dismissed, draft_answered, draft_send_in_progress)

Rate Limit#

  • 120 requests per minute, shared by every write call in your workspace. Fixed 60-second window.
  • Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (unix epoch seconds) and X-RateLimit-Bucket (write).
  • A 429 response includes a Retry-After header (seconds until the bucket resets).

For client-side patterns (Retry-After, exponential backoff, monitoring X-RateLimit-Remaining), see Rate Limiting.

Was this page helpful?
View as MarkdownLast updated November 4, 2026