---
title: "Send Follow Up Reply"
method: POST
path: "/api/v1/follow-ups/{message_id}/reply"
tags: ["follow-ups"]
---

# Send Follow Up Reply

`POST /api/v1/follow-ups/{message_id}/reply`

Reply to a follow-up without Gmail, over the chosen transport:

- "domain" (default): SES from the workspace's verified receiving domain, with
  full threading headers, so it lands in the customer's existing thread and
  their next reply attributes back by header.
- "resend": the workspace's Resend identity, threading headers included
  (Resend passes them through).
- "autosend": the workspace's AutoSend identity. AutoSend reserves the
  threading headers, so the reply arrives as a "Re:" without hard threading;
  attribution of the next customer reply falls back to the subject match.

The outbound copy is echoed into the message store, which moves the item to
Responded. When draft_id is given, the (possibly edited) body is saved back
onto the draft before it's marked sent.

## Path parameters

- `message_id` string, uuid, required

## Headers

- `authorization` string, nullable — Bearer <token>

## Request body

- FollowUpReplyRequest
  - `body` string, required
  - `subject` string, nullable
  - `draft_id` string, uuid, nullable
  - `transport` string
  - `from_name` string, nullable

## Response `200`

Successful Response

- EnvelopeDict
  - `data` object, required
  - `meta` Meta
    - `request_id` string
    - `timestamp` string, date-time
    - `total` integer, nullable
    - `truncated` boolean, nullable

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/minro/apis/minro-cs-platform.md) · [All operations](https://skmtc.dev/minro/apis/minro-cs-platform/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/minro/minro-cs-platform/revisions/eb854265cf29/schema)