Resolve Support Ticket
POST/api/support/tickets/:ticket/resolve
Marks the ticket resolved. Once resolved, the ticket can be rated (see Rate Support Ticket) and drops out of the default ticket list unless include_closed is set. The response is the updated ticket; both SLA clocks now report met or breached depending on whether the first response and the resolution landed before their due dates.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Bearer token with the support:write scope, or an authenticated session, from a user who can view the ticket. A caller whose support seat is the viewer role is refused with 403 — a viewer reads everywhere and writes nowhere, on the customer side as well as in the console. Requires the X-Tenant-Id header (or a tenant subdomain).
If this ticket was merged into another ticket, the request is refused with a 422 whose merged_into (id, number) names the live ticket — send the action there instead.
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.