/tickets/{ticket_id}/replyReply to a ticket
Submits a reply or note on a ticket, either on behalf of an admin or a contact. For an admin reply, set message_type and provide the fields required for that reply type; for a contact reply, identify the contact using one of the supported identifiers. Use the ticket object's internal id, not the ticket number shown in the Inbox.
- IdempotentThe SDK sends
Idempotency-Key, so a retried request is only applied once.
Reply payload for an admin or contact, with optional notification settings. Contact replies identify the contact using intercom_user_id, user_id, or email; admin replies require message_type, type, and admin_id.
One documented failure
parameter_mismatchUser replies are not allowed on Backoffice tickets
One documented failure
unauthorizedAccess Token Invalid
One documented failure
not_foundResource Not Found
A 400 is returned when the reply payload is invalid, a 401 when the request is unauthorized, and a 404 when the ticket is not found. The ticket_id path parameter must be the ticket object's internal ID, not its Inbox ticket number. For admin replies, message_type must be comment, note, or quick_reply; comment and note require body, while quick_reply requires reply_options with text and uuid on each option.