Draft and send a message reply on a Front conversation via the Front API
domain: dev.frontapp.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call POST https://api2.frontapp.com/conversations/{conversation_id}/messages (scope messages:send) with a required body field plus optional to/cc/bcc, subject, author_id, and channel_id to send a reply appended to the conversation.
Expect a 202 Accepted response acknowledging the send request (not a delivery confirmation), or a 301 if the conversation has been merged.
To stage an editable draft instead of sending immediately, call POST https://api2.frontapp.com/conversations/{conversation_id}/drafts (scope drafts:write), which requires channel_id and body.
Set the draft's mode to private (default, visible only to the author) or shared (visible to all teammates with access to the conversation).
Attach files as multipart/form-data on either endpoint (max 25 MB per file per Front's Attachments docs), and optionally set signature_id or should_add_default_signature.
There is no dedicated 'send draft' endpoint — to actually send, compose and call Create Message or Create Message Reply directly; the drafts endpoint is intended for in-app teammate revision.
Known gotchas
signature_id (or should_add_default_signature) only works on email channels; using it on another channel type returns a 403 Forbidden.
The 202 response from create-message-reply only means Front accepted the request to send — it is not proof the message was delivered.
Drafts default to mode=private (author-only visibility) unless you explicitly set mode to shared.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?