All the endpoints that can be called on the Message controller.
All of the endpoints require the MESSAGE_CREATE
permission.
Creates a new message.
The ticket must already exist. It will clear the ticket's cache before processing this data.
If you want to send a message in an already existing ticket.
What channel to send the message in.
^([0-9]+|calllog|contactform)$
Nullable for contact forms and notes. Can be multiple email addresses split by a ','
""
""
""
Add this parameter if it is a reply to an existing message.
0
If this one is empty, it will use the value of the message parameter instead. Only relevant for emails.
""
The actual message.
If you want to forward existing files.
[]
A special parameter as it is a string that would be following the ISO date format.
The ID of the user who created this message.
0
POST /api/v2/message HTTP/1.1
Host: {{base_url}}
apiKey: YOUR_API_KEY
Content-Type: multipart/form-data
Accept: */*
Content-Length: 195
{
"ticketID": 1,
"type": "text",
"toAddress": "",
"ccInput": "",
"bccInput": "",
"respondMessageID": 0,
"plaintext": "",
"message": "text",
"forwardedFileIDs": [
1
],
"sendAt": "text",
"userID": 0,
"submitStatus": "open"
}
No content
Creates a ticket and its accompanying message coming from a chatbot.
POST /api/v2/message/chatbot HTTP/1.1
Host: {{base_url}}
apiKey: YOUR_API_KEY
Content-Type: multipart/form-data
Accept: */*
Content-Length: 61
{
"brandID": 1,
"message": "text",
"subject": "text",
"from": "text"
}
No content