๐Ÿ”‘ /staff/tickets/:id

Updates the basic information for an already existing ticket

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requestsโ€ฆ
LoadingLoadingโ€ฆ

Necessary Permissions: can_view_tickets, can_edit_tickets

400 Response Error Keys

A 400 response will result in possibly several error keys being returned in the message section. Consult the table below for what error key represents.

KeyDescription
NO_NAMEThe name is null or blank and a name is required
INVALID_OR_MISSING_EMAILThere is no email and it is required, OR one of the email addresses are not valid
SUBJECT_REQUIREDThe subject is null or blank and a subject is required
MESSAGE_REQUIREDThe message is null or blank and a message is required
MISSING_LANGUAGEThe language is null or blank and the helpdesk supports multiple languages
Path Params
int32
required

The ticket ID. Not the tracking ID.

Body Params
string

The user's language. Must be an active language in your helpdesk install. Required if helpdesk supports multiple languages

string
required

The customer's name

string

The ticket subject. Required if helpdesk requires subjects

string

The ticket message. Required if helpdesk requires messages

boolean
required

true if the message should be stored as rich-text, false otherwise

string

The user's email. Multiple emails supported (separated by ; or ,) if multiple emails are enabled. Required if emails are enabled

Responses

Language
LoadingLoadingโ€ฆ
Response
Choose an example:
application/json