---
title: "Send an AI reply draft"
method: POST
path: "/reply-drafts/{id}/send"
tags: ["Replies"]
---

# Send an AI reply draft

`POST /reply-drafts/{id}/send`

## Request

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

Schedules an AI reply draft for delivery through the conversation's sender mailbox, in the same email thread. It goes out as Reply All: to the person who wrote the reply, with everyone else they addressed (their To and Cc lines, minus your workspace's own mailboxes) in Cc, as listed in to and cc. The draft's current subject and body are what goes out, so edit first (PUT /reply-drafts/{id}) if needed. Emails that are not sendable AI reply drafts - already sent or scheduled emails, inbound replies, campaign sequence templates - are refused with 409. A draft whose conversation has no connected sender mailbox or no resolvable recipient is refused with 422.

## Path parameters

- `id` integer, required

## Response `200`

The draft is scheduled for delivery

- ModelsSendReplyDraftResponse
  - `body` string
  - `cc` string[]
  - `id` integer
  - `leadId` integer
  - `recipient` string
  - `status` string
  - `subject` string
  - `to` string[]: To and Cc are who the reply is being sent to (see ReplyDraftItem).

## Other responses

- `400`: Invalid draft ID
- `401`: Unauthorized - invalid or missing API key
- `404`: Reply draft not found
- `409`: Email exists but is not a sendable AI reply draft
- `422`: Draft cannot be delivered (no sender mailbox or no recipient)
- `500`: Failed to send reply draft

---

[API](https://skmtc.dev/emailchaser/apis/emailchaser-api.md) · [All operations](https://skmtc.dev/emailchaser/apis/emailchaser-api/llms.txt) · [OpenAPI document](https://skmtc.dev/emailchaser/apis/emailchaser-api/revisions/8b114990abb7?raw)