Skip to content

Reply to a support ticket

POST /api/v2/support/tickets/{id}/messages

Adds your reply to a support ticket. It is a customer-visible reply in the ticket conversation, not an internal escalation or a private note. The response is the new message.

A closed ticket takes no replies and returns 400 invalid_request. Reopen it first with POST /api/v2/support/tickets/{id}/actions/reopen.

This call takes no files. Upload a file with POST /api/v2/support/attachments and put the returned url in message.

Authentication: An API key with the scope write:support. About keys and scopes

Request

Path parameters

idstringrequired
The ticket ID (tkt_…) or the ticket number.

Body

messagestringrequired
The reply, up to 65536 characters.
encryptedboolean
Set true to store the reply encrypted, for example when it holds a password. Default false.

Example

POST /api/v2/support/tickets/{id}/messages
curl -X POST "https://cloud.hostup.se/api/v2/support/tickets/tkt_01hxa3b4c5d6e7f8g9h0j1k2m3/messages" \
-H "Authorization: Bearer $HOSTUP_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"message": "Here are the extra details you asked for."
}'

Responses

201 Created customer-visible ticket message.

Response 201
{
"id": "tmsg_01hxa3b4c5d6e7f8g9h0j1k2m3",
"ticketId": "tkt_01hxa3b4c5d6e7f8g9h0j1k2m3",
"sentAt": "2026-04-27T12:00:00.000Z",
"body": "Here are the extra details you asked for.",
"sender": "customer",
"senderName": "Jane Example",
"encrypted": false,
"attachments": []
}
Response fields
idstring
The message ID (tmsg_…).
ticketIdstring
The ticket ID (tkt_…).
sentAtstring or null
When the reply was sent.
bodystring or null
The reply text.
senderstring
Who wrote the message: customer, staff or automation. One of customer, staff, automation.
senderNamestring or null
Name shown on the message.
encryptedboolean
Whether the reply is stored encrypted.
attachmentsarray of object
Files attached to the message.

Errors

Errors are Problem Details with a stable code. Branch on the code, not on the text.

400Invalid request. The response body is an RFC 7807 Problem Details document.
401Unauthorized. Authentication is required.
403Forbidden. The caller lacks a required scope or does not own the resource.
404Not found. The resource does not exist or is not owned by the caller; code is ticket_not_found.
429Rate limited. Retry after the limit resets. 429 responses include Retry-After seconds plus X-RateLimit-* headers.
500Internal error. Retry later or contact support if the issue persists.
502Upstream failure. A dependent provider request failed; the Problem Details code is upstream_failed. Retry later or contact support if the issue persists.