Turn AI Agent Off for Ticket
POST/api/support/agent/tickets/:ticket/ai/disable
Turn the AI agent off for one ticket: it never claims the ticket or acts on it until it is turned back on. If the AI agent owns the ticket, its claim is released (an internal released event with reason ai_disabled) and the ticket goes back to the unassigned queue; a ticket a human owns stays with them. Records an internal ai_disabled event; turning it off twice changes nothing. Works on any ticket.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Path parameters
ticket(integer) — the ticket id.
No request body. The response is the updated ticket in the agent shape (see Get Agent Ticket for every field, including the work control fields ai_paused, ai_paused_by, ai_paused_at, ai_disabled, stop_requested_at, stop_requested_by and pending_instructions).
Authentication: Bearer token with the support:write scope, or an authenticated session, from a caller with an active support role that can work tickets (the viewer role is read-only). No tenant context — this endpoint is central.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthorized
Response Headers
Forbidden
Response Headers
Not Found
Response Headers
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.