Authorizations
Cookie-based authentication
Path Parameters
The ID of the ticket to store conversation for
Body
When to run AI logic for the conversation. Realtime=Run AI logic synchronously, even though this will take some time, Batch=Run AI logic after the conversation is created asynchronously, False=Do not run AI logic at all.
realtime
, batch
, false
The direction of the conversation. Out=Outgoing to customer, In=Incoming from customer, Internal=Internal conversation, e.g. from an internal email address from another department.
in
, out
, internal
From email address
"john@smith.com"
From name
"John Smith"
To email addresses
["customer@web.de"]
CC email addresses (can include names with email format like "Name email@domain.com")
[
"Michael Jackson <michael-test123@jack.s.on.com>"
]
BCC email addresses
Email subject line
"Ticket subject"
HTML body content
"Ticket body PART 2"
Optional plain text body content. If not set, the body content will be used, stripped of HTML tags.
Optional clean body content. This is the body content without any HTML tags. If not set, the body content will be used, stripped of HTML tags.
Whether this is a private conversation (internal note by an agent)
false
Subchannel ID. Must correspond to a subchannel in the ticket's channel. A subchannel is e.g. a specific mailbox (for email tickets) or a specific chat channel (for chat tickets)
4
Ticket status
open
, pending
, closed
"open"
Creation timestamp (YYYY-MM-DD HH:MM:SS format) when the conversation was created. If not set, the current timestamp will be used.
"2024-03-01 00:00:00"
Optional first response due date (YYYY-MM-DD HH:MM:SS format). If set, the ticket will be updated with this first response due date.
"2021-01-02 00:00:00"
Optional due date (YYYY-MM-DD HH:MM:SS format). If set, the ticket will be updated with this due date.
"2021-01-07 00:00:00"
File attachments (either url or base64 should be provided per attachment)
External conversation ID for tracking
"abc-123"
Custom user-defined data object for additional metadata
{ "myObjectId": 123 }
The type of conversation
Sender information
Conversation content
Array of intent IDs
Optional external CRM notification ID
Contract ID
Customer ID
Agent ID that authored the conversation
Optional ticket priority. If set, the ticket will be updated with this priority.
low
, medium
, high
, urgent