Reply or create internal note
Add a reply or internal note to the ticket. For customer-visible replies, optional external_recipient_emails sets CC recipients for that message; omit or null to reuse CC recipients from the previous customer-visible message or from ticket creation. Internal notes ignore this field. Optional attachment_ids claims files previously uploaded via POST .../tickets/{ticket_id}/attachments/ (see Tickets tag for the upload flow).
Authorizations
Body
- `` - (none)
close_and_mark_resolved- Close and Mark Resolvedclose_and_mark_invalid- Close and Mark Invalidclose_and_mark_customer_inactivity- Close and Mark Customer Inactivityreopen_waiting_customer- Reopen Waiting Customerreopen_waiting_associate- Reopen Waiting Associateclose_and_mark_other- Close and Mark Otherreport_spam- Report Spamremove_from_spam- Remove from Spam
, close_and_mark_resolved, close_and_mark_invalid, close_and_mark_customer_inactivity, reopen_waiting_customer, reopen_waiting_associate, close_and_mark_other, report_spam, remove_from_spam On create with CC email routing: for customer-visible messages, a list (empty or not) sets this message's external CC snapshot only; the ticket row is not updated. Omitted or null copies the last customer-visible message's snapshot, or the ticket's creation-time list if none. Internal messages (not visible to customer) always store an empty list; this field is ignored for them. The ticket requester is always kept when a list is sent. On read: snapshot stored on this message.
1On create with CC email routing: for customer-visible messages, optional BCC list for this send only (SMTP Bcc). Omitted, null, or empty means no BCC โ prior message BCC is never carried forward. Internal messages and orgs without CC routing always store an empty list. Cannot overlap the requester (To) or this message's CC list. On read: audit snapshot.
1List of attachment IDs to associate with this message.
Response
Legacy author object; may be deprecated for display in a future API version in favor of sender.
customer- Customercc- Ccassociate- Associatesystem- System
customer, cc, associate, system Who sent the message. Shape is one of the MessageSender variants in the schema; use top-level role to select it. null when role is system, or for associate without author.
- Option 1
- Option 2
- Option 3
True when message raw content is available for see-entire-message.
Ticket this message was originally created on, when a merge moved it here. Null for messages created on this ticket.
- `` - (none)
close_and_mark_resolved- Close and Mark Resolvedclose_and_mark_invalid- Close and Mark Invalidclose_and_mark_customer_inactivity- Close and Mark Customer Inactivityreopen_waiting_customer- Reopen Waiting Customerreopen_waiting_associate- Reopen Waiting Associateclose_and_mark_other- Close and Mark Otherreport_spam- Report Spamremove_from_spam- Remove from Spam
, close_and_mark_resolved, close_and_mark_invalid, close_and_mark_customer_inactivity, reopen_waiting_customer, reopen_waiting_associate, close_and_mark_other, report_spam, remove_from_spam On create with CC email routing: for customer-visible messages, a list (empty or not) sets this message's external CC snapshot only; the ticket row is not updated. Omitted or null copies the last customer-visible message's snapshot, or the ticket's creation-time list if none. Internal messages (not visible to customer) always store an empty list; this field is ignored for them. The ticket requester is always kept when a list is sent. On read: snapshot stored on this message.
On create with CC email routing: for customer-visible messages, optional BCC list for this send only (SMTP Bcc). Omitted, null, or empty means no BCC โ prior message BCC is never carried forward. Internal messages and orgs without CC routing always store an empty list. Cannot overlap the requester (To) or this message's CC list. On read: audit snapshot.