follow-ups

Send Follow Up Reply

Changed on

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.

post/api/v1/follow-ups/{message_id}/reply

Request

  • Base URL
    https://api.minro.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.minro.com/api/v1/follow-ups/{message_id}/reply
  • Auth
    none declared

Path parameters

message_idstring uuid required

Headers

authorizationstring nullable

Bearer <token>

Request body

bodystring required
subjectstring nullable
draft_idstring uuid nullable
transportstring
from_namestring nullable

Response

Successful Response

dataobject required

Changes

  • 299da1f7604aRevision changes
    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

  • 2eae594b5490Revision changes
    • info

      the response's property default value {"request_id":"","timestamp":"2026-09-16T23:27:36.856600"} was removed for the status

    • info

      the response's property default value 2026-09-16T23:27:36.856600 was removed for the status