Flag Ticket as Important to Customer
POST/api/support/agent/tickets/:ticket/important
Flags (or unflags) a ticket as important to the tenant that raised it. The flag weights the customer-demand count behind a linked issue (see List Issue Requesters), can be filtered and sorted on in the agent queue, and every change is recorded on the ticket timeline with the agent who made it.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Path parameters
ticket(integer) — the ticket id.
Request body
important(required, boolean)
Response fields (data) — id (the ticket id) and important_to_customer (the flag after the write). Setting the flag to what it already is changes nothing and records no timeline entry.
Authentication: Bearer token with the support:write scope, or an authenticated session, from a caller with an active support role that can work tickets.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthorized
Response Headers
Forbidden
Response Headers
Not Found
Response Headers
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.