Replies

Edit an AI reply draft

Updates the subject and/or body of an AI reply draft awaiting human review. At least one field must be provided and provided fields must be non-empty. This endpoint never changes the draft's status or sends anything - use POST /reply-drafts/{id}/send once the wording is ready. Emails that are not AI reply drafts - sent or scheduled emails, inbound replies, campaign sequence templates - are refused with 409.

put/reply-drafts/{id}

Request

Base URL: https://api.emailchaser.com/r
URL: https://api.emailchaser.com/r/reply-drafts/{id}
Auth: HTTP bearer

Path parameters

idinteger required

Reply draft ID

Request body

bodystring

subjectstring

Example request

{
  "body": "Thanks for getting back to me - would Tuesday work for a quick call?",
  "subject": "Re: Quick question"
}

Response

The updated reply draft

bodystring

ccstring[]

createdAtstring

idinteger

inReplyToEmailIdinteger

InReplyToEmailID is the inbound reply this draft answers. It is null in the rare case the draft's conversation can no longer be resolved (e.g. the inbound email was deleted).

leadIdinteger

subjectstring

tostring[]

To and Cc are who the draft goes to when sent, as Reply All does it: the person who wrote the reply in To, and everyone else they addressed (their To and Cc lines, minus your workspace's own mailboxes) in Cc.

Example response

{
  "body": "Thanks for getting back to me - would Tuesday work for a quick call?",
  "cc": [
    "sam@acme.com"
  ],
  "createdAt": "2026-07-30T14:06:00Z",
  "id": 789,
  "inReplyToEmailId": 456,
  "leadId": 123,
  "subject": "Re: Quick question",
  "to": [
    "jane@acme.com"
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.