Skip to main content
POST
Reply to a ticket

Authorizations

Authorization
string
header
required

Your API key, sent as a bearer token. Create one in the control panel under API Keys, give it only the permissions the integration needs, and copy it when it is created. It cannot be shown again. Each key is restricted to one owned team. The key determines the team for every request.

Path Parameters

ticket
string
required

The ticket number returned by the support endpoints.

Example:

5316

Body

multipart/form-data

Send a JSON object containing the fields below. Required fields are marked in the schema.

message
string
required

The message text.

Required string length: 2 - 20000
attachments
file[]

The value of attachments.

Maximum array length: 5

Maximum file size: 4096 kilobytes.

Response

The record, as a JSON object. There is no envelope.

A support ticket and its current status.

id
integer
required

The id ID.

Example:

5316

number
string
required

The ticket reference sent by email, such as #ABC-123456. Use the numeric ticket ID for API requests.

Example:

"NQX-482913"

subject
string
required

The subject line for the message.

Example:

"Packet loss on lambda-core"

status
string
required

The value of status.

Example:

"Open"

priority
string | null
required

The value of priority.

Example:

"Medium"

department
string | null
required

The value of department.

Example:

"Technical Support"

opened_at
string | null
required

The date and time for opened at, in UTC.

Example:

"2026-09-14T09:12:44+00:00"

last_replied_at
string | null
required

The date and time for last replied at, in UTC.

Example:

"2026-09-14T09:12:44+00:00"

awaiting_customer
boolean
required

Whether the customer is the one being waited on.

Example:

false

closed
boolean
required

The value of closed.

Example:

false

service
string | null
required

The value of service.

Example:

null

server
TicketServerData · object | null
required

The machine it is about, where the service names one. Enough of it to draw the badge the customer recognises and to link to it.

Example:
url
string | null
required

The ticket's external portal URL. Use it for actions or attachment types unavailable in the panel.

Example:

"https://clients.advinservers.com/viewticket.php?tid=NQX-482913&c=Hx7kQ2Rm"

messages

The conversation, oldest first, and only where it was asked for.